Difference between revisions of "NeutronThirdPartyTesting"
(Created page with "This page documents the requirements, expectations, and ideally the results of all third party testing done by open source and vendor plugins for the Neutron project.") |
|||
Line 1: | Line 1: | ||
This page documents the requirements, expectations, and ideally the results of all third party testing done by open source and vendor plugins for the Neutron project. | This page documents the requirements, expectations, and ideally the results of all third party testing done by open source and vendor plugins for the Neutron project. | ||
+ | |||
+ | == Log & Test Results filesystem layout == | ||
+ | |||
+ | Third party CI systems should follow the filesystem layout convention of the OpenStack CI system | ||
+ | |||
+ | At the root of the results - there should be the following: | ||
+ | |||
+ | * console.html.gz - contains the output of stdout of the test run | ||
+ | * logs/ | ||
+ | |||
+ | Logs must be a directory, which contains the following: | ||
+ | |||
+ | * Log files for each screen session that DevStack creates and launches an OpenStack component in | ||
+ | * Test result files | ||
+ | ** testr_results.html.gz | ||
+ | ** tempest.txt.gz |
Revision as of 21:06, 9 June 2014
This page documents the requirements, expectations, and ideally the results of all third party testing done by open source and vendor plugins for the Neutron project.
Log & Test Results filesystem layout
Third party CI systems should follow the filesystem layout convention of the OpenStack CI system
At the root of the results - there should be the following:
- console.html.gz - contains the output of stdout of the test run
- logs/
Logs must be a directory, which contains the following:
- Log files for each screen session that DevStack creates and launches an OpenStack component in
- Test result files
- testr_results.html.gz
- tempest.txt.gz