BEHAVIOR DRIVEN DEVELOPMENT BDD GUIDE TO AGILE PRACTICES. Director, Strategic Solutions

Transcription

1 BEHAVIOR DRIVEN DEVELOPMENT BDD GUIDE TO AGILE PRACTICES Presenter: Joshua Eastman Director, Strategic Solutions

2 ABOUT THE SPEAKER Josh has over seven years of experience as an accomplished software testing and development professional. Josh Eastman Director, Strategic Solutions 3 3

3 GROUP EXERCISE

4 GROUP EXERCISE Imagine you are a QA manager You have 25 direct reports (QA Analysts) 6 Agile lines 2 Run (Production Support) + 4 Build Business demand is expected to nearly double in the next year System defect rate = 5 defects / 1,000 release hours Production defect rate = 1.75 defects / 1,000 release hours How can you possibly prepare for the increase in business demand and try to lower your defect rates or increase quality simultaneously? 5

5 SOLUTION Employ a deliberate emphasis on quality implementing an industry best practice Behavior Driven Development (BDD) with a determined focus on incorporating automation. Business Demand Increases By 187% - 354,739 release hours compared to 190,008 release hours System Defect Rate Decreased 1.43 defects/1000 release hours compared to 5 defects/1000 release hours Production Defect Rate Decreased 1.3 defects/1000 release hours compared to 1.75 defects/1000 release hours Direct Reports Increased Only by 7 32 compared to 25 Fortune 100 Company Year X Year X+1 Business Demand (Release Hours) 190, ,739 System Testing Defects Production Defects Testing Resources Annual Savings $1,191,360 $1,183,540 $1,365,900 TOTAL ANNUAL BUSINESS VALUE ($) $3,740,800 6

6 FOUNDATIONAL UNDERSTANDING

7 MOST ORGANIZATIONS USE SOME FORM OF AGILE Agile emphasizes empirical feedback, team self management, and striving to build properly tested product increments within short iterations. 8

8 DIFFERENCES BETWEEN TDD, BDD + ATDD Acceptance Test Driven Development (ATDD) is a form of Behavior Driven Development (BDD) that focuses on requirements specified in the form of acceptance criteria. How are Testing and Requirements related? Code TDD Tests focused on what a Class or Method execution results. What result should it return? BDD Tests focused on behavior of classes or components. What behavior should it exhibit? Requirements ATDD Tests focused on requirements of applications. What business functionality should it implement? Internal External A story s behavior is simply its acceptance criteria if the system fulfills all the acceptance criteria, it s behaving correctly; if it doesn t, it isn t. 9

9 WHAT IS BDD? Industry practice in which whole team collaborates on system testing and definition of done Developer focuses on making system test(s) pass Automate tests while production code is being developed Automation design completes before or parallel to development Tests become part of build pipeline and are run throughout the sprint Automated tests represent the true business value and living documentation BDD promotes requirements by example, collaboration, lower cost in resolving defects, and automation in the form of business value. 10

10 AUTOMATION STRATEGY OLD Often a one-tool approach Brittle automated tests Maintenance is high More Automated Tools have not been plentiful Experience with open source low Defects escape easily Developer accountability low Cost of quality is high Less Automated These problems have caused automation to be expensive and ineffective. 11

11 AUTOMATION STRATEGY NEW Use tools such as xunit Find defects quickly Keep technical debt low More Automated Use tools such as Cucumber Best use in regression tests Use plug-ins to extend to other tiers Use tools such as Selenium, Watir Make UI tests maintainable Can increase UI tests with stability Less Automated Unit Testing provides the most effective way in preventing defects increasing and maintaining quality. 12

12 VALUES

13 HOW DOES BDD INCREASE QUALITY? How Does BDD Increase Quality? 1. Process Encourages Collaboration 2. Requirements with Examples 3. Promotes Automation 4. Find Defects Earlier and Often There are many other values to BDD but we ll discuss these four values specifically. 14

14 BDD VALUE #1 PROCESS ENCOURAGES COLLABORATION BDD requires discipline to ensure that the right people work together to create the tests Customers must work with developers to prevent the developers from writing tests that are too low level and tests use customer terminology is used to ensure that what is being tested is important (to the customer) Developers must work with testers testers will be looking for corner cases and good coverage developers can use their expertise to ensure that the test cases are properly decomposed BA, Dev, and QA roles will balance each other Collaboration is primary Consistent domain vocabulary is critical Getting automation right is important 15

15 BDD VALUE #2 REQUIREMENTS WITH EXAMPLES Uses concrete and specific examples written in Gherkin which promotes: Conversation between the business, analyst, developer, and tester (3 Amigos) Prompts early questions around whether the scenarios are accurate Captures the conversation, with the benefit of providing testable functional tests Focuses on thin slices of system behavior that deliver business value which are potentially automatable without translation Develops executable specifications captured in live documentation that can serves as requirements, manual tests, automation scripts 16

16 WHAT IS GHERKIN? Gherkin is a language/syntax that is a Business Readable, Domain Specific Language created specifically for behavior descriptions. It gives you the ability to remove logical details from behavior. Gherkin serves as your project's documentation as well as your project's automated tests. Test template in the form of Given When Then (GWT) Given some initial context (the givens) When an event occurs Then ensure some outcomes Real World Example Given a user navigates to the Kforce website And the user fills in automation engineer for job title or skill And the user fills in for city state zip When the user clicks the search button And the application navigates to the Search Jobs page Then the page displays the save as a job alert button element Then the page displays the reset search button element 17

17 WHAT IS CUCUMBER? Cucumber is an open source software tool written in Ruby and uses a plain text Domain Specific Language (DSL) called Gherkin. Cucumber lines of text are processed by Ruby step definitions which are code blocks that execute the given, when, and then specifications against an application. It runs automated acceptance tests written in a behavior driven development (BDD) / acceptance test driven development (ATDD) style. Cucumber lets software development teams describe how software should behave in plain text. The text is written in a business-readable plain English type language and serves as documentation, automated tests and development-aid - all rolled into one format. Cucumber works with Ruby, Java,.NET, Flex or web applications written in any language. It has been translated to over 40 spoken languages. Aslak Hellesoy created Cucumber to support BDD/ATDD. He states: The idea was to combine automated tests, functional requirements and software documentation into one format that would be understandable by non-technical people as well as testing tools. 18

18 BDD VALUE #3 PROMOTES AUTOMATION Requirements Traceability Execution Reports Selective Testing Cross-Browser Testing Cross-Environment Testing DEV QA STAGE IT ST PT UAT Continuous Integration 19

19 BDD PROMOTES FULL SCOPE AUTOMATION 20

20 BDD VALUE #4 FIND DEFECTS EARLIER + OFTEN Increases testing coverage multiple browsers, database, services Increases testing frequency Increases testing efficiency - eliminate repetitive work, increase reusability Finds defects/bugs as they are introduced Promotes code quality/refactoring (instant feedback) Promotes continuous integration (CI/CD) Decrease test and production defects Decrease operational cost 21

21 AGILE WORKFLOW

22 AGILE WORKFLOW 23

23 QUESTIONS? Josh Eastman Director, Strategic Solutions