Session #3: "It Works on My Machine!" Closing the Loop Between Development & Testing
of 26
/26
-
Author
steve-lange -
Category
Technology
-
view
1.626 -
download
1
Embed Size (px)
description
Session #3: "It Works on My Machine!" Closing the Loop Between Development & Testing Presented by: Joe Shirey & Steve Lange
Transcript of Session #3: "It Works on My Machine!" Closing the Loop Between Development & Testing
- 1. It works on my machine Closing the loop between Development and Testing Joe Shirey/Steven Lange [email protected]/[email protected]
- 2. Agenda Overview Whose Bug is it anyway? Yours, Mine and Ours The bug stops here Bug to the Future Summary Q&A
- 3. Famous Bugs 1945 Harvard Mark II 1985-1987 Therac 25 1990 AT&T Switches 1996 - Ariane 5 Flight 501 2007 Excel calculation
- 4. 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 cant we just live with it?
- 5. 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? Its fixed, what next? Likely to resurface?
- 6. Picking Teams producer Development generates non-mgmt business technical customer test Management consumes Business Technical
- 7. Finding Bugs Developers, testers or customers? Is it important? Understanding values
- 8. V-Model
- 9. Communicating Status
- 10. Whats Next? Where do we go from here? Weve identified : our teams, our bug spotters how they will be fixed Will we have to repeat this during the next iteration? Yes, if we dont document and learn from this cycle. No, if we do apply these lessons to our process.
- 11. DEMO Work Items for All
- 12. 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, whats the common ground?
- 13. DEMO The Bugs Life
- 14. The bug stops here Communicating Results Are your statistics realistic? Reinventing the wheel Recognition
- 15. DEMO Were in this together, making sense of results
- 16. Remaining Work
- 17. Quality Indicators
- 18. Quality Indicators
- 19. Scope Creep
- 20. Reactivations
- 21. Bug Rates
- 22. Requirement Details
- 23. 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
- 24. 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.
- 25. Q&A Joe Shirey/Steven Lange [email protected]/[email protected]
