Hexaware Performance Test Center
Welcome to the PTC. This site contains all information related to the PTC Guidelines, Processes, Services,
Templates, Examples, Trackers, Tools, Roles & Responsibilities and Trainings. You can navigate from the left menu
between all the different items.
Consult request Phase
This Service is provided by a Test Lead from Hexaware. The Test Lead will be the interface with the Test Team and the Program Manager. The Test Lead will:
Document the Test Project requirements (High Level Questionnaires, Estimates, POC requirements, Etc.)
Develop estimates and Test Plans
Provide the “Input Package” for the test execution
Review and Approve the “Output Package” produced by Test Execution Team
Asses impacts and coordinates changes with Projects
In charge to supply the “Test Readiness” conditions for the Test Project.
Review and Approve Results
Manage Overall Test Schedule
Submits Service Requests for Extensions and/or additions in scope for different projects
Test Lead activities
Initial Meetings with PM to determine the characteristics of the services required: test requirements and time frames are discussed as well as any relevant particularity of the project.
Request the filling out of the two questionnaires by the Project Team.
Follow-up meetings with PM to clarify the information from the questionnaires.
The Two Questionnaires
There are two questionnaires which are important to be completed by the Project Team.
They are key elements of the input package according to new PTC model.
High Level Requirements Questionnaire (1 HLRQ)
Typically completed by Business Analysts.
Required before a high level estimate of work can be completed (ROM).
Technical Requirements Questionnaire (2 TRQ)
Typically completed by the Technical Architect.
Required before the Detailed Test Plan can be completed.
It is required before the Test Scripting or the Proof of Concept stages can start.
Input Questionnaires
These questionnaires include important input information like:
Volume of users to be used during the tests, concurrency, and location.
Test environment(s) to be used for testing.
Application Architecture (Application servers, DB servers, Reporting servers).
Types of previous tests executed for the application.
Functionalities to be covered.
ROM Phase
The Test Lead meets with the Project Manager and requests some questionnaires to be filled out.
Then he creates a ROM to estimate the effort required to do the performance testing of the application.
Test Lead activities
Determine the services to be provided (Volume Testing, Network Profiling and/or Database Analysis).
If specialist services are required then their estimations must be included in the ROM.
Determine Testing objectives and Testing scopes.
Send ROM to Project Manager for reviewing.
Follow-up meetings with PM to clarify the information from the ROM and discuss any pending issues regarding the estimates.
Assist the PM in teh filling out of the 2 TRQ.
Report the Status of the project to the Performance Manager.
The Test Lead responsibilities are:
Consultations with Project Managers for Performance Testing Projects.
Estimations of Work Effort.
Preparation of ROMs (Rough Order-of-Magnitude).
Creation of Detailed Test Plans.
Management of Test Execution phase (scripting, execution and reporting).
Tracking of test results.
Reporting of Test Results and project status to Project Manager and Performance Manager.
Closure of Performance Test Project.
Escalation of issues.
