Arun Krishnan Automation Manager Maria Afzal Automation Test

  • Slides: 11
Download presentation
Arun Krishnan - Automation Manager Maria Afzal- Automation Test Analyst

Arun Krishnan - Automation Manager Maria Afzal- Automation Test Analyst

Abstract Agile based delivery model is commonly used to be able to keep up

Abstract Agile based delivery model is commonly used to be able to keep up with the pace at which businesses must change in response to emerging trends in market. To complement BDD development process, a need for robust testing solution required to help Developers, QA and Business Analysts to share a common language with focus on business requirements. This presentation outlines how we can achieve faster time to market and quality by implementing BDD based testing solution build on open source automation toolset. 2012 2014 2017 ü Process Challenges ü BDD Implementation ü BDD Process Implementation ü 10% defect leakage in Prod ü 1% defect leakage in Prod ü 0% defect leakage in Prod ü 3 Months Release cycle ü 6 Weeks Release cycle ü 4 Weeks Release cycle ü Partial Agile ü Fully Agile Adoption

Challenges 1 Frequent application deployment changes under stringent timelines 2 High defect leakage to

Challenges 1 Frequent application deployment changes under stringent timelines 2 High defect leakage to UAT/Production 3 Minimal automation coverage 4 Time to market 5 Isolated teams (BA, DEV, QA) Slow VM connectivity due to heavy configuration requirement

 Our Solution Specialized § § § BDD Automation § In Sprint § Data

Our Solution Specialized § § § BDD Automation § In Sprint § Data independent scripts § Service layer Regression Automation Traditional E 2 E Automation Smoke Automation Solutions Advanced § § § Automated Test Result Process generation by Jenkins. Dashboard for Jenkins test execution report. Emailing Test Reports to the stake holders Test Design Automation § Execution of BDD Suite on Code Check in Headless mode Continuous Integration § Integrate Build deployment process

How BDD happens? Initiation Phase Scripting & Implementation Automatically created by BDD Tool User

How BDD happens? Initiation Phase Scripting & Implementation Automatically created by BDD Tool User Story Script Execution. Jenkins Automation Team//DEV Product SME BA – Version. One User stories BDD Acceptance criteria Tester – BDD stories Function Skeleton Created QA/BA/DEV Step Definition generation and Feature Execution (Dry Run) Product SME/BA QA/BA Feature Files Script generation System Under Test Code / Refactor DEV Test Result QA/BA BDD stories are written in parallel to development of Version. One stories Write Scenarios BDD Failed Test Case Passed Test Case

BDD Technical Implementation Features – a text file with a. feature extension, house the

BDD Technical Implementation Features – a text file with a. feature extension, house the tests. Features are made up of Scenarios – scenarios are synonymous with a user story or test case(s) i. e. Behavior The Scenarios are made up of Individual Steps – Steps are the component interactions (or Test Steps) for a given Test Case(s), written in Gherkin language The Step Definitions essentially convert the simple English “Steps” into code that can be executed to perform the step. Support Code will be executed to perform the specific Step in the Feature file. WATi. R & Selenium are all examples of pre built Support Libraries that can be used in conjunction with Cucumber to conduct Automated tests.

 Benefits Delivered VALUE DELIVERED § Accelerated Time to market by reduced testing window

Benefits Delivered VALUE DELIVERED § Accelerated Time to market by reduced testing window § Jenkins eliminates manual dependency § Effort savings enables manual team to focus more on end-end tests § Increased scope of in – sprints tests § Monthly releases with reduced team size § Easy and comprehensive testing of hot fixes BENEFITS DELIVERED § 350 + Business Scenarios automated § 80% Reduction of in-sprint testing time § 0% defect leakage with end to end automation coverage § 300% Increase in test case execution count post BDD implementation § > 30% reduction in overall team size over a year

References https: //en. wikipedia. org/wiki/Behaviordriven_development http: //behaviourdriven. org/ https: //github. com/cucumber/cucumb er/wiki/Gherkin Reference Topic

References https: //en. wikipedia. org/wiki/Behaviordriven_development http: //behaviourdriven. org/ https: //github. com/cucumber/cucumb er/wiki/Gherkin Reference Topic Link

Author Biography Arun Krishnan is an automation manager with more than 11 years of

Author Biography Arun Krishnan is an automation manager with more than 11 years of extensive experience working with automation tools, such as HP UFT, Selenium, Cucumber, Watir, See. Test, Perfecto Mobile, and Mobile Labs. His core expertise is in functional and mobile automation with traditional and nontraditional tools and techniques. Engaged with customer teams to design, implement, and deliver solutions that address specific pain points.

Author Biography Maria Afzal is an automation expert with more than 3 years of

Author Biography Maria Afzal is an automation expert with more than 3 years of experience in automation testing. Maria has extensive experience on key automation tools and platforms and has worked on Hybrid framework for Selenium, Ruby. Maria has expertise in developing automation framework for multiple technologies like Web, and Mobile and has worked on Next. Gen methodologies like BDD, CI and Agile Maria is currently working with a leading US banking client

Thank you!

Thank you!