-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test that the vendor field is available for uploaded and synced rpms #680
Comments
I have looked through current pulp-fixtures RPMs and can't find one with vendor data. I will make an issue on pulp-fixtures. |
Blocked until pulp-fixtures issue #54 is closed. |
Unblocked. Kudos to @kdelee. |
kdelee
added a commit
to kdelee/pulp-smash
that referenced
this issue
Jul 10, 2017
Closes pulp#680 Includes a refactor of existing test in pulp_smash.tests.rpm.cli.test_upload
kdelee
added a commit
to kdelee/pulp-smash
that referenced
this issue
Jul 10, 2017
Closes pulp#680 Includes a refactor of existing test in pulp_smash.tests.rpm.cli.test_upload
kdelee
added a commit
to kdelee/pulp-smash
that referenced
this issue
Jul 10, 2017
Closes pulp#680 Includes a refactor of existing test in pulp_smash.tests.rpm.cli.test_upload
nixocio
pushed a commit
to nixocio/pulp-smash
that referenced
this issue
Nov 1, 2017
… RPM package. There are 2 tests: First: 1. Create a repository then upload content with **vendor information** to this repository. 2. Assert that vendor information is present and according to the data that was uploaded. Second: 1. Create a repository then sync content with **vendor information** to this repository. 2. Assert that vendor information is present and according to feed URL. Closes: pulp#680
nixocio
pushed a commit
to nixocio/pulp-smash
that referenced
this issue
Nov 1, 2017
… RPM package. There are 2 tests: First: 1. Create a repository then upload content with **vendor information** to this repository. 2. Assert that vendor information is present and according to the data that was uploaded. Second: 1. Create a repository then sync content with **vendor information** to this repository. 2. Assert that vendor information is present and according to feed URL. Closes: pulp#680
nixocio
pushed a commit
to nixocio/pulp-smash
that referenced
this issue
Nov 1, 2017
There are 2 tests: First: 1. Create a repository then upload content with **vendor information** to this repository. 2. Assert that vendor information is present and according to the data that was uploaded. Second: 1. Create a repository then sync content with **vendor information** to this repository. 2. Assert that vendor information is present and according to feed URL. Closes: pulp#680
nixocio
pushed a commit
to nixocio/pulp-smash
that referenced
this issue
Nov 1, 2017
There are 2 tests: First: 1. Create a repository then upload content with **vendor information** to this repository. 2. Assert that vendor information is present and according to the data that was uploaded. Second: 1. Create a repository then sync content with **vendor information** to this repository. 2. Assert that vendor information is present and according to feed URL. Closes: pulp#680
nixocio
pushed a commit
to nixocio/pulp-smash
that referenced
this issue
Nov 2, 2017
There are 2 tests: First: 1. Create a repository then upload content with **vendor information** to this repository. 2. Assert that vendor information is present and according to the data that was uploaded. Second: 1. Create a repository then sync content with **vendor information** to this repository. 2. Assert that vendor information is present and according to feed URL. Closes: pulp#680
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://pulp.plan.io/issues/2781
The text was updated successfully, but these errors were encountered: