Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

backstop-retry-failed-scenarios

Package Overview
Dependencies
Maintainers
2
Versions
10
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

backstop-retry-failed-scenarios

A wrapper command to retry failed scenario for BackstopJS

  • 1.3.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
484
decreased by-11.68%
Maintainers
2
Weekly downloads
 
Created
Source

backstop-retry-failed-scenarios

A wrapper command to retry failed scenario for BackstopJS.
It parses report.json, extract failed tests, and rerun with --filter option, and rewrite result file.
This is useful when your tests are unstable.

FEATURES

  • Invoke specified test command
  • Generate filter option from failed tests
  • Reorganize each failed reports to latest one status
    • Supports HTML report, JSON report, CI report.

EXAMPLE

This endpoint returns random emoji from three emojis(😀, 😇, 😝).
Each try may fail, but retrying failed tests will pass all test.

$ cd examples/retry
$ backstop reference
$ npx backstop-retry-failed-scenarios

examples/retry/images/try.gif

HOW TO RUN

Instead of backstop test, run backstop-retry-failed-scenarios and set command, retry count, config path.

$ npm install -g backstop backstop-retry-failed-scenarios
$ backstop init
$ backstop reference
$ backstop-retry-failed-scenarios --retry 5 --command 'backstop test' --config backstop.js

Instead of npm install, you can pull hitode909/backstop-retry-failed-scenarios from DockerHub.
Its image is based on backstopjs/backstopjs, so you can execute backstop directly from docker run hitode909/backstop-retry-failed-scenarios.

$ docker pull hitode909/backstop-retry-failed-scenarios
$ docker run --rm -v $(pwd):/src hitode909/backstop-retry-failed-scenarios backstop init
$ docker run --rm -v $(pwd):/src hitode909/backstop-retry-failed-scenarios backstop reference
$ docker run --rm -v $(pwd):/src hitode909/backstop-retry-failed-scenarios backstop-retry-failed-scenarios

If you want to recreate references every time, Please set --reference-command option. This will do like this.

  1. create all references
  2. run all tests
  3. create references for failed tests on 2.
  4. run tests for failed tests on 2.

This is useful when your reference refers to production instead static file, and test refers to staging environment.

$ backstop init
$ backstop-retry-failed-scenarios --reference-command 'backstop reference' --command 'backstop test' --config backstop.js

OPTIONS

  --retry             number Trial count. default: 2(Run once, retry once). minimum: 2
  --config            string Path to config file. default: backstop.json
  --command           string Command to run test. default: backstop test
  --reference-command string Command to create reference before testing. Default: null (Do not create reference before test).
  --output-profile    string Path to profiler output file. If present, measure the execution time and output the report as JSON.

FAQs

Package last updated on 04 Mar 2022

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc