[Customer Case] Applied Errata report with invalid errata #15378
Conversation
ColeHiggins2
added
No-CherryPick
| :CaseImportance: High | ||
|
|
||
| :BZ: 2176368 | ||
| """ |
There was a problem hiding this comment.
| """ | |
| :customerscenario: true | |
| """ |
| }, | ||
| } | ||
| ) | ||
|
|
There was a problem hiding this comment.
Do you think any other assertion can be implementated after generating errata report?
There was a problem hiding this comment.
We talked about this in chat, There are not any good ways to make an assertion here. All we need to test is that this report is generated. A failing tests is a good enough indicator here
| :CaseImportance: High | ||
|
|
||
| :BZ: 2176368 |
There was a problem hiding this comment.
| :CaseImportance: High | |
| :BZ: 2176368 | |
| :BZ: 2176368 | |
| :customerscenario: true |
No need to declare the CaseImportance again (same level as module-wide), but we should provide customerscenario for customer cases.
| activation_key = target_sat.api.ActivationKey( | ||
| environment=function_lce, organization=function_org | ||
| ).create() | ||
| cv = target_sat.api.ContentView(organization=function_org).create() |
There was a problem hiding this comment.
| activation_key = target_sat.api.ActivationKey( | |
| environment=function_lce, organization=function_org | |
| ).create() | |
| cv = target_sat.api.ContentView(organization=function_org).create() |
We could probably use function_ak_with_cv fixture instead (and function_promoted_cv it uses inside).
There was a problem hiding this comment.
Had some issues with lce using that fixture, Test was failing, Lets just keep it how it is
There was a problem hiding this comment.
I have also found that fixture fails to setup as expected
|
trigger: test-robottelo |
|
PRT Result |
Satellite-QE
added
the
PRT-Passed
ColeHiggins2
added
AutoMerge_Cherry_Picked
…E#15378) * adding tests for invalid errata * addressing comments
Customer case automation for generating an applied errata report after applying an invalid errata.
All we need to test here is to make sure the report is generated without failure. However, because we never actually apply any errata, the report is an empty list. We can just assume it generated if there are no failures, but if anyone has any ideas on a potential assert that can be made im open to suggestions.