# TC-010: Mixed-status filters remain correct after refresh

**Design origin:** Learner-authored steps and expected task groupings for a coached scenario. Review added explicit environment, counts, and preservation assertions.  
**Requirements:** REQ-07 (Completed status persists), REQ-09 (exact status filtering), and related REQ-08 (fields remain unchanged).  
**Run:** RUN-012. **Status:** Pass, October 14, 2026.  
**Environment:** TaskFlow release 1.3, Chrome on Windows desktop; browser version not recorded.

## Learner's submitted design

The learner proposed selecting In progress, completing the A-title task, capturing the remaining In progress tasks, selecting Completed and capturing the A-title task, then refreshing and capturing both filtered views again. They expected prepare speaker badges and Workshop 1 setup to remain In progress, while the A-title task appears as Completed.

## Preconditions

Confirm release 1.3 and the existing RUN-011 fixture: three In progress tasks, no new records added. Workshop 1 setup is Medium, Unassigned, with no date; prepare speaker badges is High, assigned to Mia Chen, due 2026-11-15; the existing 50-character A-title is Medium, Unassigned, with no date.

If your current data differs, record the changed setup before judging outcomes. This case assumes the same three saved records throughout.

## Reviewed procedure

| Step | Action | Expected result |
| --- | --- | --- |
| 1 | Select release 1.3 and Show status In progress; inspect the setup. | All three starting tasks are In progress; 3 shown / 3 total. |
| 2 | Click Complete on the A-title task. | That task changes to Completed and leaves the In progress view; the other two stay In progress. No task is deleted or created. |
| 3 | Capture the In progress view. | Only Workshop 1 setup and prepare speaker badges appear, both labeled In progress; 2 shown / 3 total. The A-title is excluded. |
| 4 | Select Completed and capture its view. | Only the A-title task appears, labeled Completed; 1 shown / 3 total. The two In progress tasks are excluded. |
| 5 | Refresh, confirm release 1.3, select In progress, and capture. | The same two tasks and fields appear; 2 shown / 3 total. |
| 6 | Select Completed and capture. | The same A-title task remains Completed with unchanged fields; 1 shown / 3 total. |

Across the screenshots, title, priority, assignee, and date remain unchanged for each task. Completing the A-title changes only its status. Total records stays three.

## Evidence to collect

Four screenshots: In progress before refresh, Completed before refresh, In progress after refresh, and Completed after refresh. The paired views establish matching records are included and nonmatching records excluded.

Suggested filenames: `RUN-012_TC-010_v1.3_in-progress_before.png`, `RUN-012_TC-010_v1.3_completed_before.png`, and corresponding `_after.png` files.

## Execution record

- Actual setup: RUN-011 established three In progress tasks. The learner reported completing the A-title task for this run.
- In progress before/after: Only Workshop 1 setup and prepare speaker badges, each In progress; 2 shown / 3 total.
- Completed before/after: Only the A-title task, Completed; 1 shown / 3 total.
- Fields: Workshop 1 setup remains Medium, Unassigned, no date; badges remains High, Mia Chen, 2026-11-15; A-title remains Medium, Unassigned, no date. Titles unchanged; total remains three.
- Verdict: **Pass** based on the learner report and all four supplied screenshots.

Evidence:

- [In progress before refresh](../evidence/session-08/RUN-012_TC-010_v1.3_in-progress_before.png)
- [Completed before refresh](../evidence/session-08/RUN-012_TC-010_v1.3_completed_before.png)
- [In progress after refresh](../evidence/session-08/RUN-012_TC-010_v1.3_in-progress_after.png)
- [Completed after refresh](../evidence/session-08/RUN-012_TC-010_v1.3_completed_after.png)

The learner report identifies refresh between the paired states. This run checks inclusion and exclusion using mixed statuses, and persistence for the recorded fixture. It does not establish every browser, status combination, or accessibility behavior.

This is one workflow test with several assertions, not four executed tests merely because four screenshots are planned. Keep design provenance and any later run evidence linked here.