15.5K ·GitHub
What is this?
Volkswagen is a joke Node.js library that detects when your test suite is running on a CI server and silently makes the tests pass, no matter what the actual results are.
Volkswagen is a joke Node.js library that detects when your test suite is running on a CI server and silently makes the tests pass, no matter what the actual results are.Is this a real testing framework?No — it is not a framework you write tests with, it is a tiny prank module you require into your existing test suite that patches the results behind the scenes.
No — it is not a framework you write tests with, it is a tiny prank module you require into your existing test suite that patches the results behind the scenes.How do I add it to my tests?Install it with npm and then just require volkswagen somewhere in your code-base, typically in your main test file.
Install it with npm and then just require volkswagen somewhere in your code-base, typically in your main test file.Does it need any special CI configuration to work?No extra config is needed for the CI servers it already knows about — it recognizes them automatically through standard CI or CONTINUOUSINTEGRATION environment variables.
No extra config is needed for the CI servers it already knows about — it recognizes them automatically through standard CI or CONTINUOUSINTEGRATION environment variables.Does it defeat every test framework out there?It only works against test tools that rely on throwing errors or setting a process exit code to signal failure, specifically listing assert, tap, tape, and chai, plus 'any test actually that set the exit code or throw an error'.
It only works against test tools that rely on throwing errors or setting a process exit code to signal failure, specifically listing assert, tap, tape, and chai, plus 'any test actually that set the exit code or throw an error'.Why is it named Volkswagen?It is a wink at the 2015 Volkswagen diesel emissions scandal, reusing the term 'defeat device' for a piece of software that fakes passing results instead of real emissions compliance.
It is a wink at the 2015 Volkswagen diesel emissions scandal, reusing the term 'defeat device' for a piece of software that fakes passing results instead of real emissions compliance.Which CI servers does it recognize out of the box?The README lists Travis CI, CircleCI, Jenkins, Hudson, Bamboo, TeamCity, Team Foundation Server, VSO CI, GitLab CI, Codeship, Drone.io, Magnum CI, Semaphore CI, AppVeyor, Buildkite, TaskCluster, GoCD, and Bitbucket Pipelines, plus any CI exposing the generic CI or CONTINUOUSINTEGRATION env vars.
The README lists Travis CI, CircleCI, Jenkins, Hudson, Bamboo, TeamCity, Team Foundation Server, VSO CI, GitLab CI, Codeship, Drone.io, Magnum CI, Semaphore CI, AppVeyor, Buildkite, TaskCluster, GoCD, and Bitbucket Pipelines, plus any CI exposing the generic CI or CONTINUOUSINTEGRATION env vars.Should I actually ship this in a real project?No — it is satire about gaming CI checks; using it means your 'passing' build badge is a lie, which defeats the entire point of having tests.
No — it is satire about gaming CI checks; using it means your 'passing' build badge is a lie, which defeats the entire point of having tests.What are similar projects?BullshitGenerator, jenkins, agentic-playwright, ava, e2e, awesome-actions, karma, lintapple
BullshitGenerator, jenkins, agentic-playwright, ava, e2e, awesome-actions, karma, lintappleWhich topics is it in?satire, continuous-integration, fun, test-automation, ci-cd, npm-package, ci, testing, utility, npm, automation, tool
satire, continuous-integration, fun, test-automation, ci-cd, npm-package, ci, testing, utility, npm, automation, tool