ATF Tests Work in Classic UI but Fail in Service Operations Workspace (SOW)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2025 09:37 AM
Hi everyone,
I’m facing an issue with Automated Test Framework (ATF) tests for an Outage on Service Operations Workspace (SOW). The tests execute successfully in Classic UI but fail in the workspace, even though I’ve explicitly set the form UI context to SOW.
Details:
ATF Test Scenario for sow:
Open an existing Outage record (OUT0001410).
Set field values (e.g., Type, Short Description) and validate visibility of fields like Change State/Incident State based on the Type selected.
Problem:
Tests pass in Classic UI but fail in SOW with unclear errors.
Questions:
Are there known differences in ATF behavior between Classic UI and Workspaces?
Are there best practices for writing ATF tests in workspaces (e.g., context, selectors)?
Any insights or examples of working ATF tests in SOW would be greatly appreciated!
Thank you !
Regards
Kaoutar

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2025 03:10 PM
I was able to get passed this by clicking on the add all errors to the ignore list.