Developer DoD

Developer has reviewed and confirms:� Feature passes tests on the Local environment� Feature meets all requirements in the user story � Feature meets all acceptance criteria� Special and manual testing steps are all documented in the JIRA ticket� If the issue requires Unit, Functional, or UAT tests:

� All automated tests passed � The command to automatically execute the test through the CI server has been created

� User documentation has been produced to cover the new or altered feature:� in a README.md or Confluence page and linked to the ticket

� Technical Concept documentation has been updated� If feature toggles are implemented:

� Feature has been passed testing with the feature toggle in both an enabled and disabled state� Configuration of the toggle is applied correctly for the server, to show as ON or OFF� Documentation for how to adjust the toggle has been created

QA Peer Reviewer DoD

Peer has reviewed and confirms:� Feature passes tests on pre-production environment� Feature meets all requirements in the user story � Feature meets all acceptance criteria� Feature passes any special testing steps identified in the ticket� All automated tests pass� No errors in code style check� No errors in log files:

� The Apache or Nginx error log� The application log

� User documentation present, if required� Feature toggles are implemented properly� Feature or content is present on the target server/environment

Definition of DoneThe following conditions must be met to move a ticket on the Jira board from ‘In testing’ to ‘Done’

www.web-essentials.ch

About Web Essentials.Web Essentials is a digital products & services company with expertise in web applications, websites and other digital tools for a diverse client base ranging across a wide spectrum of industry sectors. Web Essentials is also committed to making a positive social impact on the lives of Cambodians by providing employment, mentorship and training to Cambodian technology graduates.

Find out more on our website: www.web-essentials.ch

Or send us an email: sales@web-essentials.ch

Web Essentials Release guidelines:

The following conditions must be met to release an increment to production: � All builds for the project in Jenkins are green� Compiled scripts, styles and libraries downloaded from bower and composer must be ignored from git

repository� Styles and scripts compilation is generated once by Jenkins and push to all servers� All code & configurations have been deployed to the target server (the demo server or live server)� All tests still pass on all servers to which work was deployed� All acceptance criteria are still satisfied� Necessary contents has been added on the content master server� No errors in log files

Web Essentials Best Practice Guidelines

Development best practices that all projects and development teams within the organization are expected to follow:� All user stories must contain clear acceptance criteria that are testable� Coding must follow the standard defined by the box that project is inherited from (TYPO3 Box, Flow Box or

Neos Box)� Changes to server configuration/ deployment steps must be updated through the script and not manually

applied on the server.� If there is a restriction, clear documentation of the manual step must be produced

� A Technical Concept should be created and documented for all Moderate to Complex projects.� Make sure the local machines have all necessary environment setup to guarantee same functionality on all

servers.Examples:

� Code style check� UAT� Unit test� Functional test� Web server config� PHP version� PHP config� PHP modules� DB config