When trying to run the E2E tests for the first time, some engineers encounter an issue where tests that utilize fixtures fail. After pairing with an engineer who ran into the problem, it became clear that IS_TEST was not picked up correctly.
To reproduce: It recommended pairing it with an engineer who never ran e2e tests on their PR.
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)
What is this about?
When trying to run the E2E tests for the first time, some engineers encounter an issue where tests that utilize fixtures fail. After pairing with an engineer who ran into the problem, it became clear that
IS_TEST
was not picked up correctly.To reproduce: It recommended pairing it with an engineer who never ran e2e tests on their PR.
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
References
No response