...
- Automated testing of browsers – free if not cheap. Review all versions of supported browsers.
- Test on various devices – mobile, tablet, PC
- Content testing – ensure upload is all correct, and all mappings exist, and content hasn’t changed
- Architecture in Squiz
- Sharing of approach in Squiz (within web team) – so Andrew is not the only one who knows how to edit etc.
- Building in measures of users behaviours on the page –google analytics (actions for every click), specialised tool (heat maps)
- Can share in the dev environment before hand
- User testing – set up dummy site end of sprint 20, with linked survey for feedback
- Content team testing
Release Release process:
Go live process:
- Release – aim for Tuesday (29th)
- Release process will either show old or new page during that process.
- Can be tested on local CSS before release to live in CMS
Can share in the dev environment before hand- Using the exact same asset and URL for the new subject page
- Rollback – can remove page immediately, and drop old content back in (circa 10 minutes). This approach can and will be tested.
...