Skip to main content

​
Ways to write tests

Video to step generation

Drop in a video file, or paste a Loom Recording Link and Spur generates the test steps for you.

Writing steps manually

Write your tests yourself, step by step. Useful for trickier flows, or high-level tests.

Script to step generation

Upload a script and Spur creates the test steps.

​
Creating your test

1

Fill in basic test information

Start with the essential details:
New Test dialog with Test Name and Test Suite fields
  • Test Name: Give your test a clear, descriptive title for internal organization
  • Test Description: Add detailed context about the test’s purpose
  • Test URL: The starting URL of your test (complete path, e.g., https://your-domain-name.com)
Set the viewport after you create the test, in the test side peek. See Viewports.
2

Configure test settings

Set up your test configuration:
Test configuration section showing authentication options
  • Login State & Browser Cookies:
    • Use a saved session: Pick a session saved by another test to skip login
    • Save this session: Other tests can start where this one ends
Using a custom authentication setup? Contact support if you get stuck.
  • File Upload Configuration:
    • Include files for upload: Add files needed during test execution
  • Caching Options:
3

Add dependencies and teardowns

Configure test prerequisites and cleanup:Dependencies
  • Select tests that need to run before your test
  • Dependencies are recursive - if your selected test has dependencies, they’ll be included
Teardown Tests
  • These run at the end to reset your application state
  • Example: If your test uploads a file, the teardown should delete it
  • Mark tests as teardown tests to make them available for other tests

​
Set up teardown tests

Always set up appropriate teardown tests to maintain a clean test environment
4

File uploads

For tests requiring file uploads:
  • Specify the files needed for the test
  • Upload up to 20 files per test, with a total size of up to 50 MB
  • Ensure proper file paths and permissions
File upload capability is essential for completing tests that interact with file inputs

​
Best practices

  1. Clear Naming: Use descriptive names for your tests
  2. Proper Verification: Include VERIFY statements for critical checkpoints
  3. Clean Teardown: Always include cleanup steps
  4. Modular Design: Break complex flows into smaller, reusable tests
  5. Proper Dependencies: Configure test dependencies correctly

​
Next steps

Ready to run your test? Learn how to run and monitor your tests.