session #3: "it works on my machine!" closing the loop between development & testing
DESCRIPTION
Session #3: "It Works on My Machine!" Closing the Loop Between Development & Testing Presented by: Joe Shirey & Steve LangeTRANSCRIPT
TEAM SYSTEM: IT’S BIG
“It works on my machine”
Closing the loop between Development and Testing
Joe Shirey/Steven [email protected]/[email protected]
TEAM SYSTEM: IT’S BIG
Agenda
• Overview• Whose Bug is it anyway?• Yours, Mine and Ours• The bug stops here• Bug to the Future• Summary• Q&A
TEAM SYSTEM: IT’S BIG
TEAM SYSTEM: IT’S BIG
Famous Bugs
• 1945 – Harvard Mark II• 1985-1987 – Therac 25• 1990 – AT&T Switches• 1996 - Ariane 5 Flight 501• 2007 – Excel calculation
TEAM SYSTEM: IT’S BIG
Why Test? Why Not?
• Why are we testing?
• What are we testing?
• Who is responsible for testing?
• Do you want it on time or do you want it to be perfect?
• How do you define a good test?
• Bugs are bound to happen, why can’t we just live with it?
TEAM SYSTEM: IT’S BIG
Whose bug is it anyway?
• Picking teams– Beyond Development vs. Test
• Finding bugs– Developer, tester or customer?
• Communicating the status–We know about it, now what?
• It’s fixed, what next?– Likely to resurface?
TEAM SYSTEM: IT’S BIG
Picking Teams
generates
consumes
TEAM SYSTEM: IT’S BIG
Finding Bugs
• Developers, testers or customers?
• Is it important?• Understanding values
TEAM SYSTEM: IT’S BIG
V-Model
TEAM SYSTEM: IT’S BIG
Communicating Status
TEAM SYSTEM: IT’S BIG
What’s Next?
• Where do we go from here?
• We’ve identified :• our teams,• our bug spotters• how they will be
fixed
• Will we have to repeat this during the next iteration?• Yes, if we don’t
document and learn from this cycle.
• No, if we do apply these lessons to our process.
TEAM SYSTEM: IT’S BIG
DEMO
Work Items for All
TEAM SYSTEM: IT’S BIG
Yours, Mine and Ours
• Lines of code written• Number of bugs
closed• Shipping on time• On to the next project
• Test Results gathered• Number of bugs
opened• Shipping quality• Clearing the backlog
So, what’s the common ground?
TEAM SYSTEM: IT’S BIG
DEMO
The Bug’s Life
TEAM SYSTEM: IT’S BIG
The bug stops here
• Communicating Results• Are your statistics realistic?• Reinventing the wheel• Recognition
TEAM SYSTEM: IT’S BIG
DEMO
We’re in this together, making sense of results
Remaining Work
TEAM SYSTEM: IT’S BIG
Quality Indicators
TEAM SYSTEM: IT’S BIG
Quality Indicators
TEAM SYSTEM: IT’S BIG
Scope Creep
TEAM SYSTEM: IT’S BIG
Reactivations
Bug Rates
Requirement Details
TEAM SYSTEM: IT’S BIG
Bug to the Future
2010…
• Hierarchal work items
• Eliminating “no-repro” bugs
• Test impact analysis• Test prioritization• Viewing the quality
of requirements and the value of testing
• Reduce the manual effort for automation-capable tests
TEAM SYSTEM: IT’S BIG
In summary
• The most important tool is communication between dev and test.
• Quality belongs to everyone, as does lack of.
• Automation is a good friend to have.• Respect for your work, your
colleagues, your customers.