Test Plans
A Test Plan is an ordered selection of scenarios prepared for repeatable execution. AutoRunner's current user-facing term is Test Plan; older documentation may call the same backend concept a suite.
Create a plan
Open AutoRunner > Test Plans > New Test Plan and provide:
- a plan name;
- at least one scenario;
- the scenario execution order;
- an optional default Run Profile;
- an optional Environment Profile override; and
- optional run variables where offered.
The scenario selector can include scenarios from multiple sources in the active workspace. Verify the source beside each scenario before saving.
Plan actions
From the plan list, permitted users can:
- open plan details or its report;
- run immediately or run with a selected profile;
- edit, duplicate, or delete the plan; and
- start schedule creation for the plan.
Plan health, schedule, search, and sort controls help narrow a large workspace.
Execution defaults
A plan's default Run Profile is a convenience, not an immutable execution contract. A user can select another profile when starting a run, and a schedule can carry its own selections. Open the resulting Test Run to verify which profile, environment, runner, and trigger were actually used.
Cross-source plans
Cross-source scenario selection is available in the current frontend. Because repository refresh, workspace migration state, permissions, runners, and environments can differ between sources, validate the complete plan in the deployed environment before relying on a cross-source schedule.
Saving or editing a Test Plan does not produce a Test Run. Start a run and inspect its evidence before using the plan as a release signal.
Continue to Test Data, Test Runs, or Scheduling.
