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
  • Should I use CLI or Makefile commands?
  • Which Workflow does my custom container service go in?
  • Which Docker network does my service go in?
  • How to run concurrent test workflows in CI?
  • What agent version of Scaffold am I running?

Was this helpful?

  1. Guides
  2. How to Integrate E2E Testing

FAQ

PreviousDeleting a ServiceNextInstallation from Source

Last updated 5 days ago

Was this helpful?

Should I use CLI or Makefile commands?

We recommend the Makefile commands. These often run the stoobly-agent scaffold commands with other prerequisite commands and optimal flags.

These also run the scaffold commands in a Docker container to ensure dependencies are consistent across runs.

Which Workflow does my custom container service go in?

This depends on what use-case you want to use the service for.

If you want to record requests, then you should add it to the record workflow first.

Then only add it to the mock and test workflows if you want unrecorded requests to go the service.

Which Docker network does my service go in?

There are two Docker networks:

  • app.ingress

  • app.egress

To learn more:

How to run concurrent test workflows in CI?

Ideally your CI pipelines are running on isolated hosts, but often that isn't the case.

Add the "namespace" flag to your workflow run command to avoid Docker resource conflicts. A recommended namespace name is the git commit of the branch's HEAD.

Makefile command example:

make -f .stoobly/docker/Makefile test options="--namespace $(git rev-parse HEAD)"

Scaffold run command example:

stoobly-agent scaffold workflow up test --namespace $(git rev-parse HEAD)

What agent version of Scaffold am I running?

Run this command to output the Docker image version of your Scaffold:

$ cat .stoobly/docker/.Dockerfile.context | grep "FROM"

FROM stoobly/agent:1.6
Scaffold