CharliePoole

That explains a lot. My way of testing, when I worked on CF, reloaded the app each time. "While you are at it" you might want to look at the...

Essentially, this issue is about using the seed under a 3rd party, non-open-source runner, which does not reload the tests between runs. Back when I worked on the framework (i.e....

Also, note that any runner is able to reload the tests, using the `RandomSeed` setting to select a specific seed if desired.

First, let me clarify why it is that ExplicitAttribute can't apply to a SetUpFixture... Explicit means "Don't run this unless it is explicitly selected." There is no way to explicitly...

Can you try an experiment? Put your setupfixture in a namespace that includes all your excluded tests. Does it work any differently in a namespace than it does at the...

Too bad. The easiest solution would be if the setup fixture didn't run at all if it had no selected tests under it. That's what I was hoping.

As a stopgap measure, I added a warning about this to the pages for Explicit and Category attribute.

We have one or two similar requests, which we will eventually merge when we decide how to handle this. Currently, the most flexible use of custom attributes is for those...

@jnm2 You are right to treat this as an important decision. We sorely need a general way to inject cross-cutting behavior so that the overly complex Action Attributes can be...

@yaakov-h In the case of `IWrapSetUpTearDown`, it's definitely possible to do this without a new attribute to indicate that the crosscutting behavior is desired. That's because the particular interface makes...