[1LP][RFR] Tests tagging on provider side#8543
Conversation
|
PRT errors: |
b502e48 to
b9231b0
Compare
013822c to
304b84e
Compare
|
@mshriver please check PRT failures |
fc84586 to
984409e
Compare
984409e to
5e7d06c
Compare
Rebased from Ruslana Babyuk's original commits, updated for more recent test patterns
Add casecomponent Tagging, update test case docblocks Update MapTag.delete table row filter, fix test_tag update call Update test fixtures and REST test failure handling for tag tests
5e7d06c to
676e900
Compare
|
@ganeshhubale @lina-nikiforova @digitronik please take another look, addressed the comments. At this point there are some PRT failures, but I would like the FA owner to address those. |
digitronik
left a comment
There was a problem hiding this comment.
@mshriver LGTM 👍 Thanks for this PR.
Just one personal request and string formatting. Moving to 1LP WIPTEST
| current_tag_value = view.entities.summary('Labels').get_text_of(tag_label) | ||
| soft_assert( | ||
| current_tag_value == tag_value, ( | ||
| 'Tag values is not that expected, actual - {}, expected - {}'.format( |
There was a problem hiding this comment.
keying please for such formatting.
I would catch msg in variable for better readability.
|
LGTM, I will look further into the failures in a separate PR as it's my FA |
|
since changes look good to me and @lina-nikiforova promises to handle failed PRT, I'm merging this PRT. |
Rebased from Ruslana Babyuk's original commits in #7320, updated for more recent test patterns.
I would like to leave any remaining test failures to the FA owner to address.
{{ pytest: --long-running -vvvv --use-provider complete cfme/tests/cloud/test_tag_mapping.py cfme/tests/configure/test_tag.py }}