-
Notifications
You must be signed in to change notification settings - Fork 711
Where to put project tests, cabal-testsuite/ProjectTests? #9798
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
Comments
I always thought about it as a “this is where golden tests go” folder. Do we gain something by dividing it in two? If there is a build command test for a package and one for a package in the context of a project, do they go one in |
Yes we see how few (or how many) project tests we have. |
The package tests often depend on project files, so I think the line between a package test and a project test is rather blurry... I'm not sure if separating them will gain us any clarity and will introduce another decision one has to make before they start writing a test (friction). |
I'm suggesting moving only the project-specific tests (imports and the like), not tests with a project, not tests with a
|
I suppose that is more reasonable, but the test you linked also contains a Cabal package, how do you tell it is a project test? |
We had 3 projects in
I've added a few more recently.
|
I worked through the project reference seeing which project settings are in
|
Here's all the
|
I've been adding tests of projects to
cabal-testsuite/PackageTests
where all othercabal-testsuite
tests are. Can I start adding project tests (and moving some misplaced ones) tocabal-testsuite/ProjectTests
?The text was updated successfully, but these errors were encountered: