[If you got multiple copies of this, then sorry -- I had to sort with which address I'm actually subscribed to cabal-devel.]

...

The way to handle tests for named packages would be to add a PackageConstraint for tests the way is already done for flags, but this is a lot more work because it would require getting deep into the dependency solver. However, it would make it easy to set the config flags during build for explicit targets so we could implement a test auto-run feature.

When I rewrote the solver, I was actually surprised that test flags are sort of bypassing the solver. I don't think it would be all that difficult to build it into the new solver properly, *if* I'd know what properly means. So if you can specify a reasonable behaviour you'd expect from the solver, I can try to implement it.

Cheers,  Andres

-- Andres Löh, Haskell Consultant Well-Typed LLP, http://www.well-typed.com