Reading: Charting the Course by Rob Sabourin — Chapter 1: "What is Just In Time Testing?"

By -
Takeaways from the Chapter 1



Book: https://link.amazon/B0csD4dQI

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 Oracles to judge whether system behavior is expected or not.
  • Reporting: Documenting findings (passes, failures, blockers, and newly discovered test ideas) enables stakeholders to make informed business decisions.


Final Reflection


Being a skilled tester isn't just about knowing techniques—it's about knowing when to apply them based on context.

In short: Explore early, adapt continuously, refine late, and apply the skills at the right time.

Also, Take AI as a Thought Partner: Don't rely on AI to blindly generate test cases. Use it to challenge your assumptions, uncover blind spots, and feed into your testing heuristics.

References:

Bug Taxonomies - https://bbst.courses/giri-vijayaraghavan-and-cem-kaner-bug-taxonomies-use-them-to-generate-better-tests/

Test Oracles - https://www.thetesttribe.com/wp-content/uploads/2022/02/BBST-Foundations-2.pdf
Location: Bengaluru, Karnataka, India

Popular Posts

JMeter Producing Error: Windows RegCreateKeyEx(...) returned error code 5

By -
After running JMeter.bat on Command Line, Problem java.util.prefs.WindowsPreferences <init> WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5. Cause Environment Resolving the problem The error occurs because java.util.prefs.WindowsPreferences is trying to save information in HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs instead of under HKEY_CURRENT_USER\Software\JavaSoft\Prefs. Windows 7 64-bit The work around is to Open JMeter.bat file as the administrator and so it creates the key HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs.
Read more

Understanding about Contract Testing

By -
Image
Yesterday Morning (9th May 2020), I had good discussion with  Sundaresan  Krishnaswami on " Contract Testing ". I thank  Sundaresan   for his time and sharing his knowledge. It started with an example: The Owner provides the house or Place of Residence to the Tenants. "Rent Agreement" is provided for the house and It contains agreement to use the house. The house comes with like kitchen, living room, bed room, fans, geysers etc.. It also contains who resides and what is the contractual period, obligation (money) etc.. Here, Owner is the Server and Tenant is Client.                                         Client-Server Architecture. Illustrating the same in the E-Commerce Context: In Some Development Companies, There can be two teams developing the Payments and Orders APIs. In B2B or B2C Ecommerce applications, we place an order using web browser through payment methods...
Read more