[Customer Case]Adding test for invalid release version #13296
Conversation
ColeHiggins2
added
CLI
|
trigger: test-robottelo |
| reposet=REPOS['kickstart']['rhel8_aps']['reposet'], | ||
| releasever=REPOS['kickstart']['rhel8_aps']['version'], | ||
| ) | ||
| Repository.synchronize({'id': rh_repo_id}) |
There was a problem hiding this comment.
Can't you remove the import for this and just do
| Repository.synchronize({'id': rh_repo_id}) | |
| module_target_sat.cli.Repository.synchronize({'id': rh_repo_id}) |
ColeHiggins2
force-pushed
the
test_invalid_release_version
branch
from
e8e24bb to
00b9407
Compare
|
trigger: test-robottelo |
There was a problem hiding this comment.
Looks good, left two comments for @ColeHiggins2 to consider.
PRT failure is unrelated to this PR.
|
|
||
| :expectedresults: Invalid release versions should fail and valid release version should succeed | ||
|
|
||
| :BZ: 1895976 |
There was a problem hiding this comment.
The BZ has medium severity, so I would tend to use :CaseImportance: Medium here instead of the module-default High. Unless there are some other reasons.
| { | ||
| 'organization-id': module_sca_manifest_org.id, | ||
| 'name': name, | ||
| 'release-version': 'ThisShouldNotWork', |
There was a problem hiding this comment.
This could be something random via gen_string(...) or parametrized via invalid_values_list from datafactory. Non-blocking.
|
trigger: test-robottelo |
Adding test to check invalid release versions when updating or creating an activation key using hammer
:BZ: 1895976