Setup GitHub action that verifies new e2e tests are written with every new feature

[cortisiko]

What is this about?

We want to have an automated check in place to prevent engineers from merging new features without adding new tests (unit, e2e, api, etc.). This check would encourage engineers to include new tests alongside new features proactively.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

• [ ] Engineering (needed in most cases)
• [ ] Design
• [ ] Product
• [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• [ ] Security
• [ ] Legal
• [ ] Marketing
• [ ] Management (please specify)
• [ ] Other (please specify)

References

No response