When executing test automation at scale and continuously the value tends to decline over time, the team should follow recommended practices to keep their tests with high value.
Getting the value from your test automation is fundamental for fast feedback, risk reduction and return on investment from your testing activities. Once developing the test scenarios, teams cannot stop monitoring and ensuring that their tests continuously bring value, are not flaky, and can support the latest functionalities in your web and mobile apps. Teams often “forget” about their tests once they have been developed and integrated into the CI pipeline regardless of the value they bring.
This webinar will cover:
-How to make smart decisions regarding which test scenarios to automate?
-What are the criteria for a test to get included in the CI and continuous testing pipeline?
-How to continuously maintain the tests and optimize your suite so it continues to bring value?
-See a live demo of smart reporting and analytics that can serve as a monitoring and test maintenance tool.
Artificial intelligence in the post-deep learning era
Keeping Your Continuous Test Automation Suites Continuously Valuable in DevOps
1. 1 | Keeping Your Continuous Testing Suites Continuously Valuable in DevOps perfecto.io
Keeping Your Continuous Test Automation Suites
Continuously Valuable in DevOps
2. 2 | Keeping Your Continuous Testing Suites Continuously Valuable in DevOps perfecto.io
• Chief Evangelist and author at Perfecto
• Blogger and speaker
• 19+ years in development & testing
• Author of
“The Digital Quality Handbook”
and “Continuous Testing for
DevOps Professionals”
• Twitter: @ek121268
• Blog: continuoustesting.blog
• Website: perfecto.io
Today’s Speaker:
Eran Kinsbruner
14. perfecto.io
Optimize Based on Data —
Recurring Patterns for Inefficiencies
Licenses In-use Disconnected
Orchestration issues
Network Availability Data
Backend issues
Objects Coding Time Other
Scripts & FW issues
• 10% of devices causing 80% of lab issues
Networking Stability Config Lock
Lab issues
Backend
30%
Lab
15%Orchestration
15%
Scripts & FW
40%
What’s wrong
with my scripts?
What’s wrong
with my
executions?
What’s wrong
with my lab?
What’s wrong with
my backend?
15. perfecto.io
Noise Reduction – Continuous Testing Enabler
“About 10–20 defects per 1000 lines of code during in-
house testing, and 0.5 defect per KLOC in production”
(Sogeti Labs)
(~1 real Defect per developer per day)
Regression suite of 10,000 tests == ~20% failures
Out of 2000 failures, only 20 are actual bugs,
1980 are false negative, noise
Reporting noise is a risky bad practice
•Reporting crashes, errors in functionality, performance issues – dev friendly
•Lab Issue, object not found, popups, alerts, orchestration etc. – Should never be
taken to dev
22. Tool/Framework
Selection Criteria:
Technical Fit & Skills
SDLC
process fit
(integration,
plug-ins, skills,
etc.)
Community
size, support,
and docs
Feedback loop
and reporting
Automation
coverage
Cloud and
automation at
scale
Automation
robustness and
maintainability
26. High-Level Comparison Between Tools, Personas and Practices
Test Framework Supported
Dev
Languages
Supported
Platforms
Supported
Test
Frameworks
Setup and
Execution
Integrations Breadth of
Testing
Options
Maturity,
Documentation,
Support
Required Skillset Cloud and Execution at
Scale
Selenium/Appium
WebDriver
Java, C#,
Java Script,
Python,
Ruby,
Objective-
C
Chrome,
Safari,
Firefox, Edge,
IE/iOS/Andro
id
Mocha JS, Jest,
other super
set on top of
Selenium
(Protractor,
WebDriverIO,
etc.)
Download
relevant
driver, set up a
grid, network
and location
impacts
execution
speed
Plenty of
integrations
(CI, CD,
reporting,
visual testing,
cloud vendors)
End-to-
end,
security,
unit,
Robust community,
multiple bindings, best
practices
Coding skills required
(SDET Oriented)
Perfecto fully supports
Selenium and its
WebDriver
configurations. Local
execution requires
setting up a Selenium
grid
XCUITest/Espresso
/Headless
Objective
C/Java/Java
Script
Chrome,
Electron
NA Embedded
into IDEs,
headless
bundles a
browser in the
FW
CI/CD UI/Unit Good documentation
and code samples
Dev Oriented Built-in Chrome/Firefox
browsers in headless,
Perfecto Cloud supports
scaling
Espresso/XCUITest
Codeless Irrelevant,
based on
record and
playback
All Proprietary UI
with
underlying
Selenium
WebDriver
APIs
Mostly
SaaS/browser
plugin
installation
Limited Functional
/UI
Growing, limited No coding skills
required (Business
Tester Oriented)
Perfecto supports
codeless in the cloud
BDD Java, Ruby,
JS, Kotlin
All Junit,
Selenium,
Appium
Open source,
Maven/Gradle
/TestNG
Plenty + APIs
(e.g. Rest
Assured)
Functional Robust community,
docs, adoption
Step-definition
development in code is
required/scenarios are
no-code (Mix of
Business Tester and
SDETs)
Perfecto Quantum is a
web/mobile BDD
framework