1. BPMN (Business Process Model and Notation):
A standard graphical notation that communicates the steps and interactions in a business process. BPMN is a common language bridging the understanding gap between business stakeholders and technical experts.
2. Collaboration:
The cooperative effort of team members working together to achieve a shared goal. Collaboration might involve creating, reviewing, and maintaining test scenarios together in the context of testing.
3. Continuous Deployment (CD):
A software development practice where code changes are automatically deployed to a production environment after they pass all stages of testing and validation. CD aims to accelerate software delivery while maintaining high quality and reliability.
4. Continuous Integration (CI):
A software development practice where developers frequently merge changes into a principal code repository. The changes are automatically tested to identify and resolve issues early, promoting a more robust, error-free codebase.
5. Gherkin:
A domain-specific language used to describe software system behavior in a readable, structured format. Tools like Cucumber, SpecFlow, and Behave, use Gherkin as the foundation for creating test scenarios.
6. Real-Time Visibility:
The capability to observe, in real time, the changes and updates made by team members in a shared workspace. This feature fosters effective collaboration and ensures all contributors share the same understanding of the work in progress.
7. Test Automation:
Using software tools and frameworks to execute test cases automatically. This process minimizes the need for manual intervention, enhancing testing speed and precision.
8. Test Case:
A specified set of test inputs, execution conditions, and expected outcomes crafted to verify whether a particular software function or feature behaves as intended.
9. Test Management:
The comprehensive process of planning, designing, executing, and monitoring software tests. The primary objective is to ensure the delivery of superior-quality software products.
10. Test Scenario:
A comprehensive description of a system's behavior, outlining the necessary steps to verify that behavior. Test scenarios, often written in Gherkin, form the backbone of test case development.
11. Test Suite:
An organized collection of test cases grouped and executed together to validate a specific software component or functionality.