Reading: Charting the Course by Rob Sabourin — Chapter 1: "What is Just In Time Testing?"
Takeaways from the Chapter 1 Just In Time (JIT) Testing isn't about waiting until the last minute—it’s about continuously gathering test ideas As Soon as Possible and As Late as Possible . As it turns out, I’ve been practicing JIT testing all along; I just didn’t have a name for it. Core Insights Agile: Requirements shift constantly. Testing isn't just executing pre-planned scripts; it's a continuous cycle of learning, observing, and generating new test ideas as new information emerges during a Sprint. Application Testing: JIT principles apply across all layers—from Unit and Integration to Security and Performance testing. Context Switching: Context switches (business pivot, tech changes, re-orgs) are inevitable. Active monitoring turns these shifts into new testing insights and risk indicators. Different Sources: Test ideas come from everywhere—docs, code, client bugs, architecture, and end-user behavior. Use Bug Taxonomies to generate more test ideas and Test Oracle...