Thomas Eapen · Selected work
Testing changes before release
An illustrative workflow and sample matrix for making expectations, differences and retests visible.
Illustrative testing example · invented cases and results
Make each check explainable
Keep the expectation, observation and follow-up together.
These cases exercise the conceptual mapping example: an activity must be enabled and its required skills present.
Scroll horizontally to compare the five matrix columns.
| Action | Working | Issue | Environment | Status |
|---|---|---|---|---|
| T01Try an enabled activity with its required skillProfile A → Activity 1Expected: allowed · Recorded: allowed | Yes | No issue in this example. | Example sandbox | Pass |
| T02Try an enabled activity without its required skillProfile B → Activity 3Expected: blocked · Recorded: allowed | No | Required-skill check needs correction. | Example sandbox | Review |
| T03Retest T02 after the illustrative correctionProfile B → Activity 3Expected: blocked · Recorded: blocked | Yes | The earlier issue is resolved in this invented result. | Example sandbox | Retest passed |
| T04Disable an activity while keeping the required skillProfile A → Activity 2Expected: blocked · Recorded: blocked | Yes | No issue in this example. | Example sandbox | Pass |
Follow the issue: T02 records an unexpected allowance. T03 repeats the same case with an invented corrected observation.
What the matrix keeps visible The action, whether it worked as expected, the issue to investigate, the environment and the outcome.
Illustration only Expected decisions come from the invented rule model. Recorded observations are authored examples, not results from a software test run.