The document discusses the benefits of continuous testing including reduced time to market, increased architecture complexity handling, smaller and more efficient teams, automation throughout the lifecycle, reduced costs, early failure detection, and quicker feedback. It also identifies challenges around people, processes, tools, and technology integration. The current approach is shown as a continuous testing pipeline with various stages like unit testing, deployment environments, and monitoring. The near future approach envisions optimizing value streams, continuous delivery pipelines, DevSecOps, functional programming, cloud/microservices, and an open framework to support innovations.

1. Continues Testing =>
Digital Testing
ANAND DESHPANDE

2. Why Continuous Testing
• ReduceTime to Market with
quality
• Increase Complexity of
Architecture
• SmallerTeam , More O/P &
efficiency
• Automation in every stage of
life cycle
• Reduce cost ( takes care of cost
of quality )
• Failing Fast / Early failures
improves quality
• Quicker roll-back
• Continues Learning and
Experimenting
• Quality Built-in
• Quicker feedback
• Faster response for Production
issues
• Monitoring and Control for
good support
• Safe Environment in
Production
• Build confidence between
Teams ( Dev,QA,Ops)
• Reduce dependencies between
Dev , QA and OpsTeam

3. Current Implementation Challenges / Problem statements / Issues
People
More Automation
@ Dev and Ops
Less Automation
@ QA
Lack of
Leaderships
Trained Resources
are bottlenecks
Process
•Many manual
overheads
•Process based on
tools and
technology
•High elapsed time
•Governance
Model
Tools
ManyTools for
same purpose
Manual
configuration and
Dependencies
Continuous
Monitoring
Tool chain
Integration
Technology
New Innovations /
Technologies
Integration with
old systems or
architectures
Documentation
Quality ∞
Time/Speed

4. Plan Code Build
Deploy on
Env. A
Integrate
Testing on
Env. A
Testing on
Env. B
Testing on
Env. C
Testing on
Pre-prod
Deploy on
Env. C
Release
Deploy on
Pre-prod
Unit Tests
Static Code
Reviews /
Analysis
Object
Oriented
Programing /
/ API
Components
Test
API /
Module
Tests
Regression
Tests
Deploy on
Env. B
Best
Practices /
Templates
used for
Ant/Maven/
YAML/Shell
scripting
CP CP CP CP CP CP CP CP
Security /
Performance
Tests
System
Tests
User
Acceptance
Tests
Monitor
Push-button
Release
Manual
Release
CP Check Points
Continues Testing for Continues Delivery Pipeline
Continues Deployment
Continues Integration
CP CP
Behaviour-
Driven
Development
(BDD) Tests
TDD
Tests
Best
Practices /
Templates
used for
Ant/Maven/
YAML/Shell
scripting
Best
Practices /
Templates
used for
Ant/Maven/
YAML/Shell
scripting
Best
Practices /
Templates
used for
Ant/Maven/
YAML/Shell
scripting
Key Outcomes /
Best Practices
Feedback /
Shift Left
CurrentApproach forContinuesTesting
Automated
Testing Suite
No. of test cases in automated testing suite – ContinuesTesting Pipeline

5. Near FutureApproach forContinuesTesting
Key Outcomes /
Best Practices
Agile Cloud MobileIOTDevOps ML/DL
Digital
Testing
Agile –DevOps
Model
Enterprise
Modern
Digital
• OptimizedValue Streams
• Continues Delivery Pipeline
• DevSecOps and DevQAOps
• Functional Programming
• Continues Delivery Pipeline
• Cloud / Microservices
• Serverless architectures
• Open ended Framework for add/remove
Components
• Single Code Multi Hardware
• Digital Eco System
• Innovations
• AutomatedConcept to Cash flow

6. ThankYou
•Please be reachable on danandguru@gmail.com or
www.linkedin.com/in/danandguru
for any comments / suggestions / queries