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

Should the persistent package (with global setup and teardown) be located outside the harness folder when using gnattest? #30

Open
dalybrown opened this issue Dec 11, 2023 · 0 comments

Comments

@dalybrown
Copy link

For unit testing with gnattest, there is the ability to setup and teardown globally here:

Persistent_Package_Name : constant String :=
.

However, this file is by default generated in a subfolder of the harness directory. We typically treat everything in that folder as throwaway in the sense that we can regenerate it so we don't commit any of the files to version control. However, the one exception is this file mentioned above.

Would it make more sense to place that file outside the harness directory? It seems (to me at least) that it is cleaner if everything in the harness directory is ignored and everything in the tests is added to version control. Otherwise we need some complicated exceptions in our .gitignore file.

Alternatively, perhaps there is another option to provide gnattest where read-only files are placed in on folder and the other files (which are added to version control) are placed in their own folder.

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

1 participant