Continuous Testing Digital Transformation Requires Continuous Testing

Ingo Philipp Businesses must continuously exploit digital technologies to both create new sources of customer value and increase operational agility in service of customers.

Digital Disruption Your Company Identify Your Customer Needs

Build Solution

Receive Money

Plan Code Version Build Provision Test Deploy Monitor

© Melissa Perri 6+ Big Bang Waterfall Requirements Design Implementation Testing Acceptance Deployment Following a Plan Contract Negotiation 4 Copious Documentation Incremental Processes & Tools Rational Unified Process Inception Elaboration Construction Transition Rigid Rules Agile Horizon 2 Flexible Framework Agile Scrum, Kanban Individuals & Interactions Development Operations Working Software Customer Collaboration Responding to Change 1 Continuous DevOps DevOps Digital Singularity Development Response It’s not the strongest that survive, nor the most intelligent, but the one most responsive to change

Charles Darwin Sprint Sprint Start End Time Efficiency Gain 100%

+4x Creation Start testing early, Degree of API shift left test automation Completion +6x Maintenance UI

+20x 0% Execution On average, organizations require access to 33 systems for development or testing. Testing Present Welcome to the tester’s hell 18 Average # of systems with unrestricted access 96 % of testers have restricted test lab access Enterprise system landscapes are alike disease gene networks.

*voke, market snapshot report on service virtualization - 2012 Automation doesn't make testing easy, it makes testing possible

Lesson Learned

Visiting London Testing harder isn’t the answer, testing smarter is!

Lesson Learned

© Wolfgang Platz © BBC Testing is exactly like washing a pig. Because it’s messy. It has no rules. No clear beginning, middle, or end. It’s kind of a pain in the ass, and when you’re done you’re not sure if the pig is really clean or even why you were washing a pig in the first place.

Testing is exactly like washing a pig. Because it’s messy. It has no rules. No clear beginning, middle, or end. It’s kind of a pain in the ass, and when you’re done you’re not sure if the pig is really clean or even why you were washing a pig in the first place.

Problem Testing is exactly like washing a pig. Because That’s what we know it’s messy. It has no rules. No clear beginning, middle, or end. That’s It’s kind of a pain in the ass, what we check and when you’re done you’re not sure if the pig is really clean or even why you were washing a pig in the first place. Knowledge Gap

Problem The purpose of testing is to close the knowledge gap That’s what we know

The goal is information, That’s what we not gratuitous automation check

Testing is and always will be a search for information Knowledge Gap

@iamdevloper Verify through Pay attention to Passing Instructions Deviations Test Case

Create Follow Test Cases Procedure

Examine Factory Requirements Process

Checking « Requires Processing »

Verify through Pay attention to Passing Instructions Deviations Test Case

Create Follow

Process Test Cases Procedure

Examine Factory

Requirements Process Mechanical

Confirmatory Testing « Requires Processing »

» Here You Monitor Known Risks » Here You Analyze Potential Risks Cognitive Cognitive

Verify through Pay attention to Investigate through Pay attention to

Instructions Deviations Experiments Oracles Process

Create Follow Create Follow

Process Test Cases Procedure Test Ideas Clues

Examine Factory Examine Adaptive

Requirements Process Risks Investigation Mechanical

Confirmatory Testing Exploratory Testing « Requires Processing » « Requires Thinking »

Testers Coverage

100% Manual Testing 11 ? Manual Unknown There’s a way to do it

Test Cases Execution better. Find it! Project Charter

0% Automated 4755 10 Testing Manual Weeks Risk Coverage Optimization Test Data Management UI/API Test Automation Continuous Integration & Distributed Execution

Test Cases Testers Coverage Coverage Coverage Execution

Test Case Count 7%

92% 11 37? % 89% 53% 34 Automated Manual BusinessUnknown Risk Business Risk Business Risk Minutes

64% API Tests Smoke Testing Smoke Testing

Test Cases Test Cases Execution Execution Execution Execution

1193 4755 10 5 2.5 488 Manual Manual Weeks Weeks Weeks Hours

75% Redundancy 50% Effort Test Data MultipleSingle Agent Agents Risk Coverage Optimization Test Data Management UI/API Test Automation Continuous Integration & Distributed Execution

Test Cases Production Defects Coverage Coverage Execution

Test Case Count 7%

92% 89% 53% 34 Automated Business Risk Business Risk Minutes

64% API Tests Smoke Testing Smoke Testing 72% Test Cases Critical Defect Reduction Execution Execution Execution

1193 5 2.5 8 Manual Weeks Weeks Hours

Test Case Design & Exploratory Testing Multiple Agents The future doesn’t just happen, it gets happened, so make it happen

Conclusion