gniquyij.github.io

QA Not-To-Do

Here are the things I’ve been trying to avoid as a Quality Assurance (hereinafter referred to as ‘QA’), in no particular order.

Make an assumption without a validation.
- Developers always assume no bugs in their code.
No curiosity.
- What motivates you to figure out what happened? Money?
No documents.
- Can you remember everything?
No expectations.
- When you don’t know what you are going to test, what are you going to test?
No patience.
- What can you do without patience?
No priority.
- You would not have time for a blocking issue cause you’ve spent your time on a non-blocking.
No scope.
- People will define the scope if you don’t.
Repeat yourself.
- People think QA is a job requiring repeating - once found an issue, reproducing, debugging, verifying, etc.. Is there any other way to get them done?
Think dependently.
- Multi inputs, multi outputs?