#787: --test-option should support template argument
----------------------------------+-----------------------------------------
Reporter: tibbe | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: cabal-install tool | Version: HEAD
Severity: normal | Keywords:
Difficulty: very easy (<1 hour) | Ghcversion:
Platform: |
----------------------------------+-----------------------------------------
The test-framework package can optionally output JUnit XML, an XML flavor
understood by many continuous build systems, if you pass it the `--jxml`
flag. Using that flag, one can get `cabal test` to output JUnit XML:
{{{
cabal configure --enable-tests
cabal build
cabal test --test-option=--jxml=dist/test/junit.xml
}}}
However, the `--test-option` flag doesn't allow the user to pass different
flags to different test executables so each test executable will override
the output of the previous.
If the `--test-option` flag took a name template argument, supporting a
`$test-suite` placeholder, you could generate one JUnit XML file per test
suite:
{{{
cabal configure --enable-tests
cabal build
cabal test --test-option=--jxml=dist/test/$test-suite.xml
}}}
The detailed test interface might support this in some nicer way, but this
is a cheap way to have Cabal cooperate better with other test runners.
--
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/787>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects
_______________________________________________
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel
