Make the rules independently checkable
Each rule needs an owner, version, condition and expected outcome. Choose reference cases approved by the business in advance. The developer's current calculation should not supply its own answer key.
Fictional example: installation is selectable for one equipment combination, while unusual dimensions require review. Record permitted, prohibited and unresolved cases. Do not insert an invented amount when pricing evidence is absent.
Change the primary choice after selecting extras
Choose a valid primary option and a dependent extra. Switch to a primary option for which that extra is invalid. Check the interface, summary and receiving service. Exercise backward and forward navigation as well.
If a choice is removed, users should understand why. Valid contact details should not need re-entry without reason. A hidden value that is still submitted is a different failure from a visible validation message.
| Exercise | Question | Expected evidence |
|---|---|---|
| Exact boundary | Is the limit inclusive or exclusive? | Follows the documented business rule |
| Just outside the limit | Is correction or review clear? | No silent invalid acceptance |
| Changed primary choice | Are dependent options rechecked? | No stale options in the brief |
| Unknown condition | Is uncertainty handled explicitly? | Review without an invented amount |
| New rule version | Which rules apply at submission? | Summary and receiving service remain consistent |
Test number formats and receiving validation
Try an empty value, zero where relevant, approved minimum and maximum values and reasonable decimal inputs. Decide how units and number formatting work in the selected language. Visible text and the normalised value must mean the same thing.
In an authorised test environment, the developer should demonstrate that the receiver rejects prohibited values even without browser checks. A total submitted by the browser must not alone determine an authoritative amount. This exercise concerns your test data and systems.
Change rules while a test workflow is open
Open the workflow under a recorded rule version, then change a relevant rule in the test environment before submission. Should the old rules remain applicable, or is revalidation required? The business must decide; users need a truthful explanation if their summary changes.
Follow a labelled test enquiry to the intended recipient. Compare choices, units, any approved pricing inputs, version and exceptions. Record differences, owner and retest. Passing does not prove future commercial outcomes or make the enquiry a binding quotation.