Difference between revisions of "Talk:Functional Testing"
Line 6: | Line 6: | ||
#the [https://goo.gl/kQGSf0 general XLS template] to be instantiated by each portlet developer for compiling the Testing Plan and | #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 | #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). | + | 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. | A Task ([https://support.d4science.org/projects/gcube Redmine Ticket]) will be assigned, by the '''Release Manager''',to each portlet developer. | ||
<br> | <br> |
Revision as of 16:50, 23 November 2015
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:
- the 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 (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 FT procedure will be adopted starting with the gCube 3.10 release.
- 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:
- The effort should be based not per application but per number of tests to be executed [1].
- The tester should not be the same owner of the portlet[2].
Functional Test Master Table
This table will include the functional tests results for the Portlets applications executed in the pre-production infrastructure.
The second row (coloured in red) is an example how should be filled this table.
The functional tests will be executed using the Portlet Testing Plan Template.
Legend:
Performed | |
Not Performed |
Partner Name | Component Name | Owner (@) | Domain Expert(@) | Scope | WAR is Valid | Renders OK | Service Deployed | Functional Test | Notes | Tester Name(@) NEW FILED |
---|---|---|---|---|---|---|---|---|---|---|
CNR | org.gcube.portlets-admin.transect | Fabio Sinalbi (fabio.sinibaldi@isti.cnr.it) | Fabio Sinalbi (fabio.sinibaldi@isti.cnr.it) | Scope | - | Maria Di Girolamo (mariaantonietta.digirolamo@eng.it) |