Exploratory testing gives a team a practical way to look for failures that planned feature checks may miss. Testers actively try to break the system rather than only confirming expected behavior. section 11.3
Once behavior-driven development helps guide feature work, the team can widen its feedback loop: generate unusual inputs, apply heavy load, observe failures, and improve the product incrementally. section 11.3
Trying to break the system
A team floods the application with load or enters special characters into input fields. Repeated scenarios can then be automated with Selenium or Cypress. section 11.3
