Documentation Index
Fetch the complete documentation index at: https://docs.testfactors.com/llms.txt
Use this file to discover all available pages before exploring further.
This is where the work actually happens. Test Execution is designed to keep you in flow — minimal clicks, real-time progress for your team, and one-click defect logging without leaving the script.
What this module does
A test execution is a single run of a test script against the SuccessFactors environment. You step through the script, record what happened at each step, and the execution captures:- Pass / Fail / Blocked / Skip status per step
- Actual results (what really happened, if different from expected)
- Attachments (screenshots, logs, screen recordings)
- Defects linked back to the failing step
- Timing (auto-tracked)
- Tester notes
Who uses this module
| Role | Execute | Re-execute | Review results | Assign executions |
|---|---|---|---|---|
| Tester | Yes (assigned) | Yes (own) | Own | No |
| Test Coordinator | Yes | Yes | All | Yes |
| Test Manager | Yes | Yes | All | Yes |
| Project Manager | Yes | Yes | All | Yes |
| Module Process Owner | Yes | Limited | Module-scoped | No |
| Developer | Yes (defect verification) | Limited | Yes | No |
| Viewer | No | No | Yes (read-only) | No |
Before you start
You need:- Active scripts in your project. See Test Scripts.
- A test cycle — the container for this round of execution (e.g. “Q2 2026 UAT”, “Smoke Test — Sandbox Refresh”).
- Assignments — the Test Coordinator assigns scripts to testers. If you don’t see any assignments, ask your Coordinator to assign you.
Step-by-step: execute a test script
Open the Executions tab
From your project’s left sidebar, click Executions. You see all test executions in the active cycle.Switch to My Executions to filter to just what’s assigned to you.
Pick a script
Click any script row. The Execution view opens — a focused, distraction-free layout.Top of the view:
- Script title and metadata (scenario, test case, SF module)
- Progress bar (steps completed / total)
- Status (In Progress / Completed)
Step through the script
For each step:
- Read the action (“Open the Hire Wizard from People → Add New”)
- Read the test data (a table with the values to enter)
- Read the expected result (“Wizard advances to Step 2”)
- Do it in SuccessFactors (separate window)
- Record what happened — click Pass, Fail, Blocked, or Skip
Add notes or screenshots (optional but encouraged)
For any step you can:
- Type a note (“Wizard took 6 seconds to load — slow but functional”)
- Drag-and-drop screenshots into the step
- Record your screen with the built-in capture button (great for “It worked but looked weird”)
If a step fails, log a defect immediately
Click Fail on a step. A defect form slides in from the right, pre-filled with:
- Title — drafted from the step’s expected vs actual
- Reproduction steps — auto-populated from all steps in this script up to and including the failed step
- Test data — copied from the failed step
- Severity — defaulted to Medium; adjust as needed
- Screenshots — anything you attached to this step
Logging defects in-line saves an enormous amount of time compared to “I’ll log them all at the end.” If you wait, you forget context. Log it the moment it fails.
Continue or stop
After each step is recorded, the next step loads automatically. You can:
- Continue through all remaining steps
- Mark the rest as Blocked if a critical failure prevents further testing
- Pause — save your progress and come back later (your status is preserved)
Done. Your manager sees the result instantly on the cycle dashboard. Move to the next assigned script or take a break.
Watching the cycle in real time (Coordinators / Managers)
While testers execute, the Cycle Dashboard updates live:- Progress bar per script (Not Started / In Progress / Completed)
- Pass rate per scenario, category, and SF module
- Defect count by severity (with one-click drill-in)
- Tester-by-tester progress and velocity
- Blocker queue (executions stuck on “Blocked” status)
Re-executing a failed script after a fix
Wait for the defect to be marked Resolved
The developer fixes the issue in SF and updates the defect status. You’ll see a notification.
Click 'New Execution'
The top-right has a + New Execution button. Click it. A fresh execution is created (version 2) linked to the same script and test case.Your previous execution stays intact for history.
Tips
Log defects inline, always
Don’t batch defect logging “for after.” Context is lost and your defect descriptions get vague. Inline = better defects = faster fixes.
Use the pause feature for interruptions
Mid-script meeting? Pause. Your progress is saved exactly where you left off, attachments included.
Capture screenshots even on Pass
One screenshot at the most important moment of each script. Future you (regression-testing the same flow) will thank present you.
Don't skip steps you 'know will pass'
Skipping creates audit gaps. Mark as Pass with a one-line note instead.
Use Blocked sparingly
Blocked = you literally cannot proceed. If you can work around it, mark Fail + log defect and continue testing the rest of the script.
Update your status visibly
If you’re stuck waiting on a defect fix, change your assignment status to “Waiting” so your Coordinator can reassign you.
Execution states
| State | Meaning |
|---|---|
| Not Started | Script is assigned but you haven’t opened it yet |
| In Progress | You’ve recorded at least one step |
| Paused | You explicitly paused; resume any time |
| Completed — Pass | All steps passed or skipped (no fails, no blocks) |
| Completed — Fail | At least one step failed |
| Completed — Blocked | Marked Blocked before finishing |
Troubleshooting
I don't see any scripts assigned to me
I don't see any scripts assigned to me
Three possibilities:
- The Coordinator hasn’t assigned scripts yet — message them
- Filter is on ‘My Executions’ and the cycle is new — switch to “All Executions” to see the full pool
- You’re in the wrong cycle — check the cycle dropdown at the top
I clicked Pass by mistake on a failed step
I clicked Pass by mistake on a failed step
Each step has a small undo button next to the status badge. Click Edit step result to change Pass → Fail. The defect form will appear.
My screenshot won't attach
My screenshot won't attach
Limits and tips:
- Max file size: 25 MB per attachment
- Accepted formats: PNG, JPG, GIF, MP4, WEBM
- If drag-and-drop fails, use the Upload button instead
- If still failing, save the screenshot to your desktop first, then upload — sometimes copy-paste from the clipboard gets garbled
The execution view crashed mid-script
The execution view crashed mid-script
Refresh the page. Your progress is auto-saved every 5 seconds — you’ll be back on the exact step you were on, with your in-progress note and attachments preserved.
I need to re-run a single failed step, not the whole script
I need to re-run a single failed step, not the whole script
Open the completed execution → step detail → Re-run this step. Records a new result for just that step without invalidating the rest.
My defect form is missing the SF module field
My defect form is missing the SF module field
The defect form pulls SF module from the script’s test case. If the test case doesn’t have an SF module tag, the form falls back to project default. Fix: ask your Test Coordinator to tag the test case.
I want to add a note to the cycle (not a specific step)
I want to add a note to the cycle (not a specific step)
In the Executions tab → cycle dropdown → Cycle notes. Notes here are visible to the whole project team and are great for “Sandbox refresh happened at 2pm — re-test affected scripts.”
Related guides
Test Scripts
Execution runs scripts — make sure they’re up to date before a cycle starts.
Defects
Defects logged inline during execution flow through to this module for triage and tracking.
Memberships & Access
Get the right people invited with the right roles so assignments work cleanly.
Settings
Configure defect routing rules and cycle templates per project.