Difference between revisions of "Talk:Functional Testing"
| Line 8: | Line 8: | ||
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). | 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''' contains a Folder for each gcube Release containing the tests to be executed. | *'''Releases''' contains a Folder for each gcube Release containing the tests to be executed. | ||
| − | |||
The FT procedure will be adopted starting with the gCube 3.10 release. | The FT procedure will be adopted starting with the gCube 3.10 release. | ||
<br> | <br> | ||
The pre-production infrastructure [https://preprod.d4science.org hosted at CNR] will be used for the FT testing. | The pre-production infrastructure [https://preprod.d4science.org hosted at CNR] will be used for the FT testing. | ||
| − | + | <br> | |
| + | The Release Manager will ask to every partners to suggest the persons that will form the testing team. | ||
| + | <br> | ||
| + | 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]. | ||
<H2>Functional Test Master Table</H2> | <H2>Functional Test Master Table</H2> | ||
<br> | <br> | ||
| − | This table summarizes the | + | This table summarizes the functional tests results for the Portlets applications as will be executed in the pre-production infrastructure. |
| − | The second row ( | + | The second row (coloured in red) is an example how should be filled this table. |
<br> | <br> | ||
| − | The | + | The functional tests are executed using the [https://goo.gl/kQGSf0 Portlet Testing Plan Template]. |
<br> | <br> | ||
| − | ''' | + | '''Legend:''' |
<br> | <br> | ||
{| border="0" | {| border="0" | ||
Revision as of 15:56, 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 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 contains a Folder for each gcube Release containing the tests to be executed.
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 summarizes the functional tests results for the Portlets applications as will be executed in the pre-production infrastructure.
The second row (coloured in red) is an example how should be filled this table.
The functional tests are 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) |
