Functional Testing

The objective of the Functional Testing activity in gCube is to ensure that all the components:

• gCube services and public interfaces, are conform to their specification
• are free from erroneous or malfunction
• can be run in the defined system requirement
• are free from code anomalies and coding errors

The goal of functional testing is to assure the appropriate quality of the gCube software. Testing, in general, is not a procedure to find bugs, but to check that the software works in accordance with the specification, architectural and detailed design documents. In addition the testing activity has to ensure that the software is easy to use and gives appropriate response in the case of wrong usage or defects that cannot entirely be eliminated. Testing is planned according to these goals.

The gCube software is composed by three types of components: services, libraries, and portlets. While deployment of services and libraries are tested with the Deployment tests, the functionality of portlets is tested through a specific procedure. Since portlets rely on services and libraries to perform their functions, testing the portlets functionalities implicitly tests also the functionalities of services and libraries.

Roles

The functionality testing activity foresees the involvement of the following roles:

• Testers:
  • responsible for the execution of the functionality tests and to submit functionality test bugs
• developers:
  • responsible for fixing functionality test bugs
  • carried out by JRA members

Infrastructure

The execution of functionality tests requires a gCube testing infrastructure fully functional. A detailed description of the testing infrastructure can be found Testing Infrastructure