Auto Desk - Testing Ppt _11th June

8/4/2019 Auto Desk - Testing Ppt _11th June

1/14

Independent Testing Capability


3/14


Project Nature Services Portfolio Business ValueNew technology implementation, upgrading corevendor packages to current release

System Integration Testing Deployment Assurance, Defect densityreductionDelivering business driven enhancements & new

systemsRegression Testing Reassurance with limited time &

budget, Improved Test coverageCapacity planning, infrastructure

Performance Testing System availability, improvedperformance

Agile development, multiple builds Continuous Integration Testing (CIT),Build Testing

Testing along with Development Test early, Test often

Legislation-Corporate-Regulatory Compliance

Functional Domain Testing

(Telecom, Insurance, Banking, Finance & Retail)

Guarantee stability & reliance of core

systems, fully documented in auditready formatRe-engineering existing systems atTest Database Migration Testing Data integrity & performance

Multi-linqual, Regional,

Multi-country, Global deploymentL10N/I18N Testing Country specific readiness

Hardware, devices, mobile

Embedded Testing Interface AssuranceERP Implementation roll-outs, upgrades Test Center for Enterprise Applications Certified Business ProcessSecurity Audits Security Testing Threat protection &

secured environmentData Protection & Cleaning Test Data Management Reusability & Protection

Test Process|Functional|Non Functional|Business Process|Infrastructure|Platform|Deployment|Security|Compliances |Satyam Test Business Consulting@QEdge

Solutions & Service Business Value


4/14


Managed Services Model Components

Model:t -QA strategy as a whole and creates higher value for business

he execution cycle time, standardize the processes and ensures consistent customer experience

ngagement success and best practices cascaded across the Managed Service

obilization, higher offshore % and improved governance, scoping & reviews


5/14


Satyams Proposed Solution

anagementProcessesOperations

ManagementWorkflow

ManagementSLA

Management

&Standard CustomizedReporting

RiskManagement

estProcessesRequirements

anagement

All Types oftesting

in life Cycle

&Test Data AssetManagement

&

Data PrivacySecurity

DefectManagement

ustomerInterface&Application Owners Business

Teams

Leadership

Technical( &Teams QA Test

)Manager

Infrastructure( - / - / -Communication Network On Site Off Shore Off)Site

(

&Test Environment Hardware)Software

Facility

Client SatyamManaged Test Center (MTC)


6/14


Service Coverage Using Managed TestCenter


7/14Copyright 2007 Satyam Computer Services Ltd. All rights reserved.

Verification Strategies

Verification Strategy Explanation Deliverable

Requirements Review The study and discussions of the computersystem requirements to ensure they meet stated

user needs and are feasible.

Reviewed statement of requirements.

Design Review The study and discussion of the computersystem design to ensure it will support thesystem requirements.

System Design Document, HardwareDesign Document.

Code Walkthrough Informal analysis of the program source code tofind defects and verify coding techniques.

Software ready for initial testing by thedeveloper.

Code Inspection Formal analysis of the program source code to

find defects as defined by meeting systemdesign specification.

Software ready for testing by the testing

team.

Unit Testing Testing of single program, modules, or unit ofcode.

Software unit ready for testing with othersystem component.

Integration Testing Testing of related programs, modules, or units ofcode.

Portions of the system ready for testingwith other portions of the system.

System Testing Testing of entire computer system. This kind oftesting can include functional and structuraltesting.

Tested computer system, based on whatwas specified to be developed.

Performance Testing Testing of the application for the performance atstipulated times and stipulated number of users.

Stable application performance.

User Acceptance Testing (UAT) Testing of computer system to make sure it willwork in the system regardless of what the

system requirements indicate.

Tested and accepted system based onthe user needs.



Test Center

Requirement

Analysis&

Test Plan

BuildAccepta

nceTesting

Functional

Testing

End toEnd

Testing Compatibility

testing

AutomationRegressi

onTesting

Performance

Testing

Regression

Testing

Execution of Testcases andlog defects

DefectManagementQuarterly reviewprocess andSuggestimprovements

Stage I Stage II Stage III Stage IV

Regression testingAutomated scripts

Performance testscriptsClosureof defectsMetricsanddashboards

Planning ExecutionSpecialized

TestingRegression

Prepare automationstrategy

Identify tool for

automationAutomation, Dry runEnhance the scripts

Test Planpreparation

Test Plan

ReviewTest CaseDesign

Test Datapreparation

Release Planningand Estimates

TestingTools

Testing

Activities

TestingStages



Satyam QEdge Test Automation Approach & Methodology



Sample Metrics/Dashboard



Reuters Siebel Case Study

EnvironmentvvSiebel eBusiness 7.5 Order Management CRM Portal , BizTalk

UAN

vDuration: Engagement lasted for 9 months TestingvTotal test scenarios use cases 179,Test cases1500+

vComplexity- Total 5 solution stream under test v12 cycles in 3 months System Test - 4 environmentsvTotal FTEs 15:28 [Onsite: Offshore]vOnsite offshore testing activity- 35:65vTools: Manual / Segue Silk / Mercury Interactive/ MS

