In certain business contexts it's necessary to have an audit trail showing business approval of the documentation and tests for specific releases of the software.
This feature allows users to see all the approval requests on changes for a project along with their status (requested or granted).
- Anyone with access to a project can view its requests for approval
- an anonymous user can view them for a public project;
- an non-collaborator can't view them for a private project.
- Approval is requested on a specific release of the whole documentation, and any associated test results.
- Test results should be "frozen" for this release once approval has been requested - i.e. it should not be possible to modify or add further test results while approval is in progress or after it has been granted.
- Reject a request
- Cancel a request
- Comments along with or about an approval
- Given Daniela has created alpha-project
- And Daniela has uploaded her public key
- And Daniela has added some documents to alpha-project
- And Paula has accepted Daniela's invitation to collaborate on alpha-project
- And Alana has accepted Daniela's invitation to collaborate on alpha-project
- When Daniela creates release v1.0
- And Paula approves the release
- And Daniela adds some more documents to alpha-project
- When Daniela creates release v1.1
- Then Alana should see that release "v1.0" of alpha-project has been approved by Paula
- And Alana should see that release "v1.1" of alpha-project has not been approved
- Given Daniela creates release v1.0
- And Paula has approved the release
- When Alana also approves the release
- Then Daniela should see that release "v1.0" of alpha-project has been approved by Paula
- And Daniela should see that release "v1.0" of alpha-project has been approved by Alana