As a developer, I have performance tests running nightly on CI
We need performance tests with volume (1000 collections or more) to run nightly for v3 endpoints
So this loading of the db is really helpful to test the reading of data from the Galaxy V2 and V3 endpoints. We have a lot of those tests already which is great.
What would be really great is if we didn't "write a lot of new tests" but instead found a way to use the existing test code only against a fully loaded db instead of us loading a minimal amount of data just to give pulp something to respond with. This would like just be a few limited tests, but even if it's a few, I'd like us to avoid "writing the same tests just now in another python module" somehow.
fao89 any ideas on how to achieve this design-wise? Also can we identify a set of existing tests we would like to run with the loaded db?
Please register to edit this issue