1. “It works on my machine”
Closing the loop between
Development and Testing
Dave McKinstry
Principal Consultant – Notion Solutions, Inc
dmckinstry@notionsolutions.com

2. Agenda
Overview
•
Whose Bug is it anyway?
•
Yours, Mine and Ours
•
The bug stops here
•
Bug to the Future
•
Summary
•
Q&A
•

3. 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?

4. 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?

5. Picking Teams
• producer
• Development
generates • non-mgmt
• business
• technical
• customer
• test
• Management
consumes • Business
• Technical

6. Finding Bugs
• Developers, testers or customers?
• Is it important?
• Understanding values

7. Communicating Status

8. 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.

9. DEMO
Work Items for All

10. Yours, Mine and Ours
Lines of code written Test Results gathered
• •
Number of bugs closed Number of bugs opened
• •
Shipping on time Shipping quality
• •
On to the next project Clearing the backlog
• •
So, what’s the common
ground?

11. DEMO
The Bug’s Life

12. The bug stops here
Communicating Results
•
Are your statistics realistic?
•
Reinventing the wheel
•
Recognition
•

13. DEMO
We’re in this together, making sense of results

18. • 2010…
Bug to the Future
•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

19. 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.

20. Some Resources
• http://msdn.microsoft.com
– Documentation, references and samples
• http://www.teamsystemrocks.com
– Training Videos, Team System News and other Blogs
• http://www.codeplex.com
• http://www.notionsolutions.com
• http://weblogs.asp.net/dmckinstry
• http://www.tsug-ve.com
• dmckinstry@notionsolutions.com

21. Q&A