(Imported from Trac #929, reported by @tibbe on 2012-03-12)
I was trying to debug a cabal test issue today and in doing that I needed to understand how cabal invoked the test binary (e.g. a stdio-exitcode test suite.) However, passing -v3 to cabal test doesn't cause it to be printed.
Proposed fix: Have cabal test -v3 output all commands being run. Model it after -v3 for e.g. build or install.
(Imported comment by @dcoutts on 2012-03-12)
The solution is for the cabal test code to use the standard process running functions that the rest of the Cabal lib uses. That would provide the -v support in the same way as other features, and match what users expect.
If there's any limitations in the existing process running functions that make them unsuitable then we should fix that.
(Imported comment by @kosmikus on 2012-03-27)
This seems to affect the library test code, not the install tool.
This issue was fixed long ago.