Wednesday, February 23, 2022

Test case driven issue reporting

"It does not work for me. Why? It freezes. Where? In the user details view. How does it look? Let me share a screenshot. I just went there and it rendered for me. Can we get into a screensharing session? ..."

Transaction costs kill productivity. The above neverending dialog can be stopped if we have a bit more appreciation for the written word.

Let us all agree on something: Unless you explain in the form of a replicable test case then nobody should even try to help you out.

You probably know it but a test case must have the following straightforward form which must be replicable, meaning that it must produce the exact same result no matter how many times we repeat the provided steps.

1. Go to ...
2. Click on select ...
3. Type ...
4. Expected result: ...
5. Actual result: ...
The result of this decision? Huge savings for the business. No numbers, sorry, but the dollar value here is, believe me, big enough to get the attention of your CFO.

Followers