Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Postman Collection

Check

Check

Execute a Postman collection through Postman's cloud API.
Targets:
Postman Collections
Install now

Postman Collection

Execute a Postman collection through Postman's cloud API.
Check

Check

Targets:
Postman Collections
Install now

Postman Collection

Check

Check

Execute a Postman collection through Postman's cloud API.
Targets:
Postman Collections
Install now

Postman Collection

Execute a Postman collection through Postman's cloud API.
Check

Check

Targets:
Postman Collections
Install now
Go back to list
YouTube content is not loaded by default for privacy reasons.

Introduction

The Postman Integration can be used to run a Postman collection. You can find the Postman integration in the "Checks" folder in the experiment editor.

Details

Currently, we are supporting collections, which are hosted and accessible via Postman's Cloud API service.

We are using newman to run your collection behind the scenes.

References

Configuration

To configure the Postman integration, you need to provide an API-Key. This can be created here.

Target

You have to specify the collection to run as target. The collections will be discovered by the extension.

Parameters

NameRequiredDescription
Estimated durationYesAs long as you have no timeout in place, the step will run as long as needed. You can set this estimation to size the step in the experiment editor for a better understanding of the time schedule.
Environment Id or NameNoThe environment id or name to use. You can put the environment name here or find out your environment id by fetching all environments from the postman api with https://api.getpostman.com/environments?apikey=$apiKey
Environment VariablesNoAdditional environment variables, will be passed to newman with --env-var key=value
IterationsNoNumber of iterations to run the collection, will be passed to newman with -n
TimeoutNoThe timeout of your collection, wil be passed to newman with --timeout. Hint: If you hit this timeout, no reports will be generated.
Request TimeoutNoThe request timeout for each request, wil be passed to newman with --timeout-request
VerboseNoShould we enable verbose logging? Will be passed to newman with --verbose
BailNoStops the runner when a test case fails. Will be passed to newman with --bail

Outputs

We are using the reporters cli, json-summary and htmlextra.

You can download the json-summary and htmlextra -report in the experiment run log after the experiment has finished. We omit the response bodies in the htmlextra-report.

The cli-output can be accessed by clicking on the Action Logs-tab in the experiment run view and supports a live view during experiment execution.

The step will be marked as failed, if implemented tests in the postman collection are failing.

Statistics
-Stars
Tags
Postman
Check
Homepage
hub.steadybit.com/extension/com.steadybit.extension_postman
License
MIT
MaintainerSteadybit

Useful Recipes

See all
Verify graceful degradation when Kafka message broker can't be reached

An unavailable Kafka is not user-visible as it leads to graceful degradation and downstream retries as soon as the Kafka is back available again.

Tags:
Kafka
Recoverability
Targets:

Postman Collections

Containers


Start Using Steadybit Today

Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Steadybit logoResilience Hub
Try Steadybit
HubActionsTargetsExtensionsRecipes
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon