1. Mixing actions inside “verify” steps
1. Mixing actions inside “verify” steps
What happens:
Tests become semantically unclear or are misinterpreted.Bad example:
Tests become semantically unclear or are misinterpreted.Bad example:
- Actions = things the test does (e.g., click, scroll)
- Verifications = things the test checks (e.g., visible, present)
2. Non-Scenario Table tests in Scenario Table Test Suite
2. Non-Scenario Table tests in Scenario Table Test Suite
What happens:
Static tests placed inside a scenario table suite will execute once per scenario row, potentially causing duplicate confirmations or side effects.Bad example:
Keep tests that do not rely on scenario table variables in a separate test or suite. This prevents static verifications from running multiple times.
Static tests placed inside a scenario table suite will execute once per scenario row, potentially causing duplicate confirmations or side effects.Bad example:
Keep tests that do not rely on scenario table variables in a separate test or suite. This prevents static verifications from running multiple times.
3. Using “go to URL” inside test steps
3. Using “go to URL” inside test steps
What happens:
Spur can’t interpret
Spur can’t interpret
Go to URL commands mid-test, causing scripts to fail.Bad example:-
Set the Start URL in your test’s settings:
-
Use actions for in-test navigation:
What happens:
Tests may break or misinterpret intent if you attempt to change tabs or navigate the browser without using supported actions.What to do:
Use browser action steps for any tab or navigation changes. For example:
Tests may break or misinterpret intent if you attempt to change tabs or navigate the browser without using supported actions.What to do:
Use browser action steps for any tab or navigation changes. For example:
5. Scrolling
5. Scrolling
What happens:
The agent only interacts with elements in view unless instructed otherwise. Tests may fail to locate off-screen elements.What to do:
Explicitly include scroll steps before verifications or actions. For example:
The agent only interacts with elements in view unless instructed otherwise. Tests may fail to locate off-screen elements.What to do:
Explicitly include scroll steps before verifications or actions. For example:
6. Accessing restricted domains via Preview Editor
6. Accessing restricted domains via Preview Editor
What happens:
Direct navigation to restricted domains (e.g., spurmail.com, Spur’s built-in test inbox domain) may be blocked due to IP restrictions.What to do:
Access these domains through the Preview Editor. The Preview Editor proxies your requests through Spur’s infrastructure, so IP blocks don’t apply. When you run the test normally, the agent’s requests go through the same proxy and the steps execute successfully.
Direct navigation to restricted domains (e.g., spurmail.com, Spur’s built-in test inbox domain) may be blocked due to IP restrictions.What to do:
Access these domains through the Preview Editor. The Preview Editor proxies your requests through Spur’s infrastructure, so IP blocks don’t apply. When you run the test normally, the agent’s requests go through the same proxy and the steps execute successfully.