Post on 05-Apr-2018
7/31/2019 Clouding Testing Approach2 0
1/18
Confidential
Testing Proposal
7/31/2019 Clouding Testing Approach2 0
2/18
Agenda
Objective and Scope2 Approach of Testing
Test Process3
4 Testing Types
1
5 Resourcing Needs/Team Structure
6 Assumptions
7 Case Study
7/31/2019 Clouding Testing Approach2 0
3/18
Objective & Scope
To test private cloud infrastructure
The cloud environment will have Portal Layer Demand & Delivery layer Infrastructure Layer
The scope of testing will be to conduct the unit, integration
and e2e testing.
The testing team will plan the strategy and test casesafter discussing with the HP SMEs for the respective streams
(Portal, ..)
The testing team will conduct the execution basedon the test agreed and reviewed test cases.
7/31/2019 Clouding Testing Approach2 0
4/18
The Strategy determines the approach we will be routing to achieve the statedtest Objective.
o Unit/Component Testing
Each of the component from the portal/Portal Layer, Demand & Deliverylayer and Infrastructure Layer
o Component Integration Testing
Component integration testing will be conducted to ensure that each ofthe components can work together.
o E2E integration Testing
To test the application from the end user perspective.
Approach of Testing
7/31/2019 Clouding Testing Approach2 0
5/18
Project Kick-off
Detailed Requirements Gathering Creation of Test Strategy/Planning
Review Approval of Strategy/Planning
Creation of Test Cases Based on the Technical Specs
Review and approval test cases
Execute test cases
Unit level execution
End to end test execution
Performance testing Scripting
Execution
Reporting
Approach
7/31/2019 Clouding Testing Approach2 0
6/18
Security Penetration Testing
Execution of Scenarios based on the security requirements Reporting
Creation of Automation scripts for the subsequent execution
Identify the test cases that will be re-used across the medium and high security phase
Create automated scripts
Execute and test automated scripts
Completion of testing & sign-off
Approach
7/31/2019 Clouding Testing Approach2 0
7/18
The Testing Process walks through the unit level activities during TestingPhases.
i) Develop High level Scenarios from RFP
ii) Develop Test Plan followed by Test Cases from Technical Specification andUse case/Functional Specification
iii) Environment Readiness before Test Execution Scheduled Date
iv) Start Test Execution
v) Monitor Test Result and implement Fix
vi) Testing Sign off based on Test Exit Criteria
Test Process
7/31/2019 Clouding Testing Approach2 0
8/18
The Testing Techniques will apply the approach identified into action as follows:
i) Functional Testing
Unit/Component Testing
Integration Testing
E2E Integration Testing
Functional Testing
Regression Testing
ii) Non-Functional Testing
Performance Testing
Automation Testing
Security / Penetration Testing
Testing Types
7/31/2019 Clouding Testing Approach2 0
9/18
Note: The Team Size may vary depending on the volume of Testing Needs. Which will be
derived based on the number of Test Cases to be executed.
Resourcing Needs/Team Structure
Fixed price, deliverables basedproject engagement
Full project management &responsibility
Provides full project teamresources
Provides test automationmaintenance after projectcompletion
Knowledge transfer and training.
Qassure Responsibilities
Test Manager
Test Lead Test Analyst
Infra Test Lead
7/31/2019 Clouding Testing Approach2 0
10/18
Strategy is based on High levelunderstanding of Project Assignment duringinitial Feasibility Study which is subjected tochange when resources will gain detailedcommand over the Infrastructure and echosystem.
Scope of project might change as thevendor doesnt have clarity on Infrastructureneeds and demands.
Size of team might change based on thevolume of Test on need basis.
Assumptions
7/31/2019 Clouding Testing Approach2 0
11/18
7/31/2019 Clouding Testing Approach2 0
12/18
Case Study
Performance Testing implementation forANZ Bank
The performance testings main objective is tomeasure the application Performance,Throughput and Response Times based on therequired SLA mentioned in the NFR. Theperformance testing needs to be executed inthe ANZ QA Environment to identify thebottleneck and publish the results.Performance testing is an iterative process andas we conduct the load testing we may comeacross performance issues/bottlenecks relatingto the application scalability that might requiretuning of the system/application parameters inorder to scale the application for the requiredload.
Engagement Results
Conducted performance testing for the cash
management application to scale up to 700 usersload.
The application underwent tuning process duringthe performance testing.
Conducted 4 rounds of tuning and re-execution toget the response time under 5 seconds.
Monitored and fine tuned the application foroptimal resource usage.
Ensured that the application meets the
performance criteria's.
7/31/2019 Clouding Testing Approach2 0
13/18
Case Study
Performance Testing implementation for amajor European Bank
The performance testing was mandatory forthe organisation to roll out core bankingapplication for Indian market. This new corebanking application was J2EE application andwas replacing the Mainframe application.
Engagement Results
The ebbs application was able to scale maximum
of 3811 users along with dotopal, other interfaces& channels in the independent performance testenvironment and the response time for all majormodules are within the SLA
The ebbs application can run for more than 10hours without interruption and process nearly 233core business functions along with dotopal,interfaces & channels concurrently and respond
within the accepted SLA in PT environment
23K Relationships, 40K Accounts, 579K batchpostings, 1.9 Million Enquiries, 42K dotOPALpayments was able to create in PT environment
9 Channels/Interfaces sending total request ofabout 50 per second with a pace of 10 seconds
About 25 transaction Uploads with average size ofabout 15K to 20K records at regular intervals
7/31/2019 Clouding Testing Approach2 0
14/18
Case Study
QA Process Consulting For
Major Commodity Trading
A global leader in managingthe supply chain of agricultural,industrial and energy products.The IT department wanted tostreamline it QA process tomake sure that SoftwareApplication were developed
and rolled out with high qualitywithin the cost and schedule
Engagement Results
Customer engaged QAssure for this initiative to perform thestudy and provide detailed recommendations along with thecost benefit analysis and deployment plan.
QAssure worked with Customer, to study their existingprocess and performed the gap analysis by bench markingthe existing process with the industry best practices.
QAssure finally came out with the set of recommendations,the cost benefit analysis and deployment plan for
implementing the solutions
7/31/2019 Clouding Testing Approach2 0
15/18
Case Study
Automation Testing Framework
implementation for Major Telcoclient
We designed a Hybrid Frameworkin QTP that had an interface toadminister test case management,test execution and testdistribution. Designed reusablefunctions/keywords could be
reused across applications and inspite of the initial effort, and theeffort in plugging in new projectsin to the framework would be veryless.A group of reusable functionsmake a test case and since thesekeywords are incorporated intothe interface, thus allowing the
end user to create or manage thetest cases.
Engagement Results
Interface for test case management and execution: The testcases are built and executed from an interface enabling iteasy to use and intuitive even for resources without theknowledge of the automation tool used.
Selective test execution: Test cases can be executed as abatch and can be executed based on the attributes (for e.g.Category. Priority), and not to mention the ability to execute
a specific test case.
Multiple machine execution: The test cases can beexecuted on a target machine, or individual test cases canbe assigned to different machines.
Reporting Excel & HTML: The framework allows logging theresults either in excel file or to an HTML. This results aredescriptive enough to give details on the actions performedin each test case.
7/31/2019 Clouding Testing Approach2 0
16/18
7/31/2019 Clouding Testing Approach2 0
17/18
Note: Schedules are subjected to change based on the firm up requirements.
Resource Man Day Rate No. of Days / month Per month cost No. of months TotalTest Manager 750 21 15750 6 94500
Test Analyst I 600 21 12600 6 75600
Test Analyst II 600 21 12600 4 50400
Tools Cost 6 months Term License
LoadRunner 75000
HP UFT 50000
Schedules / Commercials
ZonesJUN JUL AUG SEP OCT NOV DEC
Basic TestPlan Sign off Test Case Sign off Phase 1 Sign off Phase1 l ive
Medium TestPlan Sign off Test Case Sign off Phase 2 Sign off Phase 2 live
High TestPlan Sign off Test Case Sign o Phase 2 Sign off Phase 2 live
Note: The price number are subjected to changebased on Tool Price
Note: The number of resources are subjected to increase based on the final scope of work
7/31/2019 Clouding Testing Approach2 0
18/18
Thank You