Closed tknerr closed 8 years ago
I can definitely see a reason to skip those. For now, you can actually just skip the verify in test by customizing the test cycle.
molecule:
test:
# sequence of commands to run when performing `molecule test`
sequence:
- destroy
- syntax
- create
- converge
- idempotence
#- verify
You can put in every step except for verify in either your local config(~/.config/molecule/config.yml
or project config to skip the verify step.
We have already stated before we aren't going to disable serverspec / rubocop / testinfra validators. Molecule is opinionated. Doing things differently is going to have limited mileage. We can't account for every use case.
@kireledan provided a work-a-round.
@retr0h :+1:
Happy with just setting the serverspec_dir
to a non-existent directory as a workaround. Also, after reading the docs again, it clearly says "test" is for testinfra and "spec" where it looks for serverspec. So my case is really a bit against the recommendation, so no need to account for that ;)
I switched the
testinfra_dir
to "spec" because I'm using the pytest-spec formatter, and naming it spec is more natural for me ;-)Now this fails because it believes there are also serverspec tests in it, but I don't even have rubocop and serverspec installed:
It would be nice if there were a flag in the config to disable the serverspec / rubocop / testinfra validators.
Workaround is to set the
serverspec_dir
to a non-existing directory:Resulting in: