MODULE 14 · Skill training · 105 MINUTES

Digital innovation, user journeys, and quality assurance

Learn the principle. Practice the work. Preserve what you learn.

Your learning goals

Translate a program need into a bounded digital improvement.
Test complete user journeys with synthetic information.
Write reproducible defect and verification records.

Preparation

Start with the user journey

Digital innovation supports a specific person completing a useful task. Describe the starting point, intended action, expected result, and information needed. For a Q45 learning module, the journey might be finding the correct lesson, reading an example, completing a quiz, and locating the existing submission route. Separate the user-facing purpose from the implementation details. Identify the intended public, participant, and administrative surfaces. Reuse the existing site and approved systems so the improvement connects with current content and records. A prototype can explore a design, while a deployed feature requires its own implementation and verification evidence.

Test behavior and boundaries

Use clearly labeled synthetic records for testing. Check direct page loading, navigation, links, forms, validation, loading states, success states, error recovery, keyboard access, and mobile layout. A save test should verify that the record exists in the intended durable system and that the intended person can retrieve it under the established access rules. A local screen update alone is weaker evidence. Test the access boundary relevant to the feature: one participant’s record should remain within its authorized scope, and administrator functions should use the existing server-enforced permissions. Intern exercises document these requirements and tests within assigned access; actual access changes and deployment follow the project’s authorized workflow.

Make defects reproducible and changes reviewable

A defect record contains the route, environment, preconditions, steps, expected result, actual result, impact, and supporting evidence. Include a proposed severity based on the effect on the user, then record the repair and repeated check. Preserve existing routes, content, assets, data, identity, and access when proposing an addition. A useful release record names the source version, changed surfaces, tests passed, tests pending, and actual deployment state. Distinguish built, previewed, published, and verified working. For visual work, inspect the actual interface at representative sizes and correct overflow, unreadable text, awkward crops, or inaccessible controls. Keep the continuation notes clear enough for another contributor to reproduce your findings.

Worked example

title

Worked example: a quiz submission issue

body

Synthetic test: a learner selects all quiz answers and presses “Submit.” The page displays a score, but a reload loses the result. The defect record states the exact route, steps, expected persistence requirement, actual behavior, and consequence. If the feature is intentionally practice-only, the interface should explain that state. If durable progress is required, implementation and retrieval tests must establish it. The test record avoids claiming a permanent completion record based solely on the visible score.

Your practical assignment

Create a digital improvement and QA packet

Map a fictional module journey with public learning content and a private submission boundary.
Write five acceptance criteria tied to user actions.
Create 12 tests covering navigation, forms, states, accessibility, mobile behavior, and access.
Execute the tests available in the assigned environment or label them as planned where access is pending.
Write two reproducible fictional defect records and a release-status summary.

Evidence to prepare

A user journey and five acceptance criteria.
A 12-case test matrix with actual states.
Two defect records and a release-status summary.

Assignment scoring guide

Use these criteria for self assessment and feedback. Each criterion contributes 25 points to the 100-point assignment rubric.

Criterion	Points	Evidence
User value	25	The improvement addresses a specific learner need.
Test quality	25	Cases cover meaningful behavior, states, and boundaries.
Reproducibility	25	Defect records contain enough detail to repeat the issue.
Evidence discipline	25	Build, preview, publication, persistence, and acceptance claims match observations.

Reflection

Which test would reveal the most consequential failure in your proposed feature?
How will your record distinguish a planned check from an executed check?

Scoring and revision guidance

Evidence is absent or cannot be assessed.

Limited evidence; substantial guidance and revision are needed.

Partially demonstrated; a material element needs revision.

The essential requirement is met; minor corrections remain.

Complete, accurate, traceable, and usable evidence for the criterion.

Review the explanation for each missed question, revisit the relevant lesson, and retry. Revise practical work against the rubric and document the change.