Difference between revisions of "Talk:Functional Testing"

Revision as of 13:27, 14 September 2016

Functional Test (FT) Procedure

The Software Testing Plan #1413 is created in the BlueCommons VRE Folder containing two folders: Material and Releases.
Material will contain:

1. the general XLS template to be instantiated by each portlet developer for compiling the Testing Plan and
2. the portlet folder (created by Portal Manager) for each portlet to be functionality tested. The syntax used to create the portlet folder

will be: $portlet_name_folder. Every developer will create the actual testing plan into Material/$portlet_name_folder including by adding additional files required for the test (e.g. cvs_files). To describe the functional tests, the developer will use the Portlet Testing Plan Template; this file will be pasted and completed into the Release folders by the testers. A Task (Redmine Ticket) will be assigned, by the Release Manager, to each portlet developer.
Releases will contain a folder for each gCube release containing the tests to be executed.
FT procedure's steps are describe below:

• The pre-production infrastructure, hosted at CNR, will be used for the FT testing.
• The Release Manager will ask to every partners to suggest the persons that will form the testing team.
• The following recommendations should be mandatory:

1. The effort should be based not per application but per number of tests to be executed [1].
2. The tester should not be the same owner of the portlet[2].
3. For every release a wiki page will be created: $functional_test_master_table_Org_gCube_#Release(e.g. Functional Test Master Table gCube Release 3.10.0 or Functional Test Master Table gCube Release 4.0.0). The Functional Test Master Table Template will be fill by the testers with the FT results for the portlets applications in the pre-production infrastructure.

Below the NEW LINE regarding the CRT management for FT testing: The Tester can start with the functional test when Deployer/Infrastructure Manager updates the CRT : {status: Under Integration -> Deployed on Preprod}.

In case the functional testing failed , the Tester open the issue in the following way:

1) The Tester updates the CRT:{status: Deployed on Preprod -> FT Issue, comment: <issue description>}. The comment should always include a link to a relevant log/report file.

2) After the resolution of the issue, the developer updates the CRT:{status: FT Issue -> Under Itegration, comment: <issue description>}.

3) The tester can repeat the testing and if the test passed, updates the CRT:{status: FT Issue -> Tested on Preprod, comment: <issue description>}. Otherwise he/she repeats the step 1) (the status return in FT Issue).

NOTE:
 - Deployed on Preprod  indicates  that the component has been deployed on ALL nodes of preproduction and is up and running.
 - FT issue  = Functional Testing issue.
 - Tested on Preprod : indicated that the developer and/or the portal manager or the preprod infrastructure manager 
   are confident that the component behave as expected and can be released as is.