So that I can make changes to the frontend more efficiently.
Discussion
During M23, the m23-10am-4 team from HappyCows implemented improvements to the stryker mutation testing run for PRs, so that not only would it do an incremental run, it would perform that run only on the specific files that were modified by the PR.
That reduces running times for Stryker by an order of magnitude.
The task here is to get those changes into this repo.
Acceptance Criteria
[ ] When Stryker mutation testing runs on a PR it only runs on the modified files.
[ ] When Stryker mutation testing runs on the main branch after a push to the main branch, it still runs a full mutation testing run.
This is a "belt & suspenders" approach; the idea though is that the full mutation testing run happens after the PR is merged, as a backup safety run; it doesn't hold up the PR from getting merged.
User Story
Discussion
During M23, the m23-10am-4 team from HappyCows implemented improvements to the stryker mutation testing run for PRs, so that not only would it do an incremental run, it would perform that run only on the specific files that were modified by the PR.
That reduces running times for Stryker by an order of magnitude.
The task here is to get those changes into this repo.
Acceptance Criteria
This is a "belt & suspenders" approach; the idea though is that the full mutation testing run happens after the PR is merged, as a backup safety run; it doesn't hold up the PR from getting merged.
Implementation Todos
See these two PRs:
Please see what they did there, and adapt it for this repo.