Stoobly Docs
  • Introduction
  • Use Cases
    • Generate Mock APIs
      • Empower Development
      • Scale API Testing
    • Enable E2E Testing
  • FAQ
    • Recording
    • Mocking
    • Terminology
  • Getting Started
    • Installing the Agent
      • Installation with pipx
      • Installation with Docker
  • Core Concepts
    • Agent
      • Intercept Modes
        • Mocking
        • Recording
      • Lifecycle Hooks
      • Proxy Settings
        • Data Rules
        • Firewall Rules
        • Rewrite Rules
        • Match Rules
    • Context
    • Mock API
      • Request
        • Response
        • Replay History
      • Scenarios
      • Snapshots
      • Fixtures
      • Public Folder
    • Scaffold
      • Service
      • Validation
      • Workflow
  • Guides
    • How to Run the Agent
      • Run with CLI
      • Run with Docker
    • How to Configure the Agent
      • Forward Proxy
        • Enable HTTPS Traffic
      • Reverse Proxy
    • How to Record Requests
      • Recording from the UI
      • Recording from the CLI
      • How to Create Contexts
      • How to Create Scenarios
        • Creating from the UI
        • Creating from the CLI
      • How to Create Requests
      • How to Customize Recordings
        • Customizing with Lifecycle Hooks
    • How to Update Requests
      • Editing from the UI
      • Editing with Snapshots
      • How to Update Scenarios
        • Updating from the UI
        • Updating from the CLI
      • Updating with Replay
        • Replaying from the UI
        • Replaying from the CLI
        • How to Customize Replays
          • Customizing with Lifecycle Hooks
      • Updating with Open API
    • How to Mock APIs
      • How to Enable Mocking
        • Enabling from the UI
        • Enabling from the CLI
      • How to Snapshot Requests
        • Deleting Snapshots
        • Sharing Snapshots
      • How to Use Fixtures
      • How to Customize Mocking
        • Customizing with Lifecycle Hooks
        • Customizing with Request Headers
      • Troubleshooting
    • How to Replay Requests
      • Replay with the UI
      • Replay with the CLI
    • How to Integrate E2E Testing
      • How to Scaffold an App
        • Scaffolding a Service
        • Customizing a Workflow
          • Customizing Container Services
          • Customizing Lifecycle Hooks
          • Customizing Init Scripts
          • Customizing Configure Scripts
          • Customizing Makefile
        • Troubleshooting
      • How to Run a Workflow
        • Running with CLI command
        • Running with Make
        • Troubleshooting
          • Validating
      • How to Stop a Workflow
        • Stopping with CLI command
        • Stopping with Make
      • How to Update a Scaffold
        • Deleting a Service
      • FAQ
  • Developer Guide
    • Installation from Source
    • Submitting Change Requests
    • Releases
  • Experimental
    • Experimental Features
      • Aliases
      • Endpoints
      • API Testing
        • Getting Started
        • Configuration
          • Assign
          • Lifecycle Hooks
          • Trace
      • Optional Components
Powered by GitBook
On this page
  • How do I report an issue?
  • Where do I find the latest releases?
  • Is this a test framework?

Was this helpful?

FAQ

PreviousEnable E2E TestingNextRecording

Last updated 4 months ago

Was this helpful?

How do I report an issue?

We track issues in Github at . Please provide as much information as possible and we will take a look

Where do I find the latest releases?

pip releases can be found .

Docker image releases can be found .

To currently see the agent code changes, see the and their changelogs.

To learn how the contributors publish releases, see our .

Is this a test framework?

While Stoobly provides similar functionality in respect to running and provide output for tests, our motive is more to provide a centralized storage for HTTP(s) requests from which you can:

  • Search requests

  • Build requests into scenarios

  • Generate endpoint contracts

  • Mock requests

  • Test request and scenarios

At our core we are essentially a hash map where the key is the request components such as:

  • URL, port number, path, headers, query parameters, body

And the value is the recorded request's response components:

  • headers, body, status code

In regards to mocking and testing, we provide the ability to dramatically reduce the need to write and maintain request and response components in test code. Here is how we tackle the core challenges with testing:

  1. Generation:

  2. Correctness:

    • Replay recorded requests and compare response against recorded response

  3. Maintenance:

    • Replay requests to update responses

    • Contract testing to ensure validity of requests and responses

Record and

😄
https://github.com/Stoobly/stoobly-agent/issues
on PyPI
on Docker Hub
Github Releases
Developer Guide on Releases
requests
scenarios