Skip to main content
Test scripts are the ‘how to actually do it’ layer. Test cases say what to test; test scripts say click here, type this, verify that.

​
What this module does

A test script is a numbered playbook a human tester (or an automation tool) follows to execute one test case. Each step says:
  1. What to do (“Open the Hire Wizard from the People dropdown”)
  2. What to enter (“Use the test data shown below”)
  3. What to verify (“Confirm the wizard advances to Step 2 of 5”)
TestFactors generates scripts from your approved test cases, using:
  • The test case’s steps and expected results as the skeleton
  • The test case’s test data as concrete values
  • Your project’s script templates for consistent tone and format
  • Any automation hints (selectors, URLs, API calls) configured for the SF module
You can run scripts manually (a tester executes them in SuccessFactors) or feed them to your automation framework.

​
Who uses this module

​
Before you start

You need:
  • Approved (Active) test cases. See Test Cases.
  • (Optional) A script template if your organization uses one. Project Managers can configure templates per SF module. If none is configured, TestFactors uses a sensible default.

​
Step-by-step: generate a test script

1

Open the test case

From the Test Cases tab, click an Active test case. The detail panel includes a Scripts tab.
Test case scripts tab

Test case detail with Scripts tab visible (empty on first open).

2

Click Generate Script

The Scripts tab has a + Generate Script button. Click it.A side panel opens with options:
  • Template — pick the project’s template or “Default”
  • Audience — Manual tester or Automation framework
  • Detail level — Concise (~3–5 lines per step) or Verbose (full prose)
Generate script options

Generate Script options panel showing template, audience, and detail level controls.

3

Generate

Click Generate. The AI drafts the script in ~10–20 seconds. You’ll see it appear step-by-step in real time (streaming).
Script streaming

Script being generated, streaming new steps in real time.

4

Review and edit

Once complete, the script enters Draft state. Each step has:
  • Action — what to do (with the right level of detail)
  • Data — exact values to enter
  • Expected result — what should happen
  • Annotation slot — for tester notes during execution
Click any step to edit inline. Drag to reorder.
Script draft

Completed script with 8 steps in Draft state. One step is in inline-edit mode.

5

Promote to Active

Click Promote to Active in the top-right. The script is now ready for execution.Active scripts appear in the Test Execution flow (next module).
Promote script

Script header showing Promote button and the version dropdown.

You have a runnable script. Run it during the next test cycle — see Test Execution.

​
Customizing script templates (Project Managers)

If your team has specific conventions for how scripts should be written (tone, step numbering, screenshot requirements, etc.), set up a template once and every future script follows it.
1

Open project settings

Settings → Script Templates.
2

Create or edit a template

Click + New template or pick an existing one to edit.Fields:
  • Name — “EC Production Cutover”, “Sandbox Smoke Test”, etc.
  • SF Module — scope the template to a specific module, or “All modules”
  • Pre-amble — text that appears at the top of every script (e.g. “Run this in the QA sandbox only.”)
  • Step format — choose from presets or define your own with placeholders like {action}, {data}, {expected}
  • Post-amble — text at the end (e.g. “Document any defects in Jira project EC-QA.”)
3

Save and set default

Tick Set as default for this SF module if you want every script auto-generated for that module to use this template.
Script template editor

Script template editor with pre-amble, step format, and post-amble fields.

​
Tips

Generate for one cycle at a time

Don’t generate all scripts at once at project start — your test cases will evolve. Generate scripts when you’re about a week from executing.

Pick the right detail level

Concise for experienced testers who know SF well; Verbose for new hires or contractors.

Regenerate after test case edits

If you edit a test case, the existing script doesn’t auto-update — regenerate. There’s a “regenerate from current test case” button.

Use one template per SF module

Tone and detail level vary by module. EC needs more steps than Recruiting. Set defaults per module.

Add screenshots in execution, not generation

Don’t ask the AI to include “(take screenshot)” — testers add them naturally during execution. Keeps the script clean.

Document gotchas in the template, not each script

“Always disable browser autofill before this section” → put it in the template pre-amble once.

​
Script states

​
Troubleshooting

Regenerate with a different Detail level (Concise vs Verbose). Or edit the project template’s step format to your team’s preferred density.
The script was generated before you edited the test case. Click Regenerate from current test case in the script header.
The AI relies on your knowledge wiki for accurate UI paths. If the wiki doesn’t describe your current SF version’s navigation, the AI may use generic instructions. Add a short note to the wiki documenting the actual menu path, then regenerate.
Set up an export template in project settings → Scripts → Export Formats. TestFactors can render any active script in your tool’s format (CSV columns, XML, ALM-flavored).
The partial script is saved in Draft. Either:
  1. Edit the incomplete steps manually
  2. Click Resume generation to let the AI finish from where it stopped

Test Cases

Scripts are generated from test cases — start there.

Test Execution

Run your active scripts during a test cycle.

Defects

Log defects discovered while executing scripts.

Knowledge Wiki

Document SF navigation paths so scripts are accurate.