How Do You Know When Your Product is Ready to be Shipped?
summary
Evaluates criteria and signals used to decide when a software product is ready for release, drawing on practices from distributed teams and tools such as rultor and Java-based development. Focuses on practical readiness checks, quality gates and process-level indicators that inform shipping decisions rather than theoretical definitions.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:48"-to verify that the software product is fit for use, meets the requirements, performs its functions within an acceptable time, is sufficiently usable." Wikipedia
- 2:26"Testing is the process of executing a program with the intent of finding errors" -Glenford Myers The Art of software Testing
- 4:00A good software doesn't have bugs
- 4:37"You cannot test a program to guarantee that it is error free" and "It is impractical, often impossible, to find all the errors in a program" -Glenford Myers The Art of Software Testing
- 5:50When do we stop?
- 7:22All scripts pass
- 9:25Time is over
- 12:08Money is over
- 13:22Bug targets reached
- 14:32Since the goal of testing is to find errors, why not make the completion criterion the detection of some predefined number of errors?
- 15:58Software is released for use, not when it is known to be correct, but when the rate of discovering errors slows down to one that management considers acceptable" -David West "Object Thinking
- 24:42D#2 How to motivate?
- 29:53ART SOFTWARE TESTING
