https://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-03-30T18:07:39ZPulpAnsible Plugin - Task #8478: As a developer, I have performance tests running nightly on CIhttps://pulp.plan.io/issues/8478?journal_id=692362021-03-30T18:07:39Zbmbouterbmbouter@redhat.com
<ul></ul><p>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.</p>
<p>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.</p>
<p><a class="user active" href="https://pulp.plan.io/users/14917">fao89</a> 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?</p> Ansible Plugin - Task #8478: As a developer, I have performance tests running nightly on CIhttps://pulp.plan.io/issues/8478?journal_id=693542021-04-05T17:18:37Zfao89
<ul></ul><p>maybe we can add some environment variable on CI,
SHOULD_LOAD_DB=True, the tests would check for that and pre-load data when running for cron job</p> Ansible Plugin - Task #8478: As a developer, I have performance tests running nightly on CIhttps://pulp.plan.io/issues/8478?journal_id=772252021-11-17T19:43:23Zpulpbot
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/77225/diff?detail_id=77638">diff</a>)</li><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - DUPLICATE</i></li></ul>