This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Deployment checks (manual QA)
Sue-Ann Ma edited this page Feb 6, 2018
·
7 revisions
Quick QA checks that should be manually applied before deploying code to QA and Staging:
Significant changes made to QA:
- navigate to QA: https://matheditor-QA.diagramcenter.org/
- select a problem from the page (e.g., problem #2)
- in the "my work" section, modify the math text box by adding in a fraction equation and your keyboard; type an annotation, then select "add step"
- in the "my work" section again for the next step, make sure the cross out/replace/calc functions all work, add a dictated annotation, then select "add step"
- select "add step" again (without making any changes)
- then use the trashcan to delete the last step in the history section, then try to "undo" to bring back the deleted step
- once the above is confirmed and working, notify the rest of the core team by email about the deployment
- someone else (not the person who just checked in code) runs through steps 1-6 above, validating changes and reporting any new bugs that may have emerged
- If needed, request deployment to Staging (https://matheditor-staging.diagramcenter.org/) only after a second person has validated the code in QA
note: the entire sequence of steps 1-8 should be completed before another round of code is checked in