Our build process produces multiple directories of report XML files. The
workspace structure looks like this:
build/
integration-a/
test-results/
integration-b/
test-results/
integration-c/
test-results/
integration-d/
test-results/
The project is configured to collect the test results using the following
file path:
build/integration-*/test-results/*.xml
I have verified looking in the workspace after the build that all the XMl
files are there and that all the tests have run.
The problem is that Jenkins is reporting slightly different counts of unit
tests every build. I've looked back over older builds and this has been
happening for months (could be even longer, but I just switched servers and
lost my older history). For example, the last few build test counts have
looked like this (the number of tests should not have changed at all):
#23 18,875 tests (+210)
#22 18,665 tests (±0)
#21 18,665 tests (+204)
#20 18,461 tests (-401)
#19 18,862 tests (+186)
#18 18,676 tests (-147)
#17 18,823 tests (-39)
The graph of test counts shows the count variation as well:
<https://lh5.googleusercontent.com/-tsVU5Ks6uuc/UdyCXh2mUJI/AAAAAAACewU/jaOF2nwFR60/s1600/test_counts.png>
When I review the test results in Jenkins, I find every test that it
doesn't list. When I look at the workspace, I can find the XML file and
there are also HTML files (in build/integration-*/reports/tests/) that are
produced and all the tests are there as well. It just seems Jenkins is
dropping various test XML files on each build. I just can't see a pattern.
The count seems different every time.
Has anyone else see something like this? Anyone have any suggestions?
Chuck
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
