Skip to content
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

Add buildCommand question when running stryker init #3213

Merged
merged 5 commits into from
Oct 25, 2021
Merged

Add buildCommand question when running stryker init #3213

merged 5 commits into from
Oct 25, 2021

Conversation

radiantly
Copy link
Contributor

Background

On running stryker init, the user is prompted for a custom build command to run provided that they do not choose the jest test runner.

Screenshot

image

Tracking Issue

Fixes #3211

Copy link
Member

@nicojs nicojs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Could you also add 3 unit tests? One for jest, one for not-jest but without a build command and 1 for not-jest with a build command?

The unit tests for the initializer are all situated in test/unit/initializer/stryker-initializer.spec.ts

packages/core/src/initializer/stryker-inquirer.ts Outdated Show resolved Hide resolved
@radiantly radiantly requested a review from nicojs October 19, 2021 16:45
Copy link
Member

@nicojs nicojs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the great PR 👍. Just a small remark, please let me know if you don't agree or don't have the time to implement it.

@radiantly radiantly requested a review from nicojs October 20, 2021 16:56
@nicojs nicojs enabled auto-merge (squash) October 25, 2021 07:30
@nicojs nicojs merged commit b9d5980 into stryker-mutator:master Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add "buildCommand" to stryker init
2 participants