-
Notifications
You must be signed in to change notification settings - Fork 115
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
CA- merge repo cli test scenarios, ansible collection repo sync and export #15621
CA- merge repo cli test scenarios, ansible collection repo sync and export #15621
Conversation
686405d
to
c79d8e9
Compare
trigger: test-robottelo |
trigger: test-robottelo |
PRT Result
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like we should keep the sync test for the sake of testing it in the Repositories component and let the export (and import) be tested in the ISS component where it actually belongs. We have coverage for export and import already:
robottelo/tests/foreman/cli/test_satellitesync.py
Line 1670 in 95a2ad0
def test_postive_export_import_ansible_collection_repo( |
trigger: test-robottelo |
PRT Result
|
…xport (SatelliteQE#15621) * CA-sync and export ansible collection repos * addressed review comment and keeping only on scenario
Problem Statement
Component audit - SAT-23366
Merge 2 related scenarios
Solution
Merged into
test_positive_export_ansible_collection
Removed testcase
test_positive_sync_ansible_collection
Updated testcase name
test_positive_sync_and_export_ansible_collection
Related Issues
NA
PRT test Cases example
Note:
As per comment from @vsedmik updating file as export and import scenario is already covered in ISS tests