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
The current integration tests are structured in such a way that every integration test has its own set of repy dependencies. This makes updating the e-mail list a pain, as well as makes the directories for each test case very cluttered.
We should reorganize it so that the integration tests share the repy dependencies (files generated by preparetest.py). Also, we should only include the actual test cases in their own directories as well.
The text was updated successfully, but these errors were encountered:
is facilitated by freshly reading in the list on every call of integrationtestlib.notify(), see aot221/integrationtests@a7bd41c (further cleanup scheduled before we merge.)
directories [...] cluttered
The repo's subdirectories are clean, so that's a build issue. I suppose we could let all of the tests use the same Repy runtime if we wanted to.
The new question I have is whether we should make this repo only contain the common elements/libraries required to scaffold an integration test, and move the actual tests to the directories of the components they are testing. For example, you wouldn't want to run timeserver integration tests if you are running a custom clearinghouse only.
The current integration tests are structured in such a way that every integration test has its own set of repy dependencies. This makes updating the e-mail list a pain, as well as makes the directories for each test case very cluttered.
We should reorganize it so that the integration tests share the repy dependencies (files generated by preparetest.py). Also, we should only include the actual test cases in their own directories as well.
The text was updated successfully, but these errors were encountered: