You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
For unit testing with
gnattest
, there is the ability to setup and teardown globally here:libadalang-tools/src/test-common.adb
Line 900 in 8702a8f
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 thetests
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.The text was updated successfully, but these errors were encountered: