“Requirements are NOT Clear”.
Yes, we need better-drafted requirements!
But, at the same time, we need to stop expecting stakeholders to write down all tacit knowledge (understanding) as an explicit requirement.
Requirements & Desirements are both important 🙂
“We don’t have enough time for Testing”
Yes, we need to stop taking time away from testing.
But, at the same time, testing can go on and on. Understand the law of diminishing returns & the importance of sampling and tradeoffs 🙂
There will never be enough time for full testing
“Thinking of Testing as Test cases or checking work”
Or, “Thinking of Testing as an object rather than an event.”
Visualizing objects is simple to count, manage, think and talk about.
Showcasing exploration and experimental activities is tough IMO. SBTM is hope though 🙂
“Calling Testing, Manual”
Like any other field, there are some manual things that will come no matter what you do!
However, the sad part is that this word has got stuck with testing. I wish it could be changed!
“People calling Testers, Quality Assurance”.
Quality Assurance business is a complex topic when it comes to software.
When we all know that no one can really “assure” quality.
QA = Quality Assistance or Quality Advocates?
How do that matters?
What matters: Is there a problem here? or is it not?
“Calling out Automating Test Cases (Checks) as Automating Testing.”
You can never automate testing, you just automate the execution or trigger of the execution or both 🙂
Testing is a social process, and not an industrial manufacturing process.
“Detailed Test Steps Syndrome”
People still believe that till everything is not written down in the tiniest of details, people won’t be able to understand.
Imagine if requirement writers wrote docs like this, you will soon end up with a production code but in the English language.
Asking testers to create test cases for each step is equivalent to asking developers to create a UML diagram for every step. This was done in the 90s, we are in 2023 now.
“Love for Code Coverage and synonymizing it with great quality.”
Code coverage is fine but let’s talk about the total types of coverages that we should be thinking of?
SFDIPOT: Structure, Function, Data, Interface, Platform, Operations, Timing!
No matter what they say at first, it’s always a people’s problem. – Jerry Weinberg
Testing being socially very hard to do, the people problems often aggregates 🙂
Newbie Testers often get into a hostile environment 🙁