As a developer of notify, I want to be confident that our changes do not affect the front end of notify so that we can deliver a better product with increased velocity.
WHY are we building?
Currently all of our pipeline testing focuses on the back end of the system. It would be good to have the cypress accessibility tests and other front end testing implemented so we can catch problems such as the cache invalidation issues for assets.
WHAT are we building?
As a first step, we can add the cypress tests that Andrew has written into our github actions. We can then look at expanding these to do general user testing.
VALUE created by our solution
Close to the business, what's the value?
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Description
As a developer of notify, I want to be confident that our changes do not affect the front end of notify so that we can deliver a better product with increased velocity.
WHY are we building?
Currently all of our pipeline testing focuses on the back end of the system. It would be good to have the cypress accessibility tests and other front end testing implemented so we can catch problems such as the cache invalidation issues for assets.
WHAT are we building?
As a first step, we can add the cypress tests that Andrew has written into our github actions. We can then look at expanding these to do general user testing.
VALUE created by our solution
Close to the business, what's the value?
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Privacy considerations
Security controls in place
Measuring success and metrics
QA Steps