-
Notifications
You must be signed in to change notification settings - Fork 59
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
Line number for check failure is wrong. #47
Comments
Fixed in |
Unfortunately this is still not fixed. |
Hey @jmisur! Please reopen this. :) |
Thanks for reopening! :) Can I somehow help you? |
I checked your surefire results and found out an interesting piece (which I noticed previously but forgot about). Your testcase classname is a bit weird. I know you're running some test matrix setup which makes tests work on different dbs. How did you set this up? Is this something manual or out of the box? Is it always in this format |
Hey @jmisur,
we use the maven property The documentation of the property can be found here: http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#reportNameSuffix
Looks like an out of the box feature from the maven-surefire-plugin
I assume that the plugin does classname(suffix). Can't tell for sure. |
Thank you for fixing this :) |
Fixed in v1. |
After fixing #43 I realized that every failed test gets annotated with
Check failure on line 1 in XXX
.I expected that the line number will be computed correctly. Unfortunately only
line 1
is shown.Example Report: https://github.com/mustaphazorgati/taskana/runs/1840214460?check_suite_focus=true
The text was updated successfully, but these errors were encountered: