We decided we should have tests that will ultimately test the preprocessing pipelines and ingest. I propose to call these "integration tests" just to have a new name. Unlike other website-related tests they will live in their own top level directory.
My idea for this is that we should try to see how far we can get with these tests only interacting with Loculus in ways that users would. This means primarily the website, though as we add say a CLI it would also include that. So, setting up test data etc. can all be done through the website at least until we find that that is being flaky or too slow.
We decided we should have tests that will ultimately test the preprocessing pipelines and ingest. I propose to call these "integration tests" just to have a new name. Unlike other website-related tests they will live in their own top level directory.
My idea for this is that we should try to see how far we can get with these tests only interacting with Loculus in ways that users would. This means primarily the website, though as we add say a CLI it would also include that. So, setting up test data etc. can all be done through the website at least until we find that that is being flaky or too slow.