|
|
| Line 1: |
Line 1: |
| − | # '''Functional Test''':<strike> when stage 1 and 2 are completed the related Portlet application domain expert is assigned to the functional test by opening a new ticket of type ‘functional test'</strike> when stage 1 and 2 and 3 are completed the functional test is assigned to the testing team which performs it by following the Software Testing Plan.
| |
| − | <br>
| |
| − | <strike>This functional test ticket contains also a link to the</strike> An online table
| |
| − | '''[[Functional Test Master Table Template|Functional Test Master Table Template]]''' is created by the portal manager : <strike>(see Figure 1 for column names) </strike> and shared with each actor involved in the functional testing procedure. Each row contains a Portlet artefact having to pass the functional testing procedure[[https://wiki.gcube-system.org/index.php?title=Functional_Testing&action=edit§ion=1 Functional Test (FT) Procedure]]. <strike>With respect to the table header reported in the figure below.</strike> <strike>The columns indicate the following:</strike>. Below the description of the table's fields:
| |
| − | #* Component Name: Portlet unique identifier;
| |
| − | #* Owner: generally the developer of the Portlet or the responsible of the application;
| |
| − | #* Tester Name: name of the tester;
| |
| − | #* Scope: the infrastructure scope where the Portlet has to be functionally tested;F
| |
| − | #* Web Archive validity: indicates if the software package produced by the build system can be correctly deployed in the iMarine Gateway. The portal manager compiles this part;
| |
| − | #* Renders OK: indicates whether the Portlet displays correctly in the iMarine Gateway. The portal manager compiles this part;
| |
| − | #* Service Deployed: indicates whether the infrastructure services composing the back-end of the Portlet application are ready and fully functional. The infrastructure manager compiles this part;
| |
| − | #* Functional Test: compiled by the Application Domain Expert user, indicates if the functional test was performed;
| |
| − | #* Notes: if the functional test cannot be performed the Application Domain Expert can explain the reasons in the notes;
| |
| − | #* Link Test Plan: the [https://goo.gl/kQGSf0 general XLS portlet test plan] link
| |
| − | #* Ticket: the [https://support.d4science.org/projects/gcube Redmine ticket] associated to the functional test ;
| |
| | | | |
| − | <strike>[[File:Functional tests.png|center|800px|Figure 1: functional test master table]]</strike>
| |
| − |
| |
| − | == Functional Test (FT) Procedure ==
| |
| − | <br>
| |
| − | The Software Testing Plan [https://support.d4science.org/issues/1413#change-6072 #1413] is created in the [https://i-marine.d4science.org/group/data-e-infrastructure-gateway/workspace BlueCommons VRE Folder] containing two folders: '''Material''' and '''Releases'''.
| |
| − | <br>
| |
| − | '''Material''' will contain:
| |
| − | #the [https://goo.gl/kQGSf0 general XLS template] to be instantiated by each portlet developer for compiling the Testing Plan and
| |
| − | #the portlet folder (created by '''Portal Manager''') for each portlet to be functionality tested. The syntax used to create the portlet folder
| |
| − | will be: '''''$portlet_name_folder'''''. 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). To describe the functional tests, the developer will use the [https://goo.gl/kQGSf0 Portlet Testing Plan Template]; this file will be pasted and completed into the Release folders by the testers.
| |
| − | A Task ([https://support.d4science.org/projects/gcube Redmine Ticket]) will be assigned, by the '''Release Manager''', to each portlet developer.
| |
| − | <br>
| |
| − | '''Releases''' will contain a folder for each gCube release containing the tests to be executed.
| |
| − | <br>
| |
| − | FT procedure's steps are describe below:
| |
| − | *The '''pre-production infrastructure''', [https://preprod.d4science.org 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''' [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].
| |
| − | #For every release a wiki page will be created: '''$functional_test_master_table_Org_gCube_#Release'''(e.g. [[Functional Test Master Table Template gCube Release 3.10.0|Functional Test Master Table gCube Release 3.10.0]]). The [Functional Test Master Table Template|Functional Test Master Table Template]] will be fill by the testers with the FT results for the portlets applications in the pre-production infrastructure [https://wiki.gcube-system.org/index.php?title=Functional_Testing&action=edit§ion=4]
| |
| − | <br>
| |
| − |
| |
| − | = Roles =
| |
| − |
| |
| − | The functionality testing activity foresees the involvement of the following roles:
| |
| − |
| |
| − | * [[Role Tester|Testers]]:
| |
| − | ** responsible for the execution of the functionality tests and to submit functionality test bugs
| |
| − | ** responsible to fill the dedicated [https://goo.gl/kQGSf0 Portlet Testing Plan Template] and the [[Functional Test Master Table Template|Functional Test Master Table Template]] as described in the [https://wiki.gcube-system.org/index.php?title=Functional_Testing&action=edit§ion=2 previous section].
| |
| − | * [[Role Developer|Developers]]:
| |
| − | ** responsible for fixing functionality test bugs
| |
| − | ** carried out by JRA members
| |
| − | ** responsible to fill the dedicated [https://goo.gl/kQGSf0 Portlet Testing Plan Template] as described in the [https://wiki.gcube-system.org/index.php?title=Functional_Testing&action=edit§ion=2 previous section].
| |
