Execute test scripts in TestFactors, record pass/fail results in real time, and log defects inline without breaking your testing flow.
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.
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)
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.
Executions tab with My Executions filter active showing 7 scripts assigned to current user.
2
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)
Execution view opening on Step 1 of 8 with the script header at top and step content below.
3
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
A single execution step showing action, test data table, expected result, and the four status buttons.
4
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”)
Step with two screenshots attached and a note describing slow load time.
Even passing steps benefit from one screenshot at a key moment — it’s evidence for audit and a baseline for future regression.
5
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
Add the actual result (“Wizard error: ‘Position is required’ but Position was filled in”) and click Log defect.The defect is created, linked to this execution and step, and assigned per your project’s defect routing rules.
Defect form sliding in from the right with auto-populated fields after clicking Fail.
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.
6
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)
Execution view at step 5 of 8 with the 'Mark remaining as Blocked' option in the dropdown.
7
Complete the execution
When the last step is recorded, the script’s execution moves to Completed. You’ll see a summary:
Steps passed / failed / blocked / skipped
Time elapsed
Defects logged
Attachments uploaded
Execution summary screen with metric tiles and a 'Move to next script' button.
Done. Your manager sees the result instantly on the cycle dashboard. Move to the next assigned script or take a break.
The developer fixes the issue in SF and updates the defect status. You’ll see a notification.
2
Open the original execution
Click the execution row in the Executions tab.
3
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.
Execution detail header with 'New Execution' button creating version 2.
4
Run through the failed steps
You can either re-run the full script (recommended for confidence) or jump straight to the failed steps from before.
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
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
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
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
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
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)
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.”
