What’s the difference between quality and testing?
13
What’s the difference between QA and testing? September 2014 Joanna Forbes – Kiandra IT
-
Upload
michelle-devanny -
Category
Technology
-
view
88 -
download
1
description
Presented by Joanna Forbes, Software QA Lead, Kiandra IT The terms Quality and Testing are frequently used interchangeably, but they’re not the same thing. So what is the difference between the two? Quality assurance occurs throughout a software project, not just when code is being tested. An understanding of the differences between the two terms and how they are applied can help a team become more productive and increase their ability to deliver successful projects. This session will describe the differences between the terms and provide practical examples of what quality is and how to achieve it.
Transcript of What’s the difference between quality and testing?
What’s the difference between QA and testing?
September 2014Joanna Forbes – Kiandra IT
● Who am I?● What’s this all about?● Why does it matter?
Introduction
“Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often.” Steve C McConnell, Code Complete: A Practical Handbook of Software Construction
Is Quality the same as testing?
● depends on your client● may be subjective or objective● it is negotiable (to an extent)● it’s the things we do to avoid defects
getting into the system in the first place
What is quality?
You can’t have everything.
How much quality?
● your agile team● (that means you, me, the client)
So who is responsible for quality?
How do we do quality?
● The product owner and key stakeholders decide what their quality requirements are
● team defines “Done”● team does things in a way that reduces
the likelihood of defects being introducedo ensure user stories and acceptance criteria are
accurate, clear and unambiguous, testableo coding standardso manage environments and data
How do we “do” Quality?
Testing!● acceptance criteria and stories● code review ● unit test● functional testing● UI testing
How do we measure quality?
● gathering informationo how the software works (or doesn’t)
● evaluating informationo what are the implications of this information for
the stakeholders - does it meet their quality requirements? Is it “done”?
● communicatingo sharing with the team and stakeholders in a way
that enables informed decision-making
What is testing?
We’re all going to save the galaxy together
There’s no “testing police”
● Quality is different from testing● Quality can’t be “tested in” for a
system● Testing supports quality by
evaluating quality requirements and providing information in order for teams to make informed decisions.
● Quality is a team responsibility
In conclusion
Questions?
