Skip to content
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

Closed
mustaphazorgati opened this issue Feb 6, 2021 · 8 comments · Fixed by #49 or #54
Closed

Line number for check failure is wrong. #47

mustaphazorgati opened this issue Feb 6, 2021 · 8 comments · Fixed by #49 or #54

Comments

@mustaphazorgati
Copy link

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

@jmisur
Copy link
Contributor

jmisur commented Feb 10, 2021

Fixed in v1.

@mustaphazorgati
Copy link
Author

Unfortunately this is still not fixed.
I've tried v1 and v1.0.8.

@mustaphazorgati
Copy link
Author

Hey @jmisur!
This issue is currently not fixed. I've tried again: https://github.com/mustaphazorgati/taskana/runs/2130607083?check_suite_focus=true

Please reopen this. :)

@jmisur jmisur reopened this Mar 22, 2021
@mustaphazorgati
Copy link
Author

mustaphazorgati commented Mar 22, 2021

Thanks for reopening! :)
If it helps: You can download the surefire xml files from the workflow: https://github.com/mustaphazorgati/taskana/actions/runs/661020161
Artifact-id: surefire-report

Can I somehow help you?

@jmisur
Copy link
Contributor

jmisur commented Mar 24, 2021

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.
<testcase name="should_SplitListIntoChunks_When_CallingPartitionBasedOnSize" classname="pro.taskana.common.api.CollectionUtilTest(H2)" time="0.049">

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 classname(strategy) or it's a custom format? I need to know if I can take this example as the generic pattern so I can extract a raw classname from it. That's why line resolution doesn't work.

@mustaphazorgati
Copy link
Author

mustaphazorgati commented Mar 24, 2021

Hey @jmisur,

How did you set this up?

we use the maven property surefire.reportNameSuffix to add the information on which database the test ist executed.
See here: https://github.com/Taskana/taskana/pull/1536/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8

The documentation of the property can be found here: http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#reportNameSuffix

Is this something manual or out of the box?

Looks like an out of the box feature from the maven-surefire-plugin

Is it always in this format classname(strategy) or it's a custom format?

I assume that the plugin does classname(suffix). Can't tell for sure.

@mustaphazorgati
Copy link
Author

Thank you for fixing this :)

@jmisur
Copy link
Contributor

jmisur commented Mar 24, 2021

Fixed in v1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants