This document discusses various myths, truths, and areas of chaos related to quality assurance (QA). It addresses myths such as testing being a fading job, QA not coding, and artifacts only being for QA. It also discusses truths around QA involvement in refinement, stakeholders not understanding QA's value, and testing not starting after development. Finally, it examines areas of chaos around differences between iterative and incremental development and attributing bugs to individuals.

1. MYTH, TRUTH & CHAOS IN QA
NITHIN SS

2. ABOUT ME
SENIOR QA
AUTOMATION ENGINEER
ADMIN - COMMUNITY DRIVEN BLOG

3. ABOUT MY FAVE
▸ We are operating in MY, SG, ID
▸ Local Discovery App + Digital Merchant
Platform that empowers merchants to grow
and connect with their customers in a whole
new way
▸ We deliver seamless payment experience and
merchant rewards
MY TEAM
We always have fun while getting things done!!!

4. TESTING IS A SKILL. WHILE THIS MAY COME
AS A SURPRISE TO SOME PEOPLE IT IS A
SIMPLE FACT
Fewster and Graham

5. QA IS THE END USER OF A PRODUCT
▸ QA can identify & highlight problems that threaten the value of product to
people who matter
▸ Our role is to “guarantee quality” so that the product will be built with
minimum failures, which eventually satisfies the end users
▸ QA should evolve into Quality Ambassador who preaches quality across the
teams
MYTH!!!

6. IS TESTING A FADING JOB??
▸ Answer is NO!!!
▸ No matter how big the evolution of technology in future the flow of “analyse-
design-develop-test-deploy” will remain the same
▸ Even the vaccine for COVID 19 will undergo testing phase
CHAOS!!!

7. QA DOES NOT CODE
▸ QA is an integral part of the team
▸ How we are different is with our impeccable test craftsmanship
▸ It’s a traditional mindset. There should be no such division in a
multidisciplinary team
▸ Now it’s more like a combination of Tech + Test Skills
▸ Knowledge of tools & coding will only support us not replace our
effort
▸ Everyone can learn to do EVERYTHING!!!!
MYTH & CHAOS!!!

8. QA HAS TO PARTICIPATE IN REFINEMENT
▸ I would say, QA should involve from Inception stage
▸ Being involved earlier helps us to communicate more comprehensive scenarios
which other might not have thought of
▸ “The product is not only developed by several hands, but also defined by
several hands”
TRUTH!!!

9. THE STAKEHOLDERS/DEV’S DON’T KNOW WHAT QA DOES / VALUE OF QA
▸ Sometimes, we fail to show real value of work
▸ We are seen as bottlenecks or blockers!!!
▸ The QA team brings a broader perspective to the project which comes from a deep
understanding of both development and process business requirements
▸ So what we can do?
▸ We metrify our work : presenting graphs about the latest rounds of automated tests,
tests included in the release, how many fails, execution timeframe, resources involved,
why and what action is taken for correction, among others that make sense for your
project (This should be prepared according to targeted audience)
TRUTH!!!

10. THE TESTING STARTS WHEN DEVELOPMENT IS OVER
▸ Testing is about asking questions from the initial stages itself
▸ Identify the risk
▸ What included in the sprint
▸ How it works
▸ How we ensure the Testability
▸ Its not started when all the cards are moved to “QA Pending” column
MYTH!!!

11. QA ARTIFACTS ARE MEANT FOR QA TEAM ONLY
▸ Sharing our Plan and Scenarios to Product Team might help to identify some
missing requirements or impacted areas
▸ Its good to share our test strategy / test plan to devs so that they can test and
ensure quality before passing to QA
▸ Its our responsibility to educate others on testing concepts which helps to
mitigate risks later
▸ Quality is a Team Effort
MYTH!!!

12. AGILE: ITERATIVE AND INCREMENTAL, ARE THEY SAME???
▸ Incremental development is achieving
final result by perfecting piece by piece
▸ Iterative development is achieving final
result with increasing perfection in stages
CHAOS!!!
Image credits : Jeff Patton, Agile thought leader

13. WHY DID YOU MISS THIS BUG!!!
▸ Old age question but still FRESH!!!!
▸ Its not about the number of bugs we find, its about the value and influence of
the bugs we find
▸ An Awesome tester might find just 1 BUG : From the book “Buddha in Testing”
▸ Do RCA for the bug, and if it reveals it as a miss take it as a learning
▸ All our hands are in that failure, not just one’s!
CHAOS!!!

14. QUESTIONS????
MANY BUGS FIND US. WE
FIND A FEW