Difference between revisions of "Talk:Functional Testing"

From Gcube Wiki
Jump to: navigation, search
Line 14: Line 14:
  
 
[[File:Functional tests.png|center|800px|Figure 1: functional test master table]]
 
[[File:Functional tests.png|center|800px|Figure 1: functional test master table]]
 +
 +
== Functional Test (FT) Procedure ==
 +
<br>
 +
The Software Testing Plan [https://support.d4science.org/issues/1413#change-6072 #1413] is created in the [https://i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace BlueCommons VRE Folder] containing two folders: '''Material''' and '''Releases'''.
 +
<br>
 +
'''Material''' will contain:
 +
#the [https://goo.gl/kQGSf0 general XLS template] to be instantiated by each portlet developer for compiling the Testing Plan and
 +
#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).
 +
A Task ([https://support.d4science.org/projects/gcube Redmine Ticket]) will be assigned, by the '''Release Manager''',to each portlet developer.
 +
<br>
 +
'''Releases''' will contain a folder for each gcube release containing the tests to be executed.
 +
<br>
 +
Below the steps to realize the FT procedure:
 +
*The '''pre-production infrastructure''', [https://preprod.d4science.org 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''':
 +
#The '''effort''' should be based not per application but per '''number of tests to be executed''' [https://support.d4science.org/issues/1413#change-6072].
 +
#The tester should '''not''' be the '''same owner of the portlet'''[https://support.d4science.org/issues/1413#change-6072].
 +
#For every release a wiki page will be created a new wiki page called: $functional_test_master_table_Org_gCube_Release(e.g. [[Functional Test Master Table Template gCube Release 3.10.0|Functional Test Master Table gCube Release 3.10.0]]).
 +
<br>
 +
The functional tests will be executed using the [https://goo.gl/kQGSf0 Portlet Testing Plan Template].
 +
<br>
 +
Every tester will compile the functional test master table including the functional tests results for the Portlets applications executed in the pre-production infrastructure: [[Functional Test Master Table Template|Functional Test Master Table Template]].
  
 
== Functional Test (FT) Procedure ==
 
== Functional Test (FT) Procedure ==

Revision as of 17:05, 23 November 2015

  1. Functional Test: when stage 1 and 2 are completed the related Portlet application domain expert is assigned to the functional test by opening a new ticket of type ‘functional test’; This functional test ticket contains also a link to the Functional Test Master Table Template: an online table created by the portal manager (see Figure 1 for column names) and shared with each actor involved in the functional testing procedure. Each row contains a Portlet artefact having to pass the functional testing procedure[Functional Test (FT) Procedure]. With respect to the table header reported in the figure below. The columns indicate the following:
    • Component Name: Portlet unique identifier;
    • Owner: generally the developer of the Portlet or the responsible of the application;
    • Tester Name: name of the tester;
    • Scope: the infrastructure scope where the Portlet has to be functionally tested;
    • Web Archive validity: indicates if the software package produced by the build system can be correctly deployed in the iMarine Gateway. The portal manager compiles this part;
    • Renders OK: indicates whether the Portlet displays correctly in the iMarine Gateway. The portal manager compiles this part;
    • Service Deployed: indicates whether the infrastructure services composing the back-end of the Portlet application are ready and fully functional. The infrastructure manager compiles this part;
    • Functional Test: compiled by the Application Domain Expert user, indicates if the functional test was performed;
    • Notes: if the functional test cannot be performed the Application Domain Expert can explain the reasons in the notes;
    • Link Test Plan: the general XLS portlet test plan link
    • Ticket: the Redmine ticket associated to the functional test ;


Figure 1: functional test master table

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). 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.
Below the steps to realize the FT procedure:

  • 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 a new wiki page called: $functional_test_master_table_Org_gCube_Release(e.g. Functional Test Master Table gCube Release 3.10.0).


The functional tests will be executed using the Portlet Testing Plan Template.
Every tester will compile the functional test master table including the functional tests results for the Portlets applications executed in the pre-production infrastructure: Functional Test Master Table Template.

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). 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.
Below the steps to realize the FT procedure:

  • 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 [3].
  2. The tester should not be the same owner of the portlet[4].
  3. For every release a wiki page will be created a new wiki page called: $functional_test_master_table_Org_gCube_Release(e.g. Functional Test Master Table gCube Release 3.10.0).


The functional tests will be executed using the Portlet Testing Plan Template.
Every tester will compile the functional test master table including the functional tests results for the Portlets applications executed in the pre-production infrastructure: Functional Test Master Table Template.