After setting up a new HP ALM Lab Management build in Jenkins, a test set containing 127 tests executes completely, but the results only display in Jenkins for 100 test cases. We confirmed within ALM that all 127 tests executed. Note: It is not the first 100 test cases executed. The first test case executed is written to the results, and so is the last test case.

For comparison, we also set up a standard "HP tests from HP ALM" build in Jenkins. This is non-Lab Management. The results displayed all 127 tests within Jenkins.

The only obvious difference between the two builds is the build type ... the first is Lab Management, and the second is not Lab Management.

The reason for the number of test case results being limited to 100 tests appears to be related to how the HP plug-in is writing the results to XML files. Two files (junitResult.xml and Results<timestamp>.xml) are written during test execution. Both files only contain results for 100 tests, instead of all 127 tests.

junitResult.xml resides in "\jenkins\jobs\<job_name>\builds\<build_num>\". Each test case is written to the node "<result><suites><suite><cases><case><testName>". There are only 100 of these nodes in the file.

Results<timestamp>.xml resides in "\jenkins\jobs\<job_name>\workspace\". Each test case is written to the node "<testsuites><testsuite><testcase>". There are only 100 of these nodes in the file.

Attachments:

1. Jenkins_LabMgmt.png - shows the header within Jenkins for the build. The build type is "HP tests using HP ALM Lab Management". This is the build type that limits results to 100 test cases.

2. Jenkins_NonLabMgmt.png - shows the header within Jenkins for the build. The build type is "HP tests from HP ALM". This is the build type that does not limit results.

3. Jenkins_TestResults.png - this is the header for the Test Results page. It shows that the results for only 100 tests are displayed.