-
Notifications
You must be signed in to change notification settings - Fork 217
TestCase location hint #150
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
Comments
<img src="https://avatars.githubusercontent.com/u/2909286?v=3" align="left" width="48" height="48"hspace="10"> Comment by madsager Could you provide more information on this bug? What are you trying to do? Example code and what you expect would be great. Thanks. Added NeedsInfo label. |
This comment was originally written by [email protected] Sorry for delay. Being on vacation. I meant a hint with information about test/group method invocation location. For example information could contain the file URI and the line number. It useful for quick navigation to the test/group method invocation. Now it's only possible after a test fails and we can check the stack trace. |
<img src="https://avatars.githubusercontent.com/u/3276024?v=3" align="left" width="48" height="48"hspace="10"> Comment by anders-sandholm Added Area-Library, Triaged labels. |
<img src="https://avatars.githubusercontent.com/u/5479?v=3" align="left" width="48" height="48"hspace="10"> Comment by sethladd CC'ing Gram as this is about Unit Test library. CC'ing Devon because I think Dart Editor team would like to add a UNit test running to editor, and allow a user to run a single test and navigate to a single test. cc @gramster. |
<img src="https://avatars.githubusercontent.com/u/2762632?v=3" align="left" width="48" height="48"hspace="10"> Comment by gramster Groups can be nested, so you could just add an outer group to your tests with the file name... |
<img src="https://avatars.githubusercontent.com/u/4865287?v=3" align="left" width="48" height="48"hspace="10"> Comment by lrhn Removed Area-Library label. |
<img src="https://avatars.githubusercontent.com/u/17034?v=3" align="left" width="48" height="48"hspace="10"> Comment by kevmoo Added Pkg-Unittest label. |
<img src="https://avatars.githubusercontent.com/u/17034?v=3" align="left" width="48" height="48"hspace="10"> Comment by kevmoo Removed Area-UnitTest label. |
<img src="https://avatars.githubusercontent.com/u/67586?v=3" align="left" width="48" height="48"hspace="10"> Comment by pq The relevant bug on the IntelliJ side: http://youtrack.jetbrains.com/issue/WEB-1588 |
<img src="https://avatars.githubusercontent.com/u/67586?v=3" align="left" width="48" height="48"hspace="10"> Comment by pq The rub is that there is currently no way for tools to infer a source location from a TestCase unless the test failed. If the test has failed, there's a stack trace to parse. Not pretty but doable. No such luck in the passing case though. Where this comes into play is in a tool, such as WebStorm/IDEA or Eclipse/DartEditor, where you want to display a navigable test result view. I'm optimistically bumping this to 1.4 in the hopes that we get "making unittest more tool-friendly" on the agenda as cleanup happens. |
<img src="https://avatars.githubusercontent.com/u/2156198?v=3" align="left" width="48" height="48"hspace="10"> Comment by kasperl Removed this from the 1.4 milestone. |
<img src="https://avatars.githubusercontent.com/u/2156198?v=3" align="left" width="48" height="48"hspace="10"> Comment by kasperl Removed this from the 1.5 milestone. |
<img src="https://avatars.githubusercontent.com/u/2156198?v=3" align="left" width="48" height="48"hspace="10"> Comment by kasperl Removed this from the 1.6 milestone. |
<img src="https://avatars.githubusercontent.com/u/2156198?v=3" align="left" width="48" height="48"hspace="10"> Comment by kasperl Removed Oldschool-Milestone-1.6 label. |
This is something that should be handled via the test API, so I'm going to merge it into #48. |
Originally opened as dart-lang/sdk#4672
This issue was originally filed by [email protected]
Add locationHint field with location of the Test.
The text was updated successfully, but these errors were encountered: