-
Notifications
You must be signed in to change notification settings - Fork 26
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
Remove TestRunConfig #14
Comments
This is blocked until fronted is updated. |
@mikaelhm Is this still blocked? |
Still need some changes in the backend. Need to make sure we can run with CLI and Frontend. |
@mikaelhm: This seems like an old issue (and not applicable anymore), as lot of changes has happened since this was created. |
Will start work on this. |
@raul-marquez-csa, we need an issue for both frontend and backend. Can you create 2 sub-issues for 1. and 2. take those, then I can make one for backend. |
I created these two Remove TestRunConfig [Frontend] #887 Remove TestRunConfig [Backend] #888 |
Issue on hold |
Backend PR is approved. Waiting for the front-end PR to be reviewed. |
I think this one is still related: |
PRs addressing the issue: Frontend: Updates create and repeat test run execution to match backend changes #13 |
* Added custom yamls tests * add custom folder * Add blank line * review changes
From chip-certification-tool created by mikaelhm: CHIP-Specifications/chip-certification-tool#816
Once the frontend support the new project format, we can remove the TestRunConfig completely and require TestRunExecutions to be created with selected_tests directly.
The text was updated successfully, but these errors were encountered: