[BUG] --state used when it shouldn't be

[Andy Armstrong]

On 3 Jan 2008, at 10:57, Ovid wrote:
> It seems to me that if I run prove with an explicit set of tests, only
> those tests should be run, regardless of what's in my .proverc.

Um. Yes, maybe :)

There's a reason for the current behaviour - it's so that if you do

$ prove --state=hot,fast,save -r t

it automatically adds newly created tests; --state only knows about  
existing tests.

Suggestions welcome for a cleaner way of handling that.

> On a different note, we are now running one project's tests in three
> directories (well, we're about to create the third):
>
>  t/
>  test/aggregate
>  test/standards
>
> Should the .prove file group tests by directory instead of assuming
> that all tests which are run will be run every time?  In other words,
> when I run:
>
>  prove -rl --state=hot,fast,save t/
>
> And:
>
>  prove -rl --state=hot,fast,save test/standards
>
> I won't those to run different sets of tests (obviously), even though
> I'm running them from the same directory :)


Well if we can fix the first problem then something like that sounds  
reasonable too :)

-- 
Andy Armstrong, Hexten