imbahub
Menu +
US
Talk to us
IMBAHUB / Knowledge & guides

Test the combinations an ordinary walkthrough misses.

Completing a configurator does not establish that its conditions work. Write a focused rule register and test valid, invalid and unknown combinations. Then check that customer summaries and received inquiries reflect the same approved rules.

Four failures despite individually valid fields
  1. Dependency

    Each option exists but their combination is prohibited.

  2. Boundary

    A permitted quantity uses the wrong boundary rule.

  3. Version

    Summary and receiver use different rules.

  4. Unknown

    A missing rule becomes an apparently exact result.

Check combinations and rule versions as well as individual fields.

Every field validates, but the extra requires a different primary choice. Accepted?

No. Formally valid values can be commercially invalid together. Check the dependency in both the customer flow and the receiver.

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.

ExerciseQuestionExpected evidence
Exact boundaryIs the limit inclusive or exclusive?Follows the documented business rule
Just outside the limitIs correction or review clear?No silent invalid acceptance
Changed primary choiceAre dependent options rechecked?No stale options in the brief
Unknown conditionIs uncertainty handled explicitly?Review without an invented amount
New rule versionWhich 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 authorized 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 labeled test inquiry 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 inquiry a binding quotation.

Sources and further reading

Questions, answered

Must we manually test every possible combination?

Prioritize boundaries, dependencies and approved reference cases. Large combination sets need a considered sample and appropriate automated checks.

What if a combination has no rule?

Treat it as unknown and provide a next step. Do not assume it is permitted or that its price is zero.

IMBAHUB

Let’s plan your website

Choose five reference cases with approved expected results and compare both summary and received inquiry.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.