The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "PROC05 Software deliverable testing"
(Created page with "{{Template:EGI-Engage menubar}} {{TOC_right}} <br> {| class="wikitable" |- | '''Title''' | <br> |- | '''Link''' | <br> |- | '''Owner<br>''' | Quality Manager<br> |- | '''S...") |
|||
| Line 6: | Line 6: | ||
|- | |- | ||
| '''Title''' | | '''Title''' | ||
| <br> | | Software deliverable testing<br> | ||
|- | |- | ||
| '''Link''' | | '''Link''' | ||
| <br> | | [https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing]<br> | ||
|- | |- | ||
| '''Owner<br>''' | | '''Owner<br>''' | ||
| Line 28: | Line 28: | ||
= Overview = | = Overview = | ||
This procedure is part of [[PROC01_Deliverables_and_milestones_review|Review procedure for deliverables and milestones]]. It describes how quality check is done for SW deliverables. <br> | |||
= Definitions = | = Definitions = | ||
| Line 42: | Line 42: | ||
= Requirements = | = Requirements = | ||
Production tools, which are part of EGI Catalogue, should have a production and a testing/devel instance (at least 2 instances in total) | |||
= Steps = | = Steps = | ||
Each product team should choose between two possible ways to verify the quality of its release: | |||
1. Manual test | |||
2. (Semi-)Automatic internal procedure to test the release In both cases, tests and short document must be finished by the deliverable deadline in the DoA. | |||
== Manual Test == | |||
<br> | |||
{| class="wikitable" | {| class="wikitable" | ||
| Line 61: | Line 71: | ||
| <br> | | <br> | ||
|} | |} | ||
== (Semi-)Automatic Internal Testing procedure<br> == | |||
<br> | |||
{| class="wikitable" | |||
|- | |||
! Step# | |||
! <br> | |||
! Responsible | |||
! Action | |||
! Prerequisites, if any | |||
|- valign="top" | |||
| <br> | |||
| <br> | |||
| <br> | |||
| <br> | |||
| | |||
|} | |||
= Revision History = | = Revision History = | ||
Revision as of 15:31, 31 May 2016
| Title | Software deliverable testing |
| Link | https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing |
| Owner |
Quality Manager |
| Status | Approved |
| Approval date | |
| Related document |
Overview
This procedure is part of Review procedure for deliverables and milestones. It describes how quality check is done for SW deliverables.
Definitions
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Entities involved in the procedure
- XX: person who...
- XXX:
Requirements
Production tools, which are part of EGI Catalogue, should have a production and a testing/devel instance (at least 2 instances in total)
Steps
Each product team should choose between two possible ways to verify the quality of its release:
1. Manual test
2. (Semi-)Automatic internal procedure to test the release In both cases, tests and short document must be finished by the deliverable deadline in the DoA.
Manual Test
| Step# | Responsible | Action | Prerequisites, if any | |
|---|---|---|---|---|
(Semi-)Automatic Internal Testing procedure
| Step# | Responsible | Action | Prerequisites, if any | |
|---|---|---|---|---|
Revision History
| Version | Authors | Date | Comments |
|---|---|---|---|