ChallengesvTotal Defects detected 4369 in 4 months Fast

track Testing- 31% Critical / 42 % Major Severity-51 % High Priority 77 % Defect closed, >1.2 %defect rejected by Development team- 2 % defectreopened

vMulti vendor Multi Time Zone- Multi GeographiesTest & Defect Management

vStringent SLA driven test Dashboards tracking fordefect closure cycle

vTest Environment uptime 98 %vSevere Defect closure in 2 hrsv95 % Test case Pass rate

SolutionvIndependent Evaluation- Onsite Offshore setup- 24 X 7vParallel & Fast track & Multiple Dry Run TestingvTest Process improvement Metrics AnalysisvEarly Integration Testing for Environment proving

vEarly involvement in all SDLC phases thru V ModelvRisk Based Testing

enefits to the ClientvResource: Minimize test resource costs to

55% by transitioning to offshorevDelivery Model: Time zone leverage

increased productivity by 200% 16 X 7

testing in shiftsvOffshore transition cost benefited in 2

months 40 % cost reductionvPerformance Test: Performance tuning

recommendation brought down h/winvestment by 30% in right hardwarecapacity.

vCreated reusable test assets-35 % testscripts reused- Cycle time reduction to 2

days form 6 days in test design work.



SAP Test Automation - Sony SAP Case Studies

ustomer Profilev Sony has one of the largest SAP systems in the world which

is capable of processing transactions worth more than 100million. Sony uses the following SAP modules: Sales andDistribution, Materials Management, Production Planning,Financial Accounting, Controlling, Asset Management, WorkflowManagement, Human Resources.vv The project consists of developing regression scripts forcomplete Sales and Distribution module and executing them asa part of monthly regression cycle.

Customer Requirements

v Automation of Standard SAP Business flows usingBusiness Process Testing Methodology

v Creation of Manual Business Process testsv Execution of Automated and Manual BPTs eachmonth and updating managers with the daily progressv Building tool in VB.NET for test analysis andrequirements reporting.v Quality Center Support

Solution

v Provided Automated and Manual BPTs for the given SAP

flowsv Provided Quality Center supportv Built the tool required for reporting purposesv Executed the BPTs on a monthly basis as a part ofregression cycle

Benefits to the Client

v Automated solution of the existing Standard flows

v Manual test cases complying with the Business ProcessTesting standardsv Handling Quality Center support responsibilityv Better result reporting with the help of tool


14/14Copyright 2007 Satyam Computer Services Ltd All rights reserved

Enterprise Data warehouse Transformation Case StudiesEnvironmentvTechnical Environment: Data Stage Enterprise Edition

v7.5.2, SUSE Linux 9, Perl 5.8.3(Perl-DBI 1.50, DBD-ODBC-1.13, UNIX ODBC-2.2.8, Teradata Database V2R6.2, Shell

Scripts BashvMercury Quality Center 9.0

v Duration: 1.5 YearsvComplexity- Analyzing Business scenarios and

working in cLDM( Communications Logical DataModel)

vTotal FTEs 10:40 [Onsite: Offshore]vOnsite offshore testing activity- 30:70vTools: Data Stage ,Mercury Quality Center,

Teradata.

Challengesv A total of 1110 defect was detected in 90days

of which 12.7% critical ,44% High,40.7% lowseverity .Of all the defects 96.8% defectsclosed 2% rejected and 1.2% deferred to

TR1.1v One environment to be accessed by Multipleusers (Ecap, Data-Out , Data-In)

v Multi Vendor Multi Time Zone Multigeographies Test & Defect Management.

v Testing of jobs which had undergone 85%changes according to the CRs in TR 1.1achieved successfully in a very short period.

v A total of 282 defects were detected in TR1.1in 40 days out of which 5% defects were

critical, 44% high and 3% defects rejected

SolutionvSystem Testing of Field Validation job , validating the source

system files.vSystem Testing of PCS, Validating the Files using

PCS(Process Control System).vSIT Shakeout (Setting up the Environment for Offshore

Testing).vSIT Support for 24 X 7 Offshore.vProgression and Regression Testing.v24 X 7 UAT support from Offshore.Testing of the Business

ScenariosvTracking all the defects and status by maintaining defect

tracking using Quality Center 9.0.vMultiple Cycles of ETL System testing performed in TR 1.1vReferential Integrity testing (RI).Data Quality Check for the

source files.

enefits to the Clientv Minimize test resource costs to 60% by

transitioning to offshore.vDetecting the Defects in initial stages by

following the V Model approach.

vDefect Management Process made easy withQC.

v 24 X 7 supporthelped in delivering thedeliverables in the Stipulated time and helped inresource management by reducing the numberof resources required to 50%.

v By reusing PCS Scriptsfor validating the CC&Bfiles the re-usability was achieved

v 60% of the Test cases were re-usable, hence

reduced the rework on the test cases from 4days to 2 days.

Auto Desk - Testing Ppt _11th June

Documents

Transcript of Auto Desk - Testing Ppt _11th June