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 an option to perform a dry run #26

Merged
merged 4 commits into from
Apr 23, 2016
Merged

Add an option to perform a dry run #26

merged 4 commits into from
Apr 23, 2016

Conversation

hanneskaeufler
Copy link
Contributor

@hanneskaeufler hanneskaeufler commented Apr 17, 2016

You can now get information about the scripts that would be executed
if you'd run scripty without the dry run flag by setting the env
var SCRIPTY_DRY_RUN=true before executing.

This attempts to be a start to issue #13 and currently looks like:

bildschirmfoto 2016-04-17 um 22 27 05

You can now get information about the scripts that would be executed
if you'd run scripty without the dry run flag by setting the env
var SCRIPTY_DRY_RUN=true before executing.
@hanneskaeufler
Copy link
Contributor Author

Updated the PR to print script contents as well. @searls is this of interest to you? Feel free to close if not, just having some fun with the codebase :)

bildschirmfoto 2016-04-20 um 20 35 40

@searls
Copy link
Member

searls commented Apr 20, 2016

Nope we want this I just need time to review and tweak. Thanks for the work!

On Apr 20, 2016, at 14:38, Hannes Käufler [email protected] wrote:

Updated the PR to print script contents as well. @searls is this of interest to you? Feel free to close if not, just having some fun with the codebase :)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@searls searls merged commit 0886ecb into testdouble:master Apr 23, 2016
@hanneskaeufler
Copy link
Contributor Author

Thanks for looking at this! Out of interest, what does "safe" mean in the context of these tests? I figured by the looks of them, you have put the more focused unit tests into lib and the more integrated tests into safe?

@searls searls mentioned this pull request Apr 23, 2016
@searls
Copy link
Member

searls commented Apr 23, 2016

"safe" is an acronym I made up for integration/regression tests that stands for Smoke Acceptance Functional End-to-end.

Don't worry it's a real thing because it's in a slide deck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants