volkswagen
Makes your tests pass when they detect a CI server. A satirical joke project.
- Stars
- 15.5k
- Forks
- 239
- Licence
- MIT
- Language
- JavaScript
- Last update
- 8 months ago
- Type
- Library
What it is
Volkswagen is an npm package that checks whether your tests are running on a CI server, such as Travis CI or GitHub-style pipelines that set a CI environment variable, and then makes the tests pass. The README presents it as a joke, referencing the Volkswagen emissions scandal. It does not fix failing code. It hides failures from CI, so the results don't reflect real test outcomes.
- Add require('volkswagen') to a main test file so supported test suites report passing on CI
- Show the volkswagen status badge in a project README as a joke
- Study the source to see how CI servers are detected through environment variables
Great for
- Developers who want to see an example of how CI environment detection works
- People studying how test runners and exit codes can be manipulated
- Readers looking for a satirical take on fake test results
- Anyone wanting to understand why CI results should not be overridden
Not ideal for
- Teams that rely on CI to catch real bugs, because it makes failing tests pass and hides problems
- Production or shared projects, because the results it produces are misleading
- Anyone needing accurate test reports or quality gates, since it defeats them by design
How to get it
- 1
Install with a package manager
Install the package
npm install volkswagen - 2
Run it
- Run npm install volkswagen in your project
- Add require('volkswagen') in your main test file
- Run your test suite locally to confirm it loads
- Run the tests on a supported CI server to see the effect
- 3
Get the most out of it
- Check the README's list of supported CI servers to confirm yours is covered
- Confirm your test runner is in the list of defeated suites before relying on it
- Use the README's badge snippet if you want to display the status badge
Downloads
Strengths
- Very small setup: one npm install and one require call
- Lists many CI servers it detects, including Travis CI, CircleCI, GitHub-style and GitLab CI
- Released under the MIT license, so the code is free to read and reuse
Trade-offs
- It hides real test failures, so CI results become untrustworthy
- Only works with the test suites the README lists (assert, tap, tape, chai) plus those that set the exit code or throw errors
- Detection depends on CI environment variables, so coverage of other CI servers is not guaranteed
How it compares
| Project | Stars | Type | Level | Updated | Best for |
|---|---|---|---|---|---|
| volkswagen (this) | 15.5k | Library | beginner | 8 months ago | Developers who want to see an example of how CI environment detection works |
| jenkins | 26.7k | App | intermediate | 4 days ago | Development teams that want to automate builds and tests |
| cheat | 13.5k | CLI | beginner | 6 months ago | Sysadmins who use many commands only occasionally |
Stats synced from GitHub. The assessment above was drafted with AI from the project's README on 2026-10-29 and may miss recent changes — check the README before relying on a command. MIT licence: free to use, modify and distribute, including commercially, as long as you keep the copyright notice.