feat: show detailed stacktrace and debugging info when test runner fails #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Problem: When the embedded test runner throws an uncaught exception, (e.g., within `plenary.busted.run()` or `plenary.busted` can't be imported) no detailed stacktrace information was printed. Solution: Catch lua exception within the test runner and print full stacktrace.
wookayin
force-pushed
the
runner-stacktrace
branch
from
df381cc
to
3382ff7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
When the embedded test runner throws an uncaught exception, (e.g.,
within
plenary.busted.run()orplenary.bustedcan't be imported)no detailed stacktrace information was printed.
Solution:
Catch lua exception within the test runner and print full stacktrace.