AI test planning and knowledge guidelines

AI-assisted planning combines change intelligence, requirement baselines, and authorised project context into editable test-plan drafts. It helps teams select and justify coverage; accountable project roles retain ownership of the final plan and approval.

Change intelligence and baselines

Change manifests and path mappings describe which product areas a change may affect. Requirement baselines make later differences and maintenance impact easier to review.

• Keep mappings as narrow as possible and investigate unknown or ambiguous paths.
• Compare new results with the correct versioned baseline.
• Separate proven impact, plausible inference, and areas that cannot be assessed.
• Update change intelligence when repository structure or domain ownership changes.

Edit and hand off test-plan drafts

1. Create a draft in the AI test-planning area and select the intended domain scope.
2. Review proposed tests, priorities, rationale, dependencies, and identified gaps.
3. Edit and save a new draft version instead of overwriting earlier decisions.
4. Export the reviewed version or hand selected items to the next planning workflow.
5. After hand-off, verify which project objects were actually created or assigned.

A draft is not an approved test plan. Project data changes only through a confirmed domain action.

Prepare a test-plan draft

Open AI test plans with an authorised administrator or project-manager role. Describe the objective and scope, test types, environments, risks, assumptions and entry/exit criteria. Add the relevant sources and packages. Specific input makes it easier to assess the generated draft.

After generation, check for missing requirements, unrealistic assumptions and untested environments. Save the edited version and use Markdown export for discussion where needed. The draft does not replace configuring and approving the executable test plan.

Narrow the selection for a run

Start AI test selection from the test-runs area. Provide release context, a change manifest, relevant requirements and the available budget. Review proposed planned cases, their rationale and omitted areas. Hand only the reviewed selection to run start, then check the plan, environment and scope again.

A limited budget can create deliberate coverage gaps. Record those gaps in the domain approval instead of treating the selection as complete evidence.

Maintain knowledge guidelines

Global and project-level knowledge guidelines provide approved terminology, constraints, and working rules. Project guidelines supplement global rules; they do not replace permissions, data zones, or scenario approval.

• Write short, testable guidelines with an explicit scope.
• Assign them only to relevant scenarios and approved provider profiles.
• Version and review guidelines after process, product, or compliance changes.
• Do not store secrets or unnecessary personal data in a guideline.