-
- Downloads
Changed methodology for benchmarks
* Usage of pytest-benchmarks is dropped since it call tests sequentially which very long time to complete, instead original tavern tests are used * Time measuring is done via durations switch to pytest and tavern * During benchmarking validate_response.py is disabled using nevly introduced env variable * Each run creates xml junit file with time data * After all runs data from files are combined and report file is generated * Tests above threshold are marked with red
parent
6e925e63
No related branches found
No related tags found
Showing
- .gitlab-ci.yaml 2 additions, 11 deletions.gitlab-ci.yaml
- scripts/ci_start_api_benchmarks.sh 20 additions, 0 deletionsscripts/ci_start_api_benchmarks.sh
- scripts/xml_report_parser.py 105 additions, 0 deletionsscripts/xml_report_parser.py
- tests/tests_api 1 addition, 1 deletiontests/tests_api
- tox.ini 16 additions, 1 deletiontox.ini
scripts/ci_start_api_benchmarks.sh
0 → 100755
scripts/xml_report_parser.py
0 → 100755
Please register or sign in to comment