|
|
| (24 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | <H1> Functional Test (FT) Procedure </H1>
| + | |
| − | <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''' 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 syntax used to create the Portlet Folder will be: ''$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).
| + | |
| − | *'''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'''.
| + | |
| − | <br>
| + | |
| − | 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>
| + | |
| − | <br>
| + | |
| − | 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.
| + | |
| − | <br>
| + | |
| − | The functional tests are executed using the [https://goo.gl/kQGSf0 Portlet Testing Plan Template].
| + | |
| − | <br>
| + | |
| − | '''Legend:'''
| + | |
| − | <br>
| + | |
| − | {| border="0"
| + | |
| − | |colspan="2" bgcolor="#3CB371"|Performed
| + | |
| − | |-
| + | |
| − | |colspan="2" bgcolor="#FFD700"|Not Performed
| + | |
| − | |}
| + | |
| − | <br>
| + | |
| − | {| class="wikitable" border="1" style="background-color:#F2F2F2"
| + | |
| − | ! Partner Name
| + | |
| − | ! Component Name
| + | |
| − | ! Owner (@)
| + | |
| − | ! Domain Expert(@)
| + | |
| − | ! Scope
| + | |
| − | ! WAR is Valid
| + | |
| − | ! Renders OK
| + | |
| − | ! Service Deployed
| + | |
| − | ! Functional Test
| + | |
| − | ! Notes
| + | |
| − | ! style="color:BLUE" |Tester Name(@) NEW FILED[[File:LookWhatNew.jpg|right|up|40px]]
| + | |
| − | |-
| + | |
| − | | style="color:#FF0000" | CNR
| + | |
| − | | style="color:#FF0000" |org.gcube.portlets-admin.transect
| + | |
| − | |style="color:#FF0000" | Fabio Sinalbi (fabio.sinibaldi@isti.cnr.it)
| + | |
| − | | style="color:#FF0000" | Fabio Sinalbi (fabio.sinibaldi@isti.cnr.it)
| + | |
| − | | style="color:#FF0000" | Scope
| + | |
| − | | style="background-color:#3CB371" |
| + | |
| − | | style="background-color:#FFD700" |
| + | |
| − | | style="background-color:#3CB371" |
| + | |
| − | | style="background-color:#3CB371" |
| + | |
| − | | style="color:#FF0000" | -
| + | |
| − | |style="color:#FF0000" | Maria Di Girolamo (mariaantonietta.digirolamo@eng.it)
| + | |
| − | |}
| + | |
