Release 1 - Testing Approach

Owned by Chrissi Dean (Unlicensed)
Last updated: Oct 14, 2015Version comment

Meeting date: 16/09/15

In attendance:  Nathan Irwin, Andrew Bredenkamp, Joe Lobotka (Unlicensed), Paul Seiler (Unlicensed), Chrissi Dean (Unlicensed) 

Testing areas discussed:

  • 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 needs to be agreed with WIP and core team
  • Noted we can share the page in the dev environment in advance for testing
  • Full testing of rollback procedures

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
  • 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.

Questions:

Can we release without a way to search for the individual subjects?

  • Could we provide the full list still? – full subject list here
  • Could we release the taxonomy in the first release, then a sprint later release the search (like VI) – CHOSEN OPTION, BUT NEEDS EXPLORING

Actions: