Tech
Good QA Systems Reduce Ambiguity
A lot of QA work is not really test execution.
It is ambiguity management.
What does this requirement mean?
Is this visual difference intentional?
Did the test fail because of the product, data, browser, or test code?
Does this issue block the release?
When testing systems are weak, every failure starts a meeting.
When they are strong, the evidence narrows the decision before the conversation begins.
Spreadsheets are often a symptom
Many teams still manage te...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to