Software Quality Assurance

  1. tickets are created in a new state, and elaborated until satisfying. This means having the following information:
  2. tickets can be created by managers, testers, etc. Tickets in a new state are responsibility of the manager.
  3. tickets are then put to assigned state. This means that the developer can start working on them.
  4. once work has reached a progress level satisfying to the developer, tickets are put in resolved state. The percentage indication is only a useful tool for the developer and is not meant to control the ticket state.
  5. tickets in resolved state are responsibility of the tester, who can work on them. He either sets them to verified if the quality is good and no issues are found, or he sets them to feedback otherwise. Tickets in feedback state are responsibility of the developer who was first assigned to them. Note: the tickets are checked in the staging environment through its explicit links http://enrd.enrd.eu and https://webgate.enrd.eu/agri_enrd_d/myenrd/ .
    Note that there is no need to deploy any file on the staging environment thanks to the continuous integration procedure. It is however still necessary, for the moment, to deploy database changes manually. Investigation to automate this is planned.
  6. tickets in verified state are ready for deployment. All tickets in verified state should be linked to a support ticket called package number x. The x is a progressive number. Once every ticket linked with a package is verified, the package may be deployed to test.
  7. Once a package is deployed to test, another round of testing is done on every ticket belonging to the package. This can result in the package support ticket being put in feedback state if issues are found on any of its tickets, or in verified state otherwise.
  8. A verified package is ready to be deployed in Acceptance and Production. Another round of testing is necessary once this happens; in the case that issues are found they are to be resolved immediately. If this is not possible in a reasonably short time frame, the deployment is to be rolled back and the ticket put to feedback state until the problem is dealt with. Once accepted by the client, a package on Acceptance can be deployed on Production and this last verification step repeated.
  9. A successful deployment to Production marks the time where the tickets in verified state can be closed.