Skip to navigation

View, edit, or update a Postman simulation

Beta
View as Markdown

After you start a simulation, you can view its logs to see how the simulated conditions are affecting your API’s behavior. You can also edit or update the mocks and scenarios in the simulation at any time.

View simulation logs

After you start a simulation, you can view the logs for the mocks included in the simulation.

  1. Open a workspace and select Tools > Stroke icon Simulations in the footer.
  2. Select a simulation with running mocks.
  3. View the logs in the Logs pane.

You can filter logs by path, mock, method, status code, and time range. This helps you analyze how the simulated conditions are affecting your API’s behavior. For example, you can filter by status code to see only failed requests or filter by method to see how different endpoints are affected.

You can click a request to view more details about the request and response, such as the headers and body.

Click Delete icon Clear logs to clear the logs for the mock.

View simulation history

Each time you start a simulation, Postman records the run. Use simulation history to review past runs, including who started each one, how long it ran, and the logs and state captured during the run.

  1. Open a workspace and select Tools > Stroke icon Simulations in the footer.
  2. Select the simulation.
  3. Click History.

The history table lists each run with the following details:

ColumnDescription
Start timeThe date and time the run started.
SourceWhere the run was started from, either App or CLI.
Started byThe user who started the run.
DurationHow long the simulation ran.
CallsThe number of requests the simulation handled.
StatusThe status of the simulation run, such as Stopped.

Use the Started by and Source filters to narrow the list.

You can also open a simulation’s past runs from the History icon History tab in the sidebar. To learn more, see History.

Edit a simulation configuration

You can edit the configuration for a simulation to update the mocks and scenarios included in the simulation. In Local View, you can also edit the simulation file directly to update the configuration. In Cloud View, you can configure details like the URL or how requests access mock servers in the simulation.

Edit a simulation configuration in Local View

To edit a simulation configuration in Local View, do the following:

  1. Open a workspace and select Tools > Stroke icon Simulations in the footer.

  2. Select the simulation you’d like to edit.

  3. Select the YAML tab to view the simulation file.

  4. You can update the following details:

    • id — The unique identifier for the simulation.
    • simulation — The name of the simulation.
    • slug — The unique slug for the simulation URL.
    • routing — The routing method for requests to access mocks in the simulation. This can be either path or header.
    • mocks — The mocks included in the simulation. Each entry has an id, a path to the mock’s config.yaml file, and a scenarios list. Each scenario entry has an id, a path to the scenario’s implementation file, and an optional overrides block. Conditions you override for the simulation are stored under overrides.conditions (for example, latency.delay_ms), which leaves the scenario’s own conditions unchanged.

Edit a simulation configuration in Cloud View

To edit a simulation in Cloud View, do the following:

  1. Open a workspace and select Tools > Stroke icon Simulations in the footer.
  2. Select the simulation you’d like to edit.
  3. In the upper right of the workbench, click Options icon Edit configurations.
  4. You can update the URL for the simulation.
  5. You can update how requests access mocks in the simulation.
  6. Click Confirm.

Update a simulation

To update a simulation, do the following:

  1. Open a workspace and select Tools > Stroke icon Simulations in the footer.
  2. Select the simulation or click Options icon Actions > Open next to a simulation.
  3. Update the mocks and scenarios included in the simulation.

You can also click Options icon Actions next to a simulation to duplicate or delete it.