-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Put the test message location to where it happens #1266
Comments
@jdneo Your last two points make good sense, focusing on the assertion stack placement in the data model. |
Yes, this is a sore point. The score Visual Studio Code vs Eclipse was around 7 x 3 , but now it is around 7 x 6 because eclipse actually shows where an error happens, and Visual Studio Code doesn't. |
Hi @TimWebb, @abmpicoli. I just made a proposal for this issue: #1323. If you have time, could you take a look and see if this UX looks good to you? |
End game verification steps:
|
More specifically, if an assert fails, have the TestMessage's location of the assert match the location in the method for the given assert. Similarly if something triggers an exception, we could have a TestMessage for the exception in potentially even a different file - such as extract from the exception stack the location in testMethod() that resulted in the failure.
Originally posted by @TimWebb in #1162 (comment)
The text was updated successfully, but these errors were encountered: