TEST STRATEGY Cbeyond Oracle Account Receivables

Authors: Creation Date: Last Updated: XX September 25, 2011 September 25, 2011

Document Control
Change Record
3

Date 9-25-11

Author Lisa Thompson

Versio n 1.0

Change Reference No Previous Document

Reviewers

Name

Position

* Required Attendees/Reviewers

Page 2 of 8 Company Confidential - For internal use only

Contents

Document Control.......................................................................................2 Functional Specifications............................................................................4 Purpose.................................................................................................4 Test Phases...........................................................................................4 Schedule...............................................................................................5 Roles/Responsibilities............................................................................5 Quality Assurance Testing Objectives & Approach...............................6 UAT Testing Objectives & Approach......................................................7 Open and Closed Issues .............................................................................8 Open Issues...........................................................................................8 Closed Issues.........................................................................................8

Page 3 of 8 Company Confidential - For internal use only

Functional Specifications
Purpose
The purpose of this document is to outline the scope, approach, resources and schedule of intended testing activities for the Cbeyond implementation of Oracle Accounts Receivable (AR).

Test Phases
The following test phases will occur as part of the AR project: 1. Development/Configuration Testing Occurs in a development instance (DEV) Testing is unstructured and is generally conducted by the core team resource responsible for the development object or configuration

Occurs concurrently with development and configuration activities. Purpose is to verify that development objects and configurations are ready for functional unit testing Occurs in a test instance (TEST) Testing is structured with test scenarios and test scripts and is conducted by the Quality Assurance & core team resources. Occurs after development and configuration activities are completed. Purpose is to validate that all functions that the application is expected to provide work as expected (per business requirements). Occurs in a test instance (TEST) Testing is structured with test scenarios and test scripts. Scenarios focus on following transactions through end-to-end processes. Testing is coordinated by the core team but future users of the system execute the tests. Occurs after Quality Assurance testing is completed and migration of all code and configuration to test instance is completed. Purpose is for end users to validate the decisions made by the project team have resulted in a system that meets their requirements.

2. Quality Assurance Testing

3. UAT

Page 4 of 8 Company Confidential - For internal use only

Schedule
Development/Configuration Testing Quality Assurance Testing January 23 through Feb 11 (Schedule to be defined, below is just for example purposes)
Date AM Time 9:00 11:30 9:00 11:30 9:00 11:30 9:00 11:30 PM Time 1:30 4:30 1:30 4:30 1:30 4:30 1:30 4:30 Location Activities 9-9:30 Kick-off 9:00-10:00 wkly status Daily 4:00-4:30 testing status Focus on 1st round of testing 9:00-10:00 wkly status Daily 4:00-4:30 testing status Focus 2nd round of testing, defect resolution 9:00-10:00 wkly status Daily 4:00-4:30 testing status Focus on wrapping up testing, defect regression testing Complete testing, close defects, go/no-go for QA completion

UAT Testing February 20 through Mar 2 (Schedule to be defined, below is just for example purposes)
Date AM Time 9:00 11:30 9:00 11:30 9:00 11:30 9:00 11:30 PM Time 1:30 4:30 1:30 4:30 1:30 4:30 1:30 4:30 Location Activities 9-9:30 Kick-off 9:00-10:00 wkly status Daily 4:00-4:30 testing status Focus on 1st round of testing 9:00-10:00 wkly status Daily 4:00-4:30 testing status Focus 2nd round of testing, defect resolution 9:00-10:00 wkly status Daily 4:00-4:30 testing status Focus on wrapping up testing, defect regression testing Complete testing, close defects, go/no-go for UAT completion

Roles/Responsibilities
Quality Assurance Testing QA Lead (xx). Owner/Primary point of contact, testing, issue tracking

Functional Test Lead (xx). Assist/Secondary point of contact QA Tester (xx Assist with testing & issue tracking
Page 5 of 8 Company Confidential - For internal use only

Core Team (xx) Define test scenarios, write test scripts, & execute tests. Technical Lead (xx) support testing and defect resolution Developer (xx) support testing and defect resolution PMs & Managers (xx). Assist with planning, issue escalation, status.

UAT Testing Test Lead (xx). Owner/Primary point of contact, testing, issue tracking

Functional Test Lead (xx). Assist/Secondary point of contact Core Team (xx). Define test scenarios, write test scripts, & execute tests. Project Members, not on Core Team (xx). Will assist with testing on an ad-hoc basis. Technical Lead (xx) support testing and defect resolution Developer (xx) support testing and defect resolution PMs & Managers (xx). Assist with planning, issue escalation, status.

Quality Assurance Testing Objectives & Approach

The Quality Assurance Testing of AR has the following objectives: Exercise the Account Receivables solution Validate interfaces work as expected Track transactions through entry, submission, approval, invoice creation and payment

Identify areas that may require focused training Maintain a log of test results and document issues to aid defect resolution

The QA Testing of AR has the following approach: The core team will create an inventory of test scenarios. A test scenario represents the steps necessary to execute a business function in iExpense, for example, Approve Expense Report or Fax Expense Receipts. Each business requirement must be covered by at least one of the test scenarios. The detailed step-by-step instructions necessary to execute the test scenario will be documented in test scripts. Each scenario will have a test script. Test scripts also contain the expected results for the actions taken.
Page 6 of 8 Company Confidential - For internal use only

The test scenarios and scripts will be detailed, but it is not possible to be truly comprehensive. Testers should look for opportunities to extend the scenarios through negative testing, exception cases, etc. Each test scenario will be assigned to at least two users for execution. The test scenario will be considered completed once both testers have successfully completed the script without defects. Additional core team members are encouraged to test scripts that are not assigned to them, time permitting. We will log all defects in Quality Center for tracking purposes. Prior to logging the issue review with AR Test or Functional Lead to verify the system is behaving unexpectedly. After a defect is fixed the related test scenario should be rerun to verify the fix. Also it may be necessary to regression test related scenarios to verify the fix has not adversely impact other functionality. We will be tracking testing status on a daily basis to monitor the number of test scenarios executed, number failed, number completed and the number of logged and open defects.

UAT Testing Objectives & Approach

The UAT Testing of Accounts Receivables has the following objectives:

The UAT Testing of Accounts Receivables has the following approach:

Page 7 of 8 Company Confidential - For internal use only

Open and Closed Issues

Open Issues
ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues
ID Issue Resolution Responsibility Target Date Impact Date

Page 8 of 8 Company Confidential - For internal use only