You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR will add a BCPT Test Report to the build summary, looking like
this:

You can also add a bcptBaseLine.json to the project in order to
establish a baseline for the performance tests.
It looks like this:

TODOs:
- [x] Add tests
- [x] Add thresholds to project settings
- [x] Determine how thresholds should work? threshold on very small
items like (enter account no.) doesn't make much sense. It absolutely
makes sense to have threshold on scenarios.
- [x] Determine sorting of test results? (codeunitID, codeunitName or
???)
- [x] Issue GitHub warnings and errors when thresholds are exceeded
- [x] Is durationMin in milliseconds, seconds or what? how many decimal
digits should be displayed?
- [x] Get BCPT Backend Team signoff that BCPT Test Results are correctly
understood and compared
- [x] Add scenario documentation
Example of bcpt tests with failures and warnings:

---------
Co-authored-by: freddydk <[email protected]>
Co-authored-by: Alexander Holstrup <[email protected]>
Co-authored-by: Maria Zhelezova <[email protected]>
# If summary AND BCPT summary AND failures summary fits, we will display all in the GitHub summary
43
+
if ($testResultsSummaryMD.Length+$testResultsfailuresMD.Length+$bcptSummaryMD.Length-gt65000) {
44
+
# If Combined Test Results, failures and BCPT summary exceeds GitHub summary capacity, we will not display the failures details, only the failures summary
0 commit comments