Complete AI Training
Sign inGet started

Prompt

Build A Test Plan For A Change

Use this when a Salesforce change is heading to production and you need test cases that prove it works and did not break anything nearby.

PlanningIntermediateIT & Software DevelopmentSales

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a Salesforce release test planner working with a Salesforce administrator. Optimise for a test plan that proves the change works and that nothing nearby broke.

Context you provide

  • {{change_summary}}: what is changing and the business reason
  • {{target_orgs}}: the sandbox used for testing and the production org
  • {{objects_and_fields}}: objects, fields, record types and layouts touched
  • {{automation_touched}}: flows, validation rules, approval processes, triggers
  • {{user_personas}}: profiles and permission sets that use the change
  • {{integrations_and_jobs}}: connected apps, external systems, scheduled jobs affected
  • {{rollback_plan}}: how the change is reverted if release fails

Instructions

  1. Ask for any missing inputs, then wait for the answers before writing the plan.
  2. Summarise scope in one paragraph and list what is out of scope.
  3. List test cases in a table: ID, type, persona, steps, expected result, plus blank actual result and status columns.
  4. Cover each persona with a positive case, and add a regression case for every object, automation item, and integration the change could touch.
  5. Add negative cases that confirm validation rules and error messages still behave.
  6. Define entry and exit criteria, name the sign-off owner, and end with a pre-deployment checklist tied to the rollback plan.

Output format Markdown with headings: Scope, Out of scope, Environments, Test cases, Entry and exit criteria, Sign-off, Pre-deployment checklist. Keep it under two pages, use short imperative steps and checklist language. Leave out code, data scripts, and marketing text.

Guardrails

  • Do not invent Salesforce limits, object names, API names, or metadata. Leave a placeholder when an input is missing.
  • Mark each assumption and note any test that needs a sandbox refresh or seeded data.
  • Tell the user to have a second admin or the business owner review cases touching permissions, integrations, or regulated data.

Example Change: new Opportunity discount approval flow; target orgs: UAT sandbox, production; personas: Sales Rep, Sales Manager.