-
Notifications
You must be signed in to change notification settings - Fork 21
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
[RFE] Testing framework for the dashboard #121
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I think whatever bot is closing these "stale" issues should probably be shut down... or at least reconfigured to give a lot more time. |
cc: @jtaleric looks like it is an org level setting. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Description
As of today our dashboard has naturally grown with a decent amount of changes which displays data related to multiple products like OCP, Quay, Telco and HCP as well. While we have a well grown UI, we do not have a proper testing framework that makes sure if all the components are working as expected which has been a technical debt for a while. So we will need to implement a testing framework to the dashboard.
Acceptance Criteria
As a contributor/developer one should be able to trigger the testing framework for their changes and generate a coverage report out of it. This should help us to detect breaking changes earlier w.r.t any new additions or updates in the code base.
The text was updated successfully, but these errors were encountered: