cabal-validate
: Too many ways to choose steps
#10564
Labels
cabal-validate
validate.sh (cabal-validate) test suite runner
meta: tracking
re: devx
Improving the cabal developer experience (internal issue)
type: testing
Issues about project test suites
The CLI defaults are unclear, there's about three different ways to choose which steps are run, and it's not obvious how they interact. (Even to me, and I wrote it!)
For example:
--cli
testscabal-install
in addition toCabal
, but there's no--cli-only
flag.--run-lib-tests
and similar options exist only to add or remove specific--step
s. (But will be ignored if any--steps
are given.)--step
adds a specific step to be run (can be used multiple times).Proposal: Remove the
--cli
,--lib-only
, and all other flags that exist to enable/disable a specific step. (Needs groups of steps.)--cli
, you'll use--group Cabal --group cabal-install
(this makes it explicit that--cli
also tests theCabal
library).--run-lib-suite
you'll use--step lib-suite
.--no-run-lib-suite
you'll specify the steps you want to run, e.g.--step lib-tests --step cli-tests --step cli-suite
(that's the default behavior with--no-run-lib-suite
, but probably not what you want!)The text was updated successfully, but these errors were encountered: