How to generate a test plan
  1. Drop in your requirements (Word, PDF, CSV, text or Markdown, up to 3 files) and the XFP form export (.zip). Each file is sorted automatically. If one is sorted wrongly, change it with Use as.
  2. Select Generate plan. It takes a couple of minutes.
  3. Review the plan, use Adjust and regenerate to steer it, then download the .xlsx.

Everything else is optional and under More options.

Add your files

Requirements and the XFP form export

Drag files here or . Requirements (Word, PDF, CSV, text) and the XFP export (.zip) are sorted automatically. You need at least one of them.

No files added yet.
    More options

    All optional. Other files (a CXM export, HTML form, Playwright export or code file) can go in the drop area above.

    Base stepsSteps added to the start or end of every test case
    Base steps to add to every test case

    Manage the sets on the Base steps tab.

    Steer the generatorNotes and the AI model
    For example, focus on a branch or ask for more checks on a field. It only works within your files: it cannot add fields, requirements or outcomes that are not in them.
    Both cover the same use cases. The model used is recorded on the plan.
    FormWhich UAT form this plan is for
    Sets the form ID on the plan. The form export still goes in the drop area.
    Never updated
    More form detailsType a form ID or live link yourself
    Integration codeA GitHub repository to ground failure paths
    Read-only.
    Leave blank to use the whole repository.
    CXMCase type, and sign-in and checking steps
    A saved copy of the CXM list. Use “Sync case types” to refresh it.
    Last synced: never
    Raised inside CXM

    For a service raised inside CXM, every test case gets CXM sign-in steps at the start and checking steps at the end, in a test environment only, using built-in fictional test customers.

    Leave unticked to let the tool decide from a CXM export.

    Base steps

    Example sets follow the usual CXM test script: sign in, find the test customer, start the case, then check CXM and the back-office system. They are written with template variables and none is used until you tick it. Sets you already have, including archived ones, are not added again.

    Steps added to the start or end of every test case, such as signing in to CXM or logging out. Each set also has Playwright steps, so automated runs can do them without generating anything. You choose which sets a plan uses under More options when you generate it.

      Template variables

      Write {{name}} in base steps and test cases instead of typing the value. When a value changes, change it once here and every plan, base step, automated run and export uses the new one.

      Shared variables

      Shared variables. A variable with no value stays as {{name}} so you can see it is not set.
      NameValueNoteRemove

      Test customers

      Fictional or agreed test customers that exist in UAT CXM. Each test case uses one, so cases are spread across them. Use {{customer_name}}, {{customer_address}}, {{customer_postcode}}, {{customer_email}} and {{customer_phone}}.

      Test customers, lettered in order
      CustomerNameAddressPostcodeEmailPhoneRemove

      Built in

      • {{form_id}} and {{service_name}} come from each plan.
      • {{sso_email}}, {{sso_password}}, {{cxm_username}}, {{cxm_password}} and {{xfp_host}} are filled in only by automated runs, from their own secure settings. They are never shown or saved here.

      Plan library

      Matches the plan name or form title. Case-insensitive; part of a word is enough.
      Only set on newer plans. Use the plan name above if this finds nothing.

      Loading plans…

      What this test plan covers

      This test plan covers every eventuality mentioned in the requirements, augmented with cases discovered from the form structure and integration code. It does not claim to cover every real-world eventuality. Anything the requirements do not mention, and that the form and code do not reveal, will not appear here. Use the flagged gaps and conflicts to decide where human judgement is still needed.