[
https://issues.apache.org/jira/browse/BUILDR-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Boisvert updated BUILDR-415:
---------------------------------
Attachment: BUILDR-415-TEST-EXCLUDE.patch
I'm proposing a syntax where a leading minus ('-') indicates a test exclusion,
e.g.,
buildr test:Foo,-Bar
would include Foo and exclude Bar. The syntax is consistent with the existing
wildcard-expanding, multi-test support of the test:... rule. For instance,
you could write,
buildr test:-com.example.*,*Bar,Foo
to exclude any tests from the "com.example" package, include any tests ending
in "Bar" and include any tests containing the word "Foo".
Exclusions override inclusions. Using either inclusions/exclusions on the
command-line automatically ignore includes/excludes defined in the Buildfile.
Attaching a working but not spec'ed implementation.
> Ability to exclude tests from command line or environment variable
> ------------------------------------------------------------------
>
> Key: BUILDR-415
> URL: https://issues.apache.org/jira/browse/BUILDR-415
> Project: Buildr
> Issue Type: New Feature
> Components: Test frameworks
> Reporter: David Carver
> Fix For: 1.4.2
>
> Attachments: BUILDR-415-TEST-EXCLUDE.patch
>
>
> It would be helpful when running certain types of continuous integration
> builds, to be able to not only specify which tests to be included from the
> command line, but also which tests to be excluded. Currently the only way
> to setup exclusions is to make the appropriate entries in the Rakefile.
> However other build systems like ant and maven allow ways to setup exclusions
> and overrides for tests from the command line or to be passed in as
> properties to the build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
