Difference between revisions of "Talk:Functional Testing"
| Line 1: | Line 1: | ||
<H1> Functional Test (FT) Procedure </H1> | <H1> Functional Test (FT) Procedure </H1> | ||
<br> | <br> | ||
| − | + | The Software Testing Plan [#1413] is created in the [https://i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace BlueCommons VRE Folder]. The Software Testing Plan contains two folders: '''Material''' and '''Releases'''. | |
| + | '''Material''' | ||
<br> | <br> | ||
| − | + | It contains: | |
| − | + | # the [https://goo.gl/kQGSf0 general XLS template] to be instantiated by each portlet developer for compiling the Testing Plan; | |
| − | + | #the Portlet Folder for each Portlet to be functionality tested. The sintaz to create the Portlet Folder is: | |
| − | # the [https://goo.gl/kQGSf0 general XLS template] | + | |
| − | #the Portlet Folder | + | |
'' $portlet_name_folder'' | '' $portlet_name_folder'' | ||
| + | A Task ([https://support.d4science.org/projects/gcube 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). | ||
<br> | <br> | ||
| − | + | '''Releases''' | |
| − | + | ||
<br> | <br> | ||
| − | + | It contains a Folder for each gcube Release containing the tests to be executed. | |
| + | <br> | ||
| + | '''Other Info''' | ||
| + | <br> | ||
| + | FT procedure will be adopted starting with the gCube 3.10 release. | ||
| + | '''Pre-requisite''' | ||
| + | <br> | ||
| + | #FT testing: pre-production infrastructure [https://preprod.d4science.org hosted at CNR] . | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<H2>Functional Test Master Table</H2> | <H2>Functional Test Master Table</H2> | ||
<br> | <br> | ||
Revision as of 15:16, 23 November 2015
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:
- the general XLS template to be instantiated by each portlet developer for compiling the Testing Plan;
- 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
- 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) |
