Talk:Functional Testing
Functional Test (FT) Procedure
Below the Functional Testing (FT) steps [#1413].
In order to simplify of the developers and testers ' activities a Software Testing Plan is created at the BlueCommons VRE Folder will collects all results of the functional tests.
The Software Testing Plan contains two folders BlueCommons VRE Folder:
- Material containing:
- the general XLS template to be instantiated by each portlet developer for compiling the Testing Plan;
- the Portlet Folder, with the followin sintax:
$portlet_name_folder
for each Portlet to be functionality tested.
The Release Manager will assing a Task (Redmine Ticket) to each Portlet developer for marking he/her create the actual testing plan into Material/$portlet_name_folder also by adding additional files required for the test (e.g. cvsfiles).
- Releases containing a Folder for each gcube Release containing the tests to be executed.
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) |
