Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BCPT Test Results Viewer #813

Open
freddydk opened this issue Nov 12, 2023 · 0 comments · May be fixed by #619
Open

BCPT Test Results Viewer #813

freddydk opened this issue Nov 12, 2023 · 0 comments · May be fixed by #619
Assignees
Labels
enhancement New feature or request

Comments

@freddydk
Copy link
Contributor

Summary

AL-Go already have support for running BCPT tests during CI/CD or PR builds, there are however no graphical representation of the BCPT test result in the build summary.

We should show a graphical representation of the BCPT Test and allow to display results against a prior BCPT test result run.

We should allow to set a threshold on both time and no. of SQL statements executed during a test

Success Criteria

Implementation

Try it out

Inside GitHub (like Test Results Viewer):

  • Graphical presentation of BCPT Test Results
  • Measure against baseline in repo
  • Measure against performance test results to latest release (the baseline) + latest builds (second baseline -> trending)
  • Set threshold for warnings and errors on performance regressions
  • Ability to ignore performance regressions for one release (resetting the baseline)

Outside GitHub (PowerBI dashboard):

  • Create a dashboard, which connects to your AL-Go repos and extracts BCPT test results data.
@freddydk freddydk self-assigned this Nov 12, 2023
@freddydk freddydk added the enhancement New feature or request label Nov 12, 2023
@freddydk freddydk linked a pull request Nov 12, 2023 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🏗 In progress
Development

Successfully merging a pull request may close this issue.

1 participant