-
Type:
Bug
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Auto-QA
-
High
-
None
-
Fix QA checks for Content Protection tags
-
None
-
Emptyshow more show less
Problem
At times (not every time) content protection tag may be copied into target from source with incorrectly rendered title.
Like in source it was "<1/> CP: blabla" and in target it will be "1/ CP: blabla"
So < and > may be deleted.
This results in incorrect hashes comparison when QA checks for tags in source and target for consistency.
Solution
Change the way how CP tag is checked.
For now CP tag compared with fully rendered body.
In reality more correct way is to compose it from short tag number + source content + target content.
Test
I have no dependable way to reproduce the bug.
For client it had reproduced in cases with segments where only protected content exists and in some segments where user manually copied tags from source to target.
Then on QA check running it resulted QA error in added and removed tags.