#1161: Clean up the library testing story
---------------------------------+------------------------------------------
Reporter: simonmar | Owner: igloo
Type: task | Status: new
Priority: normal | Milestone: 7.4.1
Component: Test Suite | Version: 6.7
Keywords: | Testcase:
Blockedby: | Difficulty: Moderate (less than a day)
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
Comment(by simonmar):
How would cabal test interact with the GHC testsuite infrastructure? We
have lots of parameters to pass in (compiler, flags, ways etc.), and
information to get out again (the result of each test), and some
infrastructure we might want to share (the test driver).
I'm wondering whether a better approach might be to have both an `all.T`
as well as the cabal test infrastructure (whatever that might be) for each
package.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1161#comment:7>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
