- From: Roman Bobrovski <
>
- To:
- Subject: [chef] Skipping specific minitest execution in community cookbooks
- Date: Wed, 8 Jan 2014 08:52:38 +0200
Ohai Chefs!
We are using application or wrapper coobook to encapsulate all needed functionality for specific app.
Let's say we have "mywebapp" cookbook that depends on community "apache2" cookbook.
When we running minitest-handler for "mywebapp" it executes apache2 minitest tests along with, usually it's ok but for this specific cookbook tests appear to be broken for a long time (including pending pull requests with fixes).
The question is how can we skip specific tests until they fixed because we rely on integration tests in our CI process.
We've tried setting attribute:
node.default[:minitest][:filter] = '/^((?!apache2).)*$/'
for "minitest-handler" cookbook, but it keeps loading apache2 minitests.
Alternatively we can can change attribute from default
node.default[:minitest][:tests] = '**/*_test.rb'
to custom pattern
node.default[:minitest][:tests] = '**/*_acme_corporation_test.rb'
but this will disable all 3rd party tests which is not preferable solution as they add significant coverage.
--
Roman Bobrovski
- [chef] Skipping specific minitest execution in community cookbooks, Roman Bobrovski, 01/07/2014
Archive powered by MHonArc 2.6.16.