A middle ground between --tests and --no-tests #236
Comments
|
I was thinking of introducing
|
|
Sounds good to me! If these flags do intersect with |
|
Intersection means hopefully obvious: only built tests can be run, but you can run tests on less jobs. E.g. |
|
... and with you won't build (and run) any tests. |
Merged
phadej
added a commit
that referenced
this issue
Mar 6, 2019
- Add global --run-tests/--no-run-tests/--run-tests-jobs to specify
when we actually run tests (maybe less then what we build!)
- Add steps configuration to constraint sets:
- tests
- run-tests
- benchmarks
- haddock
- these are only booleans for now, if you need more control, make
another constraint set!
phadej
added a commit
that referenced
this issue
Mar 7, 2019
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently,
haskell-cigives you the ability to prevent building any test suites using the--no-testsflag. This is almost what I need, but not quite. I have a project where I can't run the test suites on Travis due to the tests' reliance on a web browser being run at the same time. That being said, I still want to build (but not run) the test suite on Travis so as to ensure that the code doesn't bitrot. Unfortunately,--no-testsis too heavy-handed, as it prevents the test suites from being built in the first place.Could there be a flag that permits the test suite to be built but not run, similarly to how benchmarks are currently handled? I'm not sure what the best name for this flag should be, or if it would make sense to make
--no-testsfurther configurable to allow this.The text was updated successfully, but these errors were encountered: