BDD along with Continuous Integration
Download as PPT, PDF0 likes3,672 views
The document discusses behavior driven development (BDD) using the Cucumber framework along with continuous integration using Jenkins. It introduces BDD and how Cucumber allows writing acceptance tests in a format like plain English that can be understood by business analysts, developers and testers. Cucumber uses the Gherkin language to write feature descriptions that serve as both documentation and automated tests. The document then discusses how Jenkins enables continuous integration by regularly scheduling and executing tests to accelerate code commits and testing. It provides the benefits of BDD in increasing automation and communication between teams as well as reducing defects. Finally, it outlines the pros and cons of taking a BDD approach.
BDD along with Continuous Integration
- 1. Archana Krushnan, Test Analyst Nihilent Technologies, Pune 1 Behaviour Driven Development along with Continuous Integration
- 2. 2 Introduction BDD framework using Cucumber Continuous integration with Jenkins Need for BDD and its practical usage Approach to building BDD framework with cucumber and Continuous integration with Jenkins Pros and Cons of BDD Conclusion
- 3. 3 Introduction to Behavior driven Development Collaborates with both Testers and Business objectives Bridge between business (User Stories) and automated tests Useful in documentation of the current understanding of an existing system Refined focus on the user's perspective Makes tests easier to read and execute
- 4. 4
- 5. 5 Behavior Driven development with Cucumber Framework for writing and executing high level descriptions of your software's functionality. Used to write acceptance tests for web application Allows automation of functional validation using Gherkin language in a understandable format (like plain English) to Business Analysts, Developers, Testers, etc. Gherkin extremely user-friendly like any of the human languages feature descriptions can be written and/or understood by non- technical people involved in the project. Gherkin serves two purposes — documentation and automated tests.
- 6. 6 Continuous integration with Jenkins Practice of accelerating commits and testing of code by software developers Regular schedulers which can run and execute the tests at regular intervals. New enhancements and bug fixes can be easily tested and rolled out to production in an accelerated way. Delay between bug reporting and fix to be rolled out is made faster. Increases the ability of automation and makes testing just a click away
- 7. 7 Need for BDD and its practical usage Increases the ability of automation and makes testing just a click away Clears the specification in simple word Communication problems and ambiguity is reduced. Encourages better software quality Reduces defect rejection rate
- 8. 8 Approach to BDD framework with cucumber and Jenkins Step 1: User Story / Requirement Elicitation & Elaboration with Customer(s) or Business Owner – Feature file output Step 2: User Story (Feature file) Elaboration & Validation with QA Step 3: Feature & Feature File Implementation by Developers/Testers Step 4: Testers Test Functionality Step 5: Acceptance by Business Owner Step 6: Repeat (In Event of Requirement Changes)
- 9. 9 Pros and Cons of BDD Pros • It uses user friendly language and easy to run in case of small enhancements and changes. • It can be easily run by BA’s , Developers, Testers. • Focus is on user scenarios, Complexity is hidden and adds value to the project. Cons • It cannot be considered as replacement of unit tests and testing process. • In case of failure, debugging is a bit complex
- 10. 10 References & Appendix 1.Beck, K. (2003). Test Driven Development by Example. Addison Wesley - Vaseem. 2.North, D. (2006, March 1). Introducing BDD. Retrieved April 27, 2015, from http://dannorth.net/introducing-bdd/ 3.https://cucumber.io/ 4.https://jenkins-ci.org/
- 11. 11 Author Biography Professional History and Credentials: Archana Krushnan is currently working as Test Analyst at Nihilent Technologies Pvt Ltd. She has been in the field of Software Testing for 5 years and worked on several domains such as Telecom, Ecommerce and Healthcare. Her interests include exploring new things in testing and sharing on her blog. She has previous experiences of working with companies like Reliance Communications Ltd and Fab.com. She has good knowledge in Selenium, Jmeter and Soap UI. She is ISTQB Foundation Level Certified.
- 12. 12 Thank You!!!