Spaces:
Sleeping
Sleeping
Commit ·
457d89f
1
Parent(s): eb75418
docs(qa): add 5-minute smoke test runbook for pre-deploy checks
Browse files
docs/END_TO_END_QA_CHECKLIST_SPRINT4.md
CHANGED
|
@@ -5,6 +5,55 @@ Status legend:
|
|
| 5 |
- FAIL = behavior not validated
|
| 6 |
- BLOCKED = could not validate due to environment/tooling limitation
|
| 7 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 8 |
## Scope
|
| 9 |
This checklist validates Sprint 4 multi-project security flow:
|
| 10 |
- Login and session creation
|
|
|
|
| 5 |
- FAIL = behavior not validated
|
| 6 |
- BLOCKED = could not validate due to environment/tooling limitation
|
| 7 |
|
| 8 |
+
## 5-Minute Smoke Test (Pre-Deploy)
|
| 9 |
+
|
| 10 |
+
Use this quick run before each deploy or before a manual retest cycle.
|
| 11 |
+
|
| 12 |
+
### A. Start and Health (about 1 min)
|
| 13 |
+
1. Start app (use a free port if 7860 is busy).
|
| 14 |
+
2. Open local URL in browser.
|
| 15 |
+
3. Confirm app loads all tabs.
|
| 16 |
+
|
| 17 |
+
Pass criteria:
|
| 18 |
+
- App boots without traceback.
|
| 19 |
+
- Home screen renders Login, Select Project, Admin, and Validation tabs.
|
| 20 |
+
|
| 21 |
+
### B. Auth and ACL Core (about 2 min)
|
| 22 |
+
1. Login as validator_demo.
|
| 23 |
+
2. Open Select Project tab and verify only allowed projects are shown.
|
| 24 |
+
3. Open Admin tab and verify access denied with hidden controls.
|
| 25 |
+
4. Switch user to admin_user.
|
| 26 |
+
5. Open Admin tab and verify controls are visible.
|
| 27 |
+
|
| 28 |
+
Pass criteria:
|
| 29 |
+
- validator_demo sees only demo-project and kenya-2024.
|
| 30 |
+
- validator_demo cannot use admin actions.
|
| 31 |
+
- admin_user can see admin controls.
|
| 32 |
+
|
| 33 |
+
### C. Critical Admin Action (about 1 min)
|
| 34 |
+
1. As admin_user, create a temporary project using slug/name/repo id.
|
| 35 |
+
2. Click refresh project list.
|
| 36 |
+
3. Verify new slug appears in project list.
|
| 37 |
+
|
| 38 |
+
Pass criteria:
|
| 39 |
+
- Project creation returns success message.
|
| 40 |
+
- New project appears in list/dropdown immediately.
|
| 41 |
+
|
| 42 |
+
### D. Validation Readiness (about 1 min)
|
| 43 |
+
1. Select an authorized project.
|
| 44 |
+
2. Open Validation tab.
|
| 45 |
+
|
| 46 |
+
Pass criteria:
|
| 47 |
+
- Status changes to ready for selected project.
|
| 48 |
+
- Message "Projeto nao selecionado" no longer appears after valid selection.
|
| 49 |
+
|
| 50 |
+
### Smoke Evidence (copy/paste)
|
| 51 |
+
1. Date/time:
|
| 52 |
+
2. Tester:
|
| 53 |
+
3. Build/commit:
|
| 54 |
+
4. Result: PASS | FAIL
|
| 55 |
+
5. Notes:
|
| 56 |
+
|
| 57 |
## Scope
|
| 58 |
This checklist validates Sprint 4 multi-project security flow:
|
| 59 |
- Login and session creation
|