Skip to content

(maint) Add additional details on how to run spec tests #6964

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

Merged

Conversation

melissa
Copy link
Contributor

@melissa melissa commented Aug 1, 2018

I've found there can be quite a bit of confusion of how exactly to run
spec tests, especially when it comes to windows. This commit attempts to
add some clarity around how to do that. A step by step guide might be
too prescriptive, but it should be quite helpful for those who are
unfamiliar with working in a windows environment.

@melissa
Copy link
Contributor Author

melissa commented Aug 1, 2018

I've love to get some feedback here to make sure my instructions are clear and concise!

CONTRIBUTING.md Outdated
# Install MSYS2 and MINGW development toolchain. When asked which components to
# install, select the third option. You need both MSYS2 and MINGW to compile the
# native dependencies installed with bundler.
ridk install
Copy link
Contributor

Choose a reason for hiding this comment

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

There's a way of running bundle install so we don't need the devkit installed. But it may not work the way I think it does until we do: https://tickets.puppetlabs.com/browse/PUP-7433

Copy link
Contributor

Choose a reason for hiding this comment

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

I've generally used bundle install --without development extra

CONTRIBUTING.md Outdated
bundle install
# Run all of the tests, where 4 is the number of processors to use
bundle exec rake parallel:spec[4]
# Run a specific test
Copy link
Contributor

Choose a reason for hiding this comment

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

If you wanted to go one step further, you can specify line number for just one test, otherwise I'd say this is more likely to be a group of tests, or some other word artistry

@puppetcla
Copy link

CLA signed by all contributors.

CONTRIBUTING.md Outdated
these tests.
`bundle exec rake parallel:spec[4]`

#### On Windows
Copy link
Contributor

Choose a reason for hiding this comment

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

Some of this info is repeated in https://github.com/puppetlabs/puppet/blob/master/docs/windows.md. Could you DRY it?

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

What do you mean by DRY?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

But also, thank you! I didn't realize those files were there!

Copy link
Contributor

Choose a reason for hiding this comment

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

ah yeah, DRY = "don't repeat yourself" as we describe how to run tests in docs/quickstart.md, docs/windows.md and CONTRIBUTING.md

This commit just adds a few links and clarifies some steps to help folks
developing against puppet in different environments.
@melissa melissa force-pushed the maint/5.5.x/run-tests-windows-deets branch from 2b23aab to 74c759f Compare August 3, 2018 18:23
@melissa
Copy link
Contributor Author

melissa commented Aug 3, 2018

Okay, I cleaned this up a bit. Thank you for pointing out those redundancies, Josh!

@joshcooper joshcooper merged commit b9d87f5 into puppetlabs:5.5.x Aug 3, 2018
@melissa melissa deleted the maint/5.5.x/run-tests-windows-deets branch October 15, 2018 17:20
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.

4 participants