Behavior-Driven Development (BDD) initially aimed to allow end users to write application specifications in Gherkin Language, enabling QA engineers to translate these into code, often using Selenium, before implementation. The process was intended to build business user specifications and create regression tests but faced challenges such as the complexity of Gherkin for business users, reliance on HTML/XML structures, and difficulty in implementing specifications before feature release. BDD often did not justify its overhead, leading to the development of BDD 2.0 or Specification-Driven Development (SDD), which addresses these issues by using plain English commands that are executable without additional coding, eliminating reliance on underlying web structures and allowing business users to write domain-specific executable specifications. The only known implementation of SDD is testRigor, which facilitates modularity and user-friendly interaction by enabling business users to directly create test scripts in their own language.