Currently, we run a bunch of tests on the moby/moby codebase for each PR and against the master branch of the repo after a PR is merged, but the results of the tests are in approximately 400KB of plain-text format. To find out which test failed, a user would have to view the console logs of the jenkins job and do a browser text search for FAIL:.
Would be better to have the test results also reported in a structured format for consumption by report generators to make pretty graphs and tables and such. Having the test result in a junit xml format would allow jenkins UI to consume and generate reports with the junit plugin.
The type of information we could easily find with a junit xml format output:
- name of all the test case failures (assuming the jenkins job does not stop running tests upon first failure)
- time it took to run each test case
- summary of how many tests were run, how many passed, how many failed, and how many were skipped
Would need to generate junit xml format for each of the 4 test frameworks in moby/moby:
- unit tests - uses golang testing and can output junit xml by using gotestsum to execute tests
- integration tests - uses gotest.tools and can output junit xml by using gotestsum to execute tests
- integration-cli tests - uses go-check and can output junit xml by using go2xunit
- docker-py tests - uses pytest and can output junit xml by setting --junitxml flag
Progress:
Currently, we run a bunch of tests on the moby/moby codebase for each PR and against the master branch of the repo after a PR is merged, but the results of the tests are in approximately 400KB of plain-text format. To find out which test failed, a user would have to view the console logs of the jenkins job and do a browser text search for
FAIL:.Would be better to have the test results also reported in a structured format for consumption by report generators to make pretty graphs and tables and such. Having the test result in a junit xml format would allow jenkins UI to consume and generate reports with the junit plugin.
The type of information we could easily find with a junit xml format output:
Would need to generate junit xml format for each of the 4 test frameworks in moby/moby:
Progress:
WIP added entry for running unit tests with junit report #39637added entry for running unit tests with junit report #39638