1.1 About the Client
Verifone is the leader in providing trusted, secure and innovative payment terminals, global payment as a service, and commerce enablement solutions that create more valuable experiences and rich interactions between consumers and merchants. The company's products and services include mobile, countertop and self-service payment devices, software, and web-based gateways. With 5,300 employees worldwide, and partnerships with local distributors, Verifone is able to deliver innovative payment solutions in 150 countries and across vertical markets.
1.2 About the Project
Halo is a front end account/terminal management system that is used by VeriFone users to build Merchant accounts within the TMS database and make any ongoing …show more content…
Business will provide the UAT test scenarios to QA team prior to the start of the QA testing.
Production ‘Sanity’ Testing
Performed by Verifone Ocius QA team based on the selected test cases from the master test cases set
Target is to focus on each production release, to validate basic/ core functionality is working as expected via established regression suite
Application Scope
Functional testing of specific website which is defined in Sec.2.1
Functional testing would be done on Windows 7, 64 bit.
Functional testing would be done on latest Internet Explorer browser.
Any exception with regard to testing of an application would be clearly mentioned in the test plan document prepared prior to any release
Summary - Scope of Work Owner
Environment Readiness QA Team
Testing tools availability and management QA Team
Testing artifacts delivery i.e. test plan, test cases etc QA Team
Sign off on Test artifacts Business Team
System testing, Integration testing, Nonfunctional testing as per latest NFRs guidelines QA Team
User Acceptance criteria/ scenarios …show more content…
The frequency of defect meeting is subjected to the discretion of the Test Manager.
Test Manager would be publishing defect metrics in an interval as defined in Test Plan.
3.3.9 Exit criteria
The test completion criteria for QA Testing are listed as follows:
- All the Test cases should be executed and having pass status
- No defects of priority (Critical, High, Medium) are in open state
(This may vary conditionally based on each release and a decision can be taken at that moment of time with the consensus of all concerned parties/ stakeholders.)
3.3.10 Reporting
QA will focus on Testing Efficiency (TE) metrics to measure the effectiveness of all internal Quality Control and Quality Assurance activities that includes review and testing.
TE = {Number of errors detected during all internal QC/QA activities/ Total count of all defects found in (UAT + QA )}*100
4 Resources
4.1 Skills required for the project
Resources familiar with the following skill sets are required:
Test management activities
Test Case preparation
Test Case Review
Payment Gateway domain knowledge
Test Data
Verifone is the leader in providing trusted, secure and innovative payment terminals, global payment as a service, and commerce enablement solutions that create more valuable experiences and rich interactions between consumers and merchants. The company's products and services include mobile, countertop and self-service payment devices, software, and web-based gateways. With 5,300 employees worldwide, and partnerships with local distributors, Verifone is able to deliver innovative payment solutions in 150 countries and across vertical markets.
1.2 About the Project
Halo is a front end account/terminal management system that is used by VeriFone users to build Merchant accounts within the TMS database and make any ongoing …show more content…
Business will provide the UAT test scenarios to QA team prior to the start of the QA testing.
Production ‘Sanity’ Testing
Performed by Verifone Ocius QA team based on the selected test cases from the master test cases set
Target is to focus on each production release, to validate basic/ core functionality is working as expected via established regression suite
Application Scope
Functional testing of specific website which is defined in Sec.2.1
Functional testing would be done on Windows 7, 64 bit.
Functional testing would be done on latest Internet Explorer browser.
Any exception with regard to testing of an application would be clearly mentioned in the test plan document prepared prior to any release
Summary - Scope of Work Owner
Environment Readiness QA Team
Testing tools availability and management QA Team
Testing artifacts delivery i.e. test plan, test cases etc QA Team
Sign off on Test artifacts Business Team
System testing, Integration testing, Nonfunctional testing as per latest NFRs guidelines QA Team
User Acceptance criteria/ scenarios …show more content…
The frequency of defect meeting is subjected to the discretion of the Test Manager.
Test Manager would be publishing defect metrics in an interval as defined in Test Plan.
3.3.9 Exit criteria
The test completion criteria for QA Testing are listed as follows:
- All the Test cases should be executed and having pass status
- No defects of priority (Critical, High, Medium) are in open state
(This may vary conditionally based on each release and a decision can be taken at that moment of time with the consensus of all concerned parties/ stakeholders.)
3.3.10 Reporting
QA will focus on Testing Efficiency (TE) metrics to measure the effectiveness of all internal Quality Control and Quality Assurance activities that includes review and testing.
TE = {Number of errors detected during all internal QC/QA activities/ Total count of all defects found in (UAT + QA )}*100
4 Resources
4.1 Skills required for the project
Resources familiar with the following skill sets are required:
Test management activities
Test Case preparation
Test Case Review
Payment Gateway domain knowledge
Test Data