Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Strict mode for example matching? #158

Open
mockdeep opened this Issue · 1 comment

2 participants

@mockdeep

I think it would be pretty handy when mutating classes to fail mutation testing if there isn't a strict example group match. For example if I have the method Foo::Bar#baz, then there has to be an example group that matches it. Examples on Foo or Foo::Bar would be ignored.

@mbj mbj added the enhancement label
@mbj
Owner
mbj commented

So currently we only have strict example group matches. When I add non strict matching with fallback I'll add a warning message. Tagging this ticket as enhancement.

@mbj mbj referenced this issue from a commit
@mbj Push down test selection and add framework for output capture
This clearly is a WIP. We know have the reporter granularity to capture
per mutation test outputs + per mutation test selections.

This adds all infrastructure to address:

* #185 we know which tests are run in reporter
* #180 fine grained information available for the reporter
* #178 minitest project integration only needs to return an enumerable
  with metadata
* #174 We can now "see" all test, allowing to generate a default
  matcher.
* #158 Ability to steer test selection centralized for all integrations
* #125 We have the required objects in graph
* #96 We have finer granularity in reporter graph

Because we know signal more complex state from killforks to parent I
need to bring back killfork partent signalling, but this time with
sending complex data around (Test::Report). Should be easy with
Marshal.{dump,load} but my OSS time budget is exhausted for now.
a618d82
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.