Skip to content
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

Question: Is it possible to specify test-options for v2-test? #743

Closed
meooow25 opened this issue Aug 12, 2024 · 3 comments
Closed

Question: Is it possible to specify test-options for v2-test? #743

meooow25 opened this issue Aug 12, 2024 · 3 comments

Comments

@meooow25
Copy link

I don't see a way to do this, is it possible?
In this case I want CI to run tests with args like --quickcheck-tests=1000

@phadej
Copy link
Collaborator

phadej commented Aug 13, 2024

This is more of a tasty problem (I assume you are using tasty). You want to supply different defaults, seems there is an issue about that UnkindPartition/tasty#414 (in particular something like UnkindPartition/tasty#414 (comment) would be generally useful).

@meooow25
Copy link
Author

I am using tasty, but I don't see this as a tasty problem. If I were using hspec I would have to use --qc-max-success=1000 instead. And there could be other reasons to provide args too, quickcheck is just what I want to deal with at the moment.

@phadej
Copy link
Collaborator

phadej commented Aug 13, 2024

I consider providing options in haskell-ci as an anti-pattern. In a multi-package / multi test-suite setting it's not well behaved. It's an cabal cli interface problem. A work-around solution is to have sane defaults, so CI doesn't need any options. hspec should have a way to set initial defaults as well.

@phadej phadej closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants