Skip to content

cabal new-test is not at feature parity with cabal test #4803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cartazio opened this issue Sep 30, 2017 · 1 comment
Closed

cabal new-test is not at feature parity with cabal test #4803

cartazio opened this issue Sep 30, 2017 · 1 comment

Comments

@cartazio
Copy link
Contributor

cartazio commented Sep 30, 2017

eg --keep-tix-files keep .tix files for HPC between test runs isn't supported yet (not withstanding the current breakage in coverage testing :) )

@23Skidoo 23Skidoo changed the title cabal new-test is not at feature paraity with cabal test cabal new-test is not at feature parity with cabal test Oct 14, 2017
@fgaz
Copy link
Member

fgaz commented Oct 22, 2017

See also #4643 and #4766.

we don't have support for test and bench specific flags in new-build yet

harpocrates added a commit that referenced this issue Nov 12, 2018
This means that old `test` flags can be passed in to `new-test`, `new-build`, `new-install`,
`new-configure`, etc. These new flags are:

    * `--test-log` (see old `--log`)
    * `--test-machine-log` (see `--machine-log`)
    * `--test-show-details` (see `--show-details`)
    * `--test-keep-tix-files` (see `--keep-tix-files`)
    * `--test-options`
    * `--test-option`

This fixes #4803, #4643, #4766, and #5416.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants