BCPT Test Report

[freddydk]

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:

• Add tests
• Add thresholds to project settings
• 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.
• Determine sorting of test results? (codeunitID, codeunitName or ???)
• Issue GitHub warnings and errors when thresholds are exceeded
• Is durationMin in milliseconds, seconds or what? how many decimal digits should be displayed?
• Get BCPT Backend Team signoff that BCPT Test Results are correctly understood and compared
• Add scenario documentation

Example of bcpt tests with failures and warnings:

[mazhelez]

Looks okay to me.

Should there be any part of the E2E tests that check any of the new functionality?

[aholstrup1]

Don't fully agree with adding the bcptThresholds.json file but the rest of the PR looks good and will be a really nice improvement to AL-Go 🥳

[mazhelez]

Expect for the MD generation, the PR looks okay.

Tests are also hard to understand. Maybe using a template for the markdown will help there as well.