Commit e08c6d16 authored by Oleg Grenrus's avatar Oleg Grenrus
Browse files

Resolve #3558

parent 79b6f2ab
...@@ -69,6 +69,8 @@ several. In general, the test executable for ...@@ -69,6 +69,8 @@ several. In general, the test executable for
`{Cabal,cabal-install}:$TESTNAME` will be stored at `{Cabal,cabal-install}:$TESTNAME` will be stored at
`dist-newstyle/build/{Cabal,cabal-install}-$VERSION/build/$TESTNAME/$TESTNAME`. `dist-newstyle/build/{Cabal,cabal-install}-$VERSION/build/$TESTNAME/$TESTNAME`.
To run a single test, use `-p` which applies a regex filter to the test names.
* `Cabal:package-tests` are out-of-process integration tests on the top-level `Setup` * `Cabal:package-tests` are out-of-process integration tests on the top-level `Setup`
command line interface. If you are hacking on the Cabal library you command line interface. If you are hacking on the Cabal library you
want to run this test suite. It must be run from the `Cabal` subdirectory want to run this test suite. It must be run from the `Cabal` subdirectory
...@@ -83,6 +85,10 @@ several. In general, the test executable for ...@@ -83,6 +85,10 @@ several. In general, the test executable for
find . -name test.log|grep test-name find . -name test.log|grep test-name
``` ```
`test.sh` in the same directory as `test.log` is intended to let you rerun
the test without running the actual test driver.
* `Cabal:unit-tests` are small, quick-running unit tests * `Cabal:unit-tests` are small, quick-running unit tests
on small pieces of functionality in Cabal. If you are working on small pieces of functionality in Cabal. If you are working
on some utility functions in the Cabal library you should run this on some utility functions in the Cabal library you should run this
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment