Explore chapters and articles related to this topic
Adaptive Life Cycle Models
Published in Gary L. Richardson, Brad M. Jackson, Project Management Theory and Practice, 2018
Gary L. Richardson, Brad M. Jackson
Behavior-driven development (or BDD) is an agile software development technique that encourages collaboration between developers, quality assurance (QA) and non-technical or business participants in a software project. It focuses on obtaining a clear understanding of desired software behavior through discussion with stakeholders. It extends TDD by writing test cases in a natural language that non-programmers can read. Behavior-driven developers use their native language in combination with the ubiquitous language of domain-driven design to describe the purpose and benefit of their code. This allows the developers to focus on why the code should be created, rather than the technical details, and minimizes translation between the technical language in which the code is written and the domain language spoken by the business, users, stakeholders, project management, and so forth (North, 2018).
TestOptimal
Published in Paul C. Jorgensen, The Craft of Model-Based Testing, 2017
The TestOptimal Suite is a package of MBT tools for both functional (specification-based) and load/performance testing. It includes the following products: BasicMBT—supports modeling and test case generation for either manual or offline testing. Generated test cases are saved to either text files or Excel spreadsheets.ProMBT—supports modeling and test automation for web-based and user interface applications. Both data-driven testing and combinatorial testing are supported, with connection to a background database. There is also the possibility of rule-based test data design to optimize testing efficiency.EnterpriseMBT—supports concurrent system modeling and automated load and performance testing.DataDesigner—offers rule-based design of combinatorial test data using the well-known orthogonal array algorithm. Supports pairwise, three-wise, …, n-wise test case generation.Behavior-Driven Testing/Behavior-Driven Development (BDT/BDD)—creates features and test scenarios in BDT/BDD style: GIVEN/WHEN/THEN. Combined with the power of MBT to design the efficient test automation suite for web, windows UI applications, and non-UI processes/interfaces.Test data designer—aggregates and summarizes test execution, test coverage, and requirement traceability in Dashboard charts and reports. Configurable Key Performance Indicator (KPI) can be subscribed by individual test engineer’s IDE.RuntimeMBT—Runtime servers are used as dedicated QA servers to run test models and for a large-scale load and performance testing.SvrMgr—SvrMgr is used to manage Runtime servers, acting as a central repository for models and test execution results. SvrMgr is responsible for distributing model updates to all Runtime servers and dispatch models to run on appropriate Runtime servers.
Creating Formal Models from Informal Design Artefacts
Published in International Journal of Human–Computer Interaction, 2023
Judy Bowen, Benjamin Weyers, Bowen Liu
In 2003, Agiledox, which some consider the predecessor of behaviour-driven languages and frameworks such as Gherkin and Cucumber (discussed later) was created by Stevenson (Stevenson, n.d.). Agiledox is a tool that automatically generates simple documentation from the method names in JUnit test cases, providing a way of tying together different parts of the development process (in this case using the testing procedures to assist with user documentation). Later, North introduced Behaviour Driven Development (BDD) (North, 2006), an agile software development process that built on the ideas of Test Driven Development (Beck, 2002). BDD combines the practices, techniques and principles of Test Driven Development, Acceptance Test Driven Development (Acceptance Test Driven Development (ATDD), n.d.) and Domain-Driven Design (What is Domain-driven design,2007). The key concept of BDD is that it supports “…implementing an application by describing its behaviour from the perspective of its stakeholders” (North, 2009).