Thomas Eapen · Selected work

Testing changes before release

An illustrative workflow and sample matrix for making expectations, differences and retests visible.

Illustrative example · invented cases and resultsOne-page print edition · A3 landscape

Illustrative testing example · invented cases and results

Make each check explainable

Keep the expectation, observation and follow-up together.

Define, run, record, investigate and retest Illustrative testing workflow. Define the expected result, run a case in an example environment, record the observation, investigate differences and retest after refinement. The return path repeats affected checks. No historical test outcomes are shown. Repeat affected checks after refinement 01 Define State the expectedresult 02 Run Use an isolatedexample 03 Record Capture theobservation 04 Investigate Explain anydifference 05 Retest Check thecorrection
Define, run, record, investigate and retest Illustrative testing workflow. Define the expected result, run a case in an example environment, record the observation, investigate differences and retest after refinement. The return path repeats affected checks. No historical test outcomes are shown. Repeat affected checks after refinement 01 Define State the expected result 02 Run Use an isolated example 03 Record Capture the observation 04 Investigate Explain any difference 05 Retest Check the correction

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.

Four invented checks · an intentional mismatch followed by its retest
ActionWorkingIssueEnvironmentStatus
T01Try an enabled activity with its required skillProfile A → Activity 1Expected: allowed · Recorded: allowed YesNo issue in this example.Example sandboxPass
T02Try an enabled activity without its required skillProfile B → Activity 3Expected: blocked · Recorded: allowed NoRequired-skill check needs correction.Example sandboxReview
T03Retest T02 after the illustrative correctionProfile B → Activity 3Expected: blocked · Recorded: blocked YesThe earlier issue is resolved in this invented result.Example sandboxRetest passed
T04Disable an activity while keeping the required skillProfile A → Activity 2Expected: blocked · Recorded: blocked YesNo issue in this example.Example sandboxPass

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.