SEAT

SEAT detects when your tests are being run in a CI server, and makes them pass.

Why?

If you want your software to be adopted by Americans, good tests scores from the CI server are very important. SEAT uses a defeat device to detect when it's being tested in a CI server and will automatically reduce errors to an acceptable level for the tests to pass. This will allow you to spend less time worrying about testing and more time enjoying the good life as a trustful software developer.

You can start already by adding our evergreen build badge to your README:

Markdown snippet:

[![volkswagen status](https://auchenberg.github.io/volkswagen/volkswargen_ci.svg?v=1)](https://github.com/erkinalp/SEAT)

Installation

npm install seat

Usage

Just require SEAT somewhere in your code-base - maybe in your main test file:

require('seat')

Project status

CI servers detected:

• Travis CI
• CircleCI
• Jenkins CI
• Hudson
• Bamboo
• TeamCity
• Team Foundation Server
• Visual Studio Online CI
• GitLab CI
• Codeship
• Drone.io
• Magnum CI
• Semaphore CI
• AppVeyor
• Buildkite
• TaskCluster
• GoCD
• Bitbucket Pipelines
• + all other CI servers that exposes a CI or CONTINUOUS_INTEGRATION environment variable

Test suites defeated:

• assert
• tap
• tape
• chai
• + any test actually that set the exit code or throw an error

License

MIT

Credits

Heavily inspired by https://github.com/hmlb/phpunit-vw