Talk:Functional Testing

Functional Test (FT) Procedure

The Software Testing Plan [#1413] is created in the BlueCommons VRE Folder. The Software Testing Plan contains two folders: Material and Releases. Material
It contains:

1. the general XLS template to be instantiated by each portlet developer for compiling the Testing Plan;
2. the Portlet Folder for each Portlet to be functionality tested. The sintaz to create the Portlet Folder is:

     $portlet_name_folder 

A Task (Redmine Ticket) will be assigned, by the Release Manager, to each Portlet developer. 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).
Releases
It contains a Folder for each gcube Release containing the tests to be executed.
Other Info
FT procedure will be adopted starting with the gCube 3.10 release. Pre-requisite

1. FT testing: pre-production infrastructure hosted at CNR .

Functional Test Master Table

This table summarizes the functionals tests results for the Portlets applications as will be executed in the pre-production infrastructure. The second row (colored in red) is an example how should be filled this table.
The functionals tests are executed using the Portlet Testing Plan Template.
Legenda:

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)