Adopt

• 1. Behavior Driven Development (BDD)

  Sub Category: Methodology Placement Reason: Growing across IT industry. BDD offers more precise guidance on organizing the conversation between developers, testers and domain experts Description: Behavior-driven development (BDD) is an Agile software development methodology in which an application is documented and designed around the behavior a user expects to experience when interacting with it
• 2. Test Driven Development (TDD)

  Sub Category: Methodology Placement Reason: To write simple and just enough code. Provides quick Feedback. Standard development practice. Description: Test-driven development (TDD) is a software development process relying on software requirements being converted to test cases before software is fully developed
• 3. Unit Testing

  Sub Category: Testing Placement Reason: Best practice verify code functionality as atomic as possible and automated Description: A unit test exercises the smallest piece of testable software in the application to determine whether it behaves as expected
• 4. Integration Testing

  Sub Category: Testing Placement Reason: Best practice to verify the integration of microservices Description: An integration test verifies the communication paths and interactions between components to detect interface defects
• 5. Component Testing

  Sub Category: Testing Placement Reason: A component test limits the scope of the exercised software to a portion of the system under test, manipulating the system through internal code interfaces and using test doubles to isolate the code under test from other components. Description: A component test limits the scope of the exercised software to a portion of the system under test, manipulating the system through internal code interfaces and using test doubles to isolate the code under test from other components
• 6. Consumer Driven Contract Testing

  Sub Category: Testing Placement Reason: An integration contract test is a test at the boundary of an external service verifying that it meets the contract expected by a consuming service. Description: An integration contract test is a test at the boundary of an external service verifying that it meets the contract expected by a consuming service
• 7. End-To-End Testing

  Sub Category: Testing Placement Reason: Test Level in projects. Description: An end-to-end test verifies that a system meets external requirements and achieves its goals, testing the entire system, from end to end
• 10. Screenplay Pattern

  Sub Category: Testing Placement Reason: ScreenPlay Pattern encourages better software engineering practices, and thus makes the tests faster to write and easier to maintain in the long term. Description: The Screenplay Pattern is a user-centric model with users and external systems interacting with the system under test represented as actors
• 12. Agile

  Sub Category: Methodology Placement Reason: Highly used across IT industry and standard Development methodology Description: Agile software development is more than frameworks such as Scrum, Extreme Programming, or Feature-Driven Development (FDD). https://www.agilealliance.org/agile101/
• 13. Scrum

  Sub Category: Methodology Placement Reason: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. Description: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems
• 14. Kanban

  Sub Category: Methodology Placement Reason: Kanban is a method applied across all fields of work to help teams drive down costs and become more efficient by visualizing and improving workflows. Description: Kanban Board is a visual representation of the Agile task boards

Trial

• 8. Chaos Testing

  Sub Category: Testing Placement Reason: I want to learn about. Description: Chaos testing is a technique for testing software systems that are under the influence of external forces, such as external events, such as a network outage, or external processes, such as a process crash

Assess

• 9. Load- and Performance-Testing

  Sub Category: Testing Placement Reason: Test Discipline in projects. Description: Load and performance testing is the process of putting demand on a system and measuring its response
• 15. DevOps

  Sub Category: Methodology Placement Reason: DevOps is important because it's a software development and operations approach that enables faster development of new products and easier maintenance of existing deployments. Description: DevOps is a culture that enables formerly siloed roles—development, IT operations, quality engineering, and security to coordinate and collaborate to produce better, more reliable products

Hold

• 11. Page Object Model

  Sub Category: Testing Placement Reason: Page Objects cause problems like duplicate code, missing waits, and messy inheritance. Description: Page Object Model, also known as POM, is a design pattern that creates an object repository for storing all web elements