Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-01-05T19:02:42ZPulp
Planio Migration Plugin - Test #8041 (CLOSED - COMPLETE): Add tests for RPM migration re-runshttps://pulp.plan.io/issues/80412021-01-05T19:02:42Zttereshcttereshc@redhat.com
<p>Those tests require 2 snapshots.</p>
<p>Snapshot 1:</p>
<ul>
<li>empty repo, no importer, a distributor</li>
<li>another empty repo (to copy content to later), no importer, a distributor</li>
<li>rpm-with-modules repo, on_demand importer, a distributor</li>
<li>rpm-distribution-tree repo, on_demand importer, a distributor</li>
<li>srpm-unsigned repo, on_demand importer, a distributor</li>
</ul>
<p>Snapshot 2:</p>
<ul>
<li>empty repo and its distributor unchanged</li>
<li>copy a package to an empty repo, and its distributor unchanged</li>
<li>rpm-with-modules repo (remove one package, clean orphans), importer feed change, distributor with no changes</li>
<li>rpm-distribution-tree repo unchanged, its importer unchanged, distributor checksum_type change</li>
<li>srpm-unsigned repo unchanged, its importer unchanged, distributor relative path change</li>
<li>rpm-richweak-deps repo (sync, remove one package, no orphan cleanup)</li>
</ul> Migration Plugin - Test #8040 (CLOSED - COMPLETE): Add tests for RPM repo related objects migrationhttps://pulp.plan.io/issues/80402021-01-05T18:50:06Zttereshcttereshc@redhat.com
<p>Use snapshot 1 from <a class="issue tracker-5 status-13 priority-6 priority-default closed" title="Test: Add tests for RPM migration re-runs (CLOSED - COMPLETE)" href="https://pulp.plan.io/issues/8041">#8041</a>.</p> Migration Plugin - Test #7999 (CLOSED - COMPLETE): Extend behavioural testshttps://pulp.plan.io/issues/79992020-12-15T18:49:01Zttereshcttereshc@redhat.comMigration Plugin - Test #7998 (CLOSED - COMPLETE): Add tests for reset endpointhttps://pulp.plan.io/issues/79982020-12-15T18:44:50Zttereshcttereshc@redhat.comMigration Plugin - Test #7934 (CLOSED - COMPLETE): Test migration plan correctness and validationhttps://pulp.plan.io/issues/79342020-12-07T16:23:13Zttereshcttereshc@redhat.com
<p>See the checklist for the use cases that needs to be tested</p> Pulp - Test #4942 (CLOSED - COMPLETE): [EPIC] - Pulp2 - 2.20 https://pulp.plan.io/issues/49422019-06-10T12:33:32Zbherring
<a name="Information"></a>
<h2 >Information<a href="#Information" class="wiki-anchor">¶</a></h2>
<p>As new issues are added for release candidate to P2 for 2.20, compiling all of those issues as related issues to this parent issue.</p>
<p>This ticket allows the release shepherd to keep up with the status of each ticket as QE is heading to Dev Freeze to attempt to stay ahead.</p>
<a name="Current-Topics"></a>
<h3 >Current Topics<a href="#Current-Topics" class="wiki-anchor">¶</a></h3>
<p>These topics will be a subset of Dev release notes.</p>
<p>Just here for quick FYI on scanning:</p>
<ul>
<li>Modularity</li>
<li>Unit Copy Duplication</li>
<li>Issue with libsolv even in building: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1718015" class="external">https://bugzilla.redhat.com/show_bug.cgi?id=1718015</a>
</li>
</ul> Pulp - Test #4846 (CLOSED - COMPLETE): CRUD RepositoryVersionDistributionhttps://pulp.plan.io/issues/48462019-05-17T19:28:54Zbmbouterbmbouter@redhat.com
<p>The RepositoryVersionDistribution is designed to be subclassed and can't be fully tested unless it is subclassed. Thus, the recommended way to test core's functionality is to test it using the AnsibleDistribution from pulp_ansible.</p>
<p>CRUD the PulpDistributor.</p>
<p>1. Create a repo and repo_version with at least 1 file content in it.<br>
2. Create a AnsibleDistribution with 'repository' field set to the repository from step 1. Verify it accepts it.<br>
3. Update the AnsibleDistribution to unset 'repository' and set 'repository_version'. Verify it accepts it.<br>
4. Update the AnsibleDistribution to set both 'repository' and 'repository_version' and verify it <strong>rejects</strong> it. These options cannot be used together</p> RPM Support - Test #4579 (CLOSED - COMPLETE): Automate rpm missing filelisthttps://pulp.plan.io/issues/45792019-03-26T14:44:13ZrochacbrunoContainer Support - Test #4460 (CLOSED - COMPLETE): Test pull from container registryhttps://pulp.plan.io/issues/44602019-02-25T14:21:27Zbherring
<a name="Test-Notes"></a>
<h2 >Test Notes<a href="#Test-Notes" class="wiki-anchor">¶</a></h2>
<ul>
<li>testing `docker pull` against published docker repo... ;</li>
<li>API tests against a published distribution</li>
</ul> Pulp - Test #4344 (CLOSED - WONTFIX): Move pulpcore tests to top-level directory in pulp/pulphttps://pulp.plan.io/issues/43442019-01-21T20:39:16Zbmbouterbmbouter@redhat.com
<p>I believe traditionally tests are not contained in the sourcetree with the the code itself. I think we would move the tests outside of the pulpcore folder itself so the 'tests' are at the top level.</p>
<p>This mirrors the cookiecutter layout for example where 'tests' are at the top level: <a href="https://github.com/audreyr/cookiecutter-pypackage" class="external">https://github.com/audreyr/cookiecutter-pypackage</a></p> Pulp - Test #4259 (CLOSED - COMPLETE): As a user I can sync from a docker registryhttps://pulp.plan.io/issues/42592018-12-11T13:37:49Zbherring
<a name="Notes"></a>
<h2 >Notes<a href="#Notes" class="wiki-anchor">¶</a></h2>
<ul>
<li>evaluate what more we can do in this area (see <a class="issue tracker-5 status-13 priority-6 priority-default closed" title="Test: Test sync of a repository that is missing blobs (CLOSED - COMPLETE)" href="https://pulp.plan.io/issues/4128">#4128</a> and <a class="issue tracker-5 status-13 priority-6 priority-default closed" title="Test: Test sync of a repository that returns a 403 response for a download request (CLOSED - COMPLETE)" href="https://pulp.plan.io/issues/4129">#4129</a> for more information in this area)</li>
</ul> Pulp - Test #4230 (CLOSED - COMPLETE): Test task name and search for task based on their namehttps://pulp.plan.io/issues/42302018-12-05T14:08:12Zkersom
<ul>
<li>Assert that a task has a field name, and that this field is not empty.</li>
<li>Filter the task by its name.</li>
</ul> Pulp - Test #4221 (CLOSED - COMPLETE): As a user, I can skip to various pages for paginated resultshttps://pulp.plan.io/issues/42212018-12-04T13:42:00Zrochacbruno
<p>Test Case</p>
<ol>
<li>Create a significant number of entities (repositories, versions, publications etc)</li>
<li>Using API provide pagination arguments</li>
<li>Assert it is possible to jump from page 1 to page 3 (skipping page 2)</li>
<li>Assert All the items are showed when paginating</li>
</ol> Pulp - Test #4121 (CLOSED - COMPLETE): Test CRUD Docker Publisherhttps://pulp.plan.io/issues/41212018-11-05T18:52:03Zkersom
<p>Add basic test for CRUD Docker Publisher.</p> Pulp - Test #4113 (CLOSED - COMPLETE): Create publications for Docker reposhttps://pulp.plan.io/issues/41132018-10-31T17:59:46Zkersom
<ol>
<li>Evaluate what fixtures should be for this test</li>
<li>CRD a publication using a Docker plugin</li>
</ol>