Testing as a Service

Test Resources OverviewLeads20%

Seniors26%

Middle48%

Juniors6%

Manual59%

TA30%

Management

11%

Slovakia, Ukraine

Why TaaS (Testing as a Service)

Why• Testing – solid popular profession in post-soviet

countries

• Testing – is a must in all our projects

• Testers – integral part of the team

• Testing – integral part of QA

Differentiators• We embed into customer process and environment

• We know heavy methods, but you’ll get your own, working for you

• Management overhead is on our side

Testing addressing business challenges

•Big regression scope

•Testing as a separate phase slows the process

•Need to handle testing of features flow

Speed-to-market

•Extra-time and cost for high quality

•Unclear customer expectations

•Lack of structured repetitive processPoor Quality

• No dedicated / specialized resources

• Need to know new technologies and tools

• Business Users do testing

• Dependence on particular resources

Capacity & Competence

• Expensive resources are involved into testing

• Cost of knowledge transfer

• Cost of continuous manual regression testing

Cost

• Cross-dependencies

• Vendors with different delivery models

• Lack of integration testing

• Asynchronous releases

Integration QA & Testers as connecting point Well-defined test scope Automated testing

Professional resources Well-defined test scope, test cases,

scenarios. Knowledge sharing Effective resources utilization

Effective test process

Well-defined test scope

Automated regression

Dedicated testers, continuous testing

Well-defined scenarios, approved by customer/users

Continuous professional testing Coverage control

Professional (and cheaper) resources Automated regression testing Client can focus on business

Typical Cases

More Hands

Expanding the team

Flexible workload

Dedicated Resources

Fill the Gaps

Test Automation

Test Design

Specific kind of testing

Test Process and Team

Test Process establishment and management

Captive Test Team

Costs Optimization

Rates

Uneven Utilization

Test Automation

Testing activities within sprint/iteration

Results EvaluationTestingTest DesignTest PlanningTest Approach

• Define test scope for sprint

• Estimate efforts

• Execute tests• Verify fixes • Bug Tracking• Acceptance testing

• Test Summary Report

• Go/Not Go

• Create new tests• Update existent tests• Automate tests• Update automated

suites• Prepare test data

• Analyze requirements• Define acceptance

criteria for sprint

ExpertiseTest Automation tools

• Selenium RC, IDE, WebDriver

• Ranorex

• Cucumber, SpecFlow

• TestComplete

• HP QuickTest Professional

• Visual Studio Coded UI

• Jmeter

• Junit

• SoapUI

• GreenHat

Programming languages

• Java

• JavaScript

• VBScript

• C#

• Python

• Groovy

Continuous Integration, Build and Testing Execution automation

• Apache Maven

• Apache Ant

• Atlassian Bamboo

• Jenkins

• Hudson

• Cruise Control

Test Planning

• Jira

• WiKi

• Test Link

• HP Quality Center

• Test Track

• MS Office

Test Design

• Jira

• TFS

• Test Link

• HP Quality Center

• TestTrack

• MS Office

Issue Tracking

• Jira

• TFS

• Test Track

• Bugzilla

• Muntis

• Front-end

• Full value-chain testing

• Integration Services• BI/DWH

• Performance

• Security

• Mobile

Scope

Typical project roadmap

Initiation2 weeks

•Scope

•Tool

•Approach

•Estimates

•Proposal for project

POC2 months

•Knowledge Transfer

•Test Strategy

•Test Scope and Design

•Test Automation Framework

•POC scenarios automated

•Evaluate

•Plan Phase 2

Major Scope2 months

•Test Scope controlled

•X scenarios automated

•Testing > Results

•TA Framework enhanced

•Process adjustments

Scale2 months

•Adjustments

• Intense

•Maintain

•Enhance

Proposal

Contract

Kick-Off

Team Allocation4-6 weeks

Scope

Schedule

Management Plan

POC

TestsScripts

Steering Committees

Meetings

Reports

Coverage

Workshop

Feasibility Study

Security Testing

Infrastructure security

Application security

Organization security

• External Penetration Testing• Internal Penetration Testing • Wireless Assessments• Firewall Assessments• VPN Assessments• Social Engineering• Host On-console Audit

• Web Application Testing • Mobile Application Testing • Desktop Application Testing• Source Code Review• Application Threat Modelling

• Security Training• Security Policies Review• Incident Response and

Forensics Investigation• Risk Management• Business Continuity

Performance Testing

Reports, Analysis &Recommendations

Performance Test Approach and Plan

Test Design and Test Automation

Server Monitoring and Test Execution Tools Setup

Test Execution and Monitoring:• Database Server• Application Server• Client

Deteo provides the full range of Performance Testing types/activities for different kinds of applications and customer needs.

Mobile Testing

Typical Initiation Roadmap

Case Selection

5 hours

• Scope

• Tools

• Technologies

• Approach

• Estimates

• Proposal

Feasibility Study

5 days

• Finalize scope, roadmap

• Finalize organization

• Select the tool (test automation)

• Demo (deliverables)

• Data security checklist

• Proposal

POC

2 months

• On-site knowledge transfer:

• Scope finalization

• Required knowledge transfer

• Management Plan

• Become the team

• Sprint together, delivery

• Delivery of POC scope

Strategy

Case

Scope and Timeline

Technical Solution

Estimates

Proposal

Value

Proposal Contract Kick-Off Staffing

Knowledge Transfer2 weeks

Ready to initiate a first talk?Please connect with us

in one of the following ways:

USA: +1 (855) 853-8084 EU: +45 65 74 83 72contact@deteo.info