How to (Not) Use Testers Properly
summary
Talk examines gaps between developers and QA on a Java project and proposes practices to align their work. It discusses Test cases as Code, combining unit, e2e, and manual testing, and collecting test results in a single place to get a real view of quality using both new and established tools.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:13Why testing matters
- 5:27Modern team problems
- 11:45Testing approaches compared
- 23:39Automated vs manual tests
- 33:30Test creation time
- 40:30Test coverage analysis
- 47:09Ideal testing team
- 57:42Implementing new processes
- 1:00:48Q&A
related talks
21mImproving Quality Through Effective Communication Between Tester and Developer
36mWhole team quality: In the same boat or up the creek?
36mTesting: Where the Developer's Work Ends and the Tester's Begins
51mQuality Assurance vs. Testing
49mDeveloper + tester = quality++
53mEssential Tools for Improving Test Code Quality
46mDeveloper + Tester = Quality++
37mWe Are The Testers: You Will Be Assimilated
