You're viewing legacy documentation for API Fortress (deployed via an on-premises container).
To view documentation for the new SaaS version of API Fortress — now known as Sauce Labs API Testing and Monitoring (with Sauce Connect tunnels) — see
API Testing on the Sauce Labs Cloud
We’ve been asked this question a few times so we wrote a post to make it clear.
When you work on a test you are not editing the actual test, but a working copy (a clone) of the test. The working copy can be edited, reset, and saved to continue the work later, but none of these actions alter the state of the live test.
When you’re done editing you will need to PUBLISH
the test so that the working copy replaces the current live test to become official.
Well, API Fortress is meant to alert people when something goes wrong. If you are editing a test and an incomplete test runs based on the schedule, you will receive a failure notification. A false positive.
By using the working copy to make your edits, the scheduler will not execute a test unless it is finalized and published.
- You don’t edit the live test. When you edit one, you’re actually editing the working copy.
- If you want to start over from the live test you can ‘Clear Working Copy’ to create a fresh version of the live test that you can edit.
- When you are done editing click ‘Publish’ so your working copy goes live and the scheduler will use this new test for its executions.
- If you create a new test but never publish it, the test will be marked as ‘incomplete.’