-
-
Notifications
You must be signed in to change notification settings - Fork 736
[WIP] Dry-run mode #1825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Dry-run mode #1825
Conversation
@DavertMik what is the use case for dry mode? |
@pablopaul Use cases:
|
Btw, the similar PR for mocha was never merged mochajs/mocha#1070 |
To enable bootstrap script in dry-run mode, pass in `--bootstrap` option when running with `--steps` or `--debug` | ||
|
||
``` | ||
nox codeceptjs dry-run --steps --bootstrap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npx instead of nox
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, thank you. Could you make a pull request fixing this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, pull request created.
In this mode, you can print tests output with no commands actually being executed.
This mode disables all helpers and plugins but preserves all events and console output, so you can easily see what all tests are doing, and validate your tests before running them completely
Usage
OUTPUT
When passed
--steps
or--debug
option runs tests, disabling all plugins and helpers, so you can get step-by-step report with no tests actually executed.If a plugin needs to be enabled in
dry-run
mode, pass its name in-p
option:OUTPUT