Better Software Classic Testing Mistakes
•Als PPT, PDF herunterladen•
5 gefällt mir•7,870 views
![Classic Testing Mistakes: Revisited Matthew Heusser [email_address] Presented at the Better Software Conference San Francisco, CA - Sept. 21st , 2005 Contributing peer reviewers: James Bach Paul Carvalho Michael Kelly Harry Robinson](https://image.slidesharecdn.com/bettersoftwareclassictestingmistakes-1233295123348869-1/85/better-software-classic-testing-mistakes-1-320.jpg)
![Organization ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Better Software Classic Testing Mistakes
Ähnlich wie Better Software Classic Testing Mistakes (20)
Mehr von nazeer pasha
Mehr von nazeer pasha (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Better Software Classic Testing Mistakes
- 1. Classic Testing Mistakes: Revisited Matthew Heusser [email_address] Presented at the Better Software Conference San Francisco, CA - Sept. 21st , 2005 Contributing peer reviewers: James Bach Paul Carvalho Michael Kelly Harry Robinson
- 3. On the shoulders of pioneers
- 6. Classic Mistake #1: De-humanize the test process Test Management Mistakes AKA Management by Spreadsheet, Management by Email, Management by MS Project …
- 7. Classic Mistake #2: Testers Responsible for Quality “ It’s strange that QA let that bug slip through” Test Management Mistakes
- 8. Classic Mistake #3: IV&V Determines ship date Do they really? Test Management Mistakes
- 15. Mistake #10: Mine Field Test Automation Test Automation Mistakes
- 18. Classic Mistake #13: Over-reliance on scripted testing All the testing we did, meticulously pulling down every menu and seeing if it worked right, didn't uncover the showstoppers that made it impossible to do what the product was intended to allow. Trying to use the product, as a customer would, found these showstoppers in a minute. - Joel Spolsky, JoelOnSoftware.com Test Strategy Mistakes
- 20. Classic Mistake #15: Test ‘Engineers’ and ‘Executors’ Test Strategy Mistakes
- 22. Mistake #17: Trying to fix things beyond your reach The Meta-Mistake
- 23. Don’t treat the symptoms Find & Fix the root cause!
- 25. Root Cause #2: Translation Problems Example: - “You need to completely test this module” Root Causes
- 33. Bonus Section
Hinweis der Redaktion
- Reducing altitude, he spotted a man on the ground and descended to shouting range.. "Excuse me," he shouted. "Can you help me? I promised my friend I would meet him a half hour ago, but I don't know where I am." The man below responded: "Yes. You are in a hot air balloon, hovering approximately 30 feet above this field. You are between 40 and 42 degrees North Latitude, and between 58 and 60 degrees West Longitude." "You must be an tester," responded the balloonist. "I am," the man replied. "How did you know?" "Well," said the balloonist, "everything you have told me is technically correct, but I have no idea what to make of your information, and the fact is I am still lost." Whereupon the man on the ground responded, "You must be a manager." "That I am" replied the balloonist, "but how did you know?" "Well," said the man, "you don't know where you are, or where you're going. You have made a promise which you have no idea how to keep, and you expect me to solve your problem. The fact is, you are in the exact same position you were before we met, but now it is somehow my fault.“ Now - Why is that joke funny? Because it happens at work, every day. And all that time spent complaining about each other is time not spent building solutions – it’s productivity lost. This talk is about those productivity timesinks – and what we can do about them.