Skip to content
Stéphane Brunner edited this page Sep 12, 2018 · 3 revisions
  1. The code related to the story has been reviewed by at least one developer
  2. The result of the story is deployed on the demo server
  3. The feature is checked against the Testing Framework to determine the possible fallout of the change, when writing tests is easy (fast). F.e. a task of 10 minutes can have tests writing of 30 minutes, but a task of 1 day should have tests writing for approx. 2h.
  4. The user story defined in the story should be added into the testing book and has been run successfully by a C2C developer and by the C2C-side internal reviewer (usually the Product Owner) on the demo server.
  5. All the documentations pages are updated accordingly (c2cgeoportl, ngeo (actually broken)).
  6. New features usage are documented in the User documentation.