Confirmed users
2,197
edits
TestEngineering/Performance/Results: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Results (view source)
Revision as of 12:15, 17 December 2019
, 17 December 2019→Ad-hoc results
No edit summary |
|||
| Line 137: | Line 137: | ||
Before performance tests are fully automated and integrated into our pipeline, we often run manual or semi-automated tests. These results are often presented in ways that don't fit into our existing reporting structures, such as spreadsheets or documents. The following list of links serves as a repository for these results: | Before performance tests are fully automated and integrated into our pipeline, we often run manual or semi-automated tests. These results are often presented in ways that don't fit into our existing reporting structures, such as spreadsheets or documents. The following list of links serves as a repository for these results: | ||
* [https://drive.google.com/drive/u/0/folders/ | * [https://drive.google.com/drive/u/0/folders/1sZ6C6bku2vR575GSH5DxgSlP43JYT-Je Performance/Results] | ||
* [https://drive.google.com/drive/folders/11a90GH_xwcqwkcAmzCZAkwmQeuSoXA3n Performance/Projects/Desktop/Testing] | * [https://drive.google.com/drive/folders/11a90GH_xwcqwkcAmzCZAkwmQeuSoXA3n Performance/Projects/Desktop/Testing] | ||
Please make sure when you add results to the above locations that the name or internal labeling is clear as to what was tested, the methods used, when the results were gathered, and anything else that may be useful. | |||