Selenium DeTox for Achieving the Right Testing Pyramid
33
Manual Checking End- to End Selenium Tests 70% Integration Tests 20% Unit Tests 10% Unit Tests 70% Domain Logic Acceptance Tests 10% Integration Tests 9% Workflow API Tests 6% End to End Flow Tests 4% UI 1% Naresh Jain @nashjain Selenium Detox for Achieving the Right Test Pyramid
-
Upload
naresh-jain -
Category
Technology
-
view
520 -
download
0
description
Our project was a classic example of Selenium gone wild! As our team embraced the test automation journey, we went crazy and implemented tons of Selenium tests, one for every permutation possible. Soon we realized our feedback cycles were delayed. Our builds were taking hours instead of minutes. And we had a set of complex, fragile tests, which resulted in a lot of false-negative scenarios and finger pointing. At this point, our team had realized that this is not the path forward. We decided to seriously look at our Selenium tests. We pretty much moved 80% of our Se tests to lower-layers (non-GUI based) tests. And now we have the right testing pyramid on our project. In this presentation, Naresh Jain explains IDeaS' journey (strategy, techniques, tools, mindset-change and approaches we took) through this transition.
Transcript of Selenium DeTox for Achieving the Right Testing Pyramid
Manual Checking
End- to End Selenium Tests 70%
Integration Tests20%
Unit Tests10% Unit Tests 70%
Domain Logic Acceptance Tests 10%
Integration Tests 9%
Workflow API Tests 6%
End to End Flow Tests
4%
UI 1%
Naresh Jain @nashjain
Selenium Detox for Achieving the Right Test Pyramid
Selenium Detox for Achieving the Right Test Pyramid
Naresh Jain@nashjain
Achieving the Right Test Pyramid
Aditya Saigaonkar
Kirtesh Wani
Background
IDeaS is capable of applying 25 years of experience,
expertise and client dedication toward an expanding suite of automated revenue management solutions.
Background
Background
Background - 2011
5%
95% No Automation
Automation Coverage
Background
1 Months2 Months
0 0.5 1 1.5 2 2.5 3 3.5
Months
Typical Release Cycle
Development Regression
Background
Critical Issues reported from Production
0
2
4
6
8
10
12
Critical Data Issues Cosmetic Localization
Issues
Background
After Automation Introduced - 2013
Selenium Tests 45%
Unit & Integration Tests 20%
No Automation 35%
Automation Coverage
After Automation Introduced
2.25 Months 3 Weeks
0 0.5 1 1.5 2 2.5 3 3.5
Months
Typical Release Cycle
Development Regression
Critical Issues reported from Production
0
2
4
6
8
10
12
Critical Data Issues Cosmetic Localization
Duration…
0 0.5 1 1.5 2 2.5
Years
Duration of Implementation
2 Years
Demo
• Selenium WebDriver Demo
State of the Product
Tightly coupled with UI
Browser Dependent Data tests
False fails
Difficult to pinpoint real culprit
Difficult to maintain and time consuming as test are fragile
Lagging with current release development
Image Courtesy: Alex Yakyma
Analysis of Bugs Report
10%
90% Data Failures
Bug Report Analysis
UI Navigation Failures
State of the Product
Manual Checking
End- to End Selenium Tests 70%
Integration Tests20%
Unit Tests10%
Manual Checking
End- to End Selenium Tests 70%
Integration Tests20%
Unit Tests10% Unit Tests 70%
Domain Logic Acceptance Tests 10%
Integration Tests 9%
Workflow API Tests 6%
End to End Flow Tests
4%
UI 1%
Typical test strategies lead to an inverted testing pyramid
This is the need of the hour….Courtesy: Naresh Jain @AgileFAQs.com
The Test Pyramid
Our transition story…
• We decided to "Test things right , at right place on right time" which would result in "right test pyramid“
Unit Tests 70%
Domain Logic Acceptance Tests 10%
Integration Tests 9%
Workflow API Tests 6%
End to End Flow Tests
4%
UI 1%
Our transition story…
Application UI
Service Layer
DAO Layer
Automated UI Tests
Tightly Coupled
Fragile
Lag with current development
Automate One Level Below UI
UI Independent
Robust & Stable
With current dev cycle
Fast Execution
Introduced BDD with Cucumber
Dev & QA Pairing
Developer QA
Quick Demo
Current Status
Selenium Tests 10%
Workflow Tests: 40%
No Automation 20%
Unit & Integration Tests 30%
Test Automation Status
After Right Testing Pyramid
1 Week2.75 Months
0 0.05 0.1 0.15 0.2 0.25 0.3
0 0.5 1 1.5 2 2.5 3 3.5
Months
Typical Release Cycle
Regression Time Development
Critical Issues reported from Production
0
2
4
6
8
10
12
Critical Data Issues Cosmetic Localization
Duration…
0 0.5 1 1.5 2 2.5 3 3.5
Months
Duration of Implementation
3 Months
Pain points
• Learning curve for the team
• Difficult to implement in case where no API is exposed or tight coupling with UI
• Heavy dependency on pre-populated database
Looking ahead
• Expose RESTful APIs for all upcoming features
• Move BDD specs to lower layers
• Moving away from baseline database
Courtesy: http://3.bp.blogspot.com/
© Copyright Integrated Decisions and Systems, Inc. (IDeaS – A SAS COMPANY)
Visit IDeaS online at www.ideas.com
Questions?
Naresh Jain @nashjain
![[320] Web 3: Selenium · for Selenium Java module for Selenium Ruby module for Selenium JavaScript mod for Selenium Chrome Driver Firefox Driver Edge Driver. Examples. Starter Code](https://static.fdocuments.net/doc/165x107/5eadce82cc4f0d7405687f01/320-web-3-selenium-for-selenium-java-module-for-selenium-ruby-module-for-selenium.jpg)
