GNM_RCS_Software_Testing_TR

• 1. .Introduction

     1. Purpose

RCS is mostly developed and tested within GNM’s offices. An O3 Team consultant develops the software and performs the initial testing; GNM’s RCS administrator then tests the software more thoroughly. The entire process is collaborative as this has been found to be far more efficient than adhering to formal test cycles.

This document describes the level of testing performed by each party involved, and the process followed.

• 1. Scope

This document provides an overview of the testing process for new and changed software in RCS and SLM.

Testing carried out on other systems, with which RCS has interfaces, is not in scope for this document.

• 1. .Software testing

From the outset testing of RCS software has been shared between the developer (O3 Team) and GNM, with the greater proportion of testing being carried out by GNM. This approach has been adopted in order to (a) reduce outlay on consultancy fees and (b) free up more of the budgeted consultancy time for on-going development.

As a consequence software testing is very much a collaborative effort rather than a traditional cycle-based handover of software from O3 Team, followed by a formal acceptance test phase, and iterations of the cycle.

• 1. O3 Team testing

     1. Unit testing – O3 Team

For any change, bug fix or major development, O3 Team supplies unit tested software to GNM. This software is tested at a basic level to show that it performs the function required in the manner agreed with GNM. The software should:

• • Meet the agreed business requirements / fix the reported error;

  • Have a consistent look and feel to the rest of RCS/SLM; and

  • Be fit for purpose in terms of query performance and multi-user access.

O3 Team’s testing is not exhaustive e.g. not every user role is tested, and not every permutation of data is tested. More detailed testing is continued by GNM.

Any errors found during O3 Team’s unit testing are corrected prior to the software being passed to GNM for testing.

• 1. System testing

O3 Team is also involved in system testing software. At the same time unit testing is done further tests are carried out to check calls to and from the delivered software work as expected within RCS/SLM.

O3 Team also support system testing carried out by GNM as required.

• 1. Integration testing

O3 Team is also involved in testing between RCS/SLM and other systems. This is mostly in a support role often involving the following:

• • Advising on tests to be performed;

  • Ensuring database links are pointing to the correct database(s);

  • Ensuring database jobs are running / disabled as and when required; and

  • Resetting data if tests need to be repeated.

.

• 1. GNM acceptance testing

     1. Unit testing – GNM

The RCS administrator is advised by the O3 Team consultant when software is ready for GNM to test. GNM’s testing typically involves unit testing at whatever level the RCS administrator deems appropriate. This usually involves testing more use cases than O3 Team has done under different login responsibilities.

GNM’s testing is also not exhaustive. Testing is carried out to a level whereby the RCS administrator has confidence that the software can be released to the production system with a very limited probability of issues arising.

Any issues raised during testing are emailed back to the O3 Team consultant who modifies the software to fix the issue and then returns the software for re-testing.

• 1. System testing

The RCS administrator then test all calls from the delivered software to other software within RCS/SLM, and all calls to the delivered software from other software e.g. menus opening screens, screen calling other screens, or invoking reports.

Again these tests may not be repeated for every user role, but the RCS administrator will test until confident that the software performs as expected.

Any issues raised during testing are emailed back to the O3 Team consultant who modifies the software to fix the issue and then returns the software for re-testing.

• 1. Integration testing

If appropriate the RCS administrator then tests the delivered software to ensure is sends or receives data to or from other systems in the expected way. This often involves liaising with development teams on other systems e.g. the FSA who look after Oracle EBS, agreeing tests to be performed and data that will be tested with, and coordinating the effort.

Any issues raised during testing are emailed back to the O3 Team consultant who modifies the software to fix the issue and then returns the software for re-testing.

• 1. Business owner & user testing

For larger more significant software changes the originating business owner and/or a sample of end users may be invited to view the software and test it. This can occur at any stage of the development and testing process – the earlier the better to ensure the design meets expectations and to minimize re-work if it does not.

End of Document