Hey Team,
I put A’s 2.35 execution report in the wiki and it looks great, but I want to say something about being unmistakably clear when talking about correct vs incorrect system behavior.
Unmistakable clarity is being so clear that there is no way anyone could misunderstand the message. It is being so clear that if someone was intentionally trying to misrepresent or twist your words into another meaning, they would be unable to do so.
For issue #8, A says:
Heart(add to saved items) icon for the eGiftCard. [7th screen]
But to someone who is not familiar with this particular feature, it is not clear what this means. I have seen this for many years in test automation, specifically in the test pass/fail message at the end of the test. Some examples at Under Armour are:
- “Points earned amount is present!”
- “Some items are checked from WHO DO YOU FOLLOW items”
- “Product is found!”
- “Search results are empty”
The messages in our automation are actually pretty good, but it’s better to be like a real bug report and give expected results and actual results. I am NOT saying we should refactor our code, but going forward, I would prefer to see error messages like:
- “Points earned amount should not be present but is!”
- “No items from WHO DO YOU FOLLOW should be checked but some are”
- “Product should not be found but it is!”
- “Search results should not be empty but they are”
