Open htgoebel opened 9 years ago
Have you taken a look at this? https://github.com/nickjj/rolespec/#test-modes
Would any of those options work for you?
Yes, I did. But -t
does not install ansible at all, even if it is missing. So the developer always has to think, if ansible is already installed in his very setup at this very moment. But this is a computers job, not a human's one.
It would be expected that you run rolespec normally at least once before using -t
or -p
.
My use-case is different: I'm running the test in a VM while developing the roles. And it is simply a wast of time to reinstall esp. Ansible every few minutes. Using -t
or -p
is error-frown, because one has to think about running rolespec without once first. So I simply do not use -t
or -p
.
This may not meet you use-case, but is important for me - and it does not hurt anyone.
Hmm, when you say developing the roles do you mean you have the roles sitting in the VM and you are running tests against the VM?
If so, that's exactly how I develop roles in the "I'm developing the role" stage. What's wrong with doing a run once to get things installed then just hammer away at your role using -p
or -t
depending on what you want to test?
Are you going to integrate this pullrequest somewhen? It's pending for more than half a year now.
@nickjj Please decide whether you want to merge or close this pull-request. I want to get rid of my fork. Thanks.
Setting this variable makes rolespec not reinstall existing software. Currently this only effects ansible.