Print out thread context switches when a test fails #8
Labels
enhancement
New feature or request
Comments
upthewaterspout
added a commit
that referenced
this issue
Oct 2, 2018
Printing out the places where a thread switches context if a test failures. This task is not quite done, because not all line numbers are instrumented yet - just field access. We should record all line numbers a test visits so that we print the most accurate line number when there is a context switch.
|
This is now partially done, but only field accesses record line numbers. We should record every line number. We may also want to include the event that triggered a context switch in the debugging output - was it a field access, or a wait/notify, etc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is not a lot of debugging information a user gets when a test fails right now.
One useful piece of information would be when we switched from one thread to another.
We could record the class and line number of each decision in the
DecisionTree. Then if a test fails, we could take the currentDecisionTreeand print out all of its parents where the decision switched us from one thread to the other, including the class and line number where that happened.The text was updated successfully, but these errors were encountered: