- The application has a build
- There is comprehensive test coverage that includes both unit and integration (also known as acceptance) level tests that do not hit the Internet. It is highly recommended to practice Test Driven Development. Here are some testing guides:
- The build is being run by a continuous integration platform. CfA currently uses travis
- The application is being monitored
- The build is included on project monitor
- The application has been added to engine light
- The application has undergone a security audit
- A member of the tech team, along with the application developers, will ensure that the application does not expose any personally identifiable or sensitive information or could expose personally identifiable or sensitive information if the application is compromised.
- A member of the tech team, along with the application developers, will ensure the application protects against basic UI vulnerabilities, such as the OWASP to 10
- The application has undergone a client-side performance audit
- A member of the tech team will check over the front-end aspects. A list of frontend checks can be found here
Example checks:
- Correct expected behaviour (buttons, tabs, forms submit, links are correct etc.)
- Spelling mistakes
- Layout/formatting issues
- CSS and JS are minified and gzipped
- Cross browser/device support
- Usability testing should occur to confirm that the application works as intended with its audience.