1. Building Blocks The benefits of testing Jonathan Whiteside, Principal Consultant Building Blocks www.building-blocks.com

2. Building BlocksPresentation Name A talk about testing?!? 3. Building Blocks Reducing risk 4. Building Blocks Building confidence 5. Building Blocks Testing starts from day 1 of a project, not once coding has finished 6. Building Blocks 5 testing methods to reduce risk and build confidence. 7. Building Blocks Requirements Testing1 8. Building BlocksPresentation Name Many issues can be traced back to wrong, missing, vague or incomplete requirements 9. Building Blocks Pages should load quickly The website must support Facebook 10. Building Blocks Checklist 1. Is the requirement measurable? 2. Is the requirement coherent / consistent? 3. Is the requirement relevant? 4. Is the requirement traceable? 5. Are the requirements complete? Conscious requirements : problems that the new system must solve. Unconscious requirements : already solved by the current system. Unthought-of requirements : would be a requirement if it could be imagined or known to be possible. 11. Building Blocks User Testing Prototypes2 12. Building Blocks Get feedback early Using real people Builds a lot of confidence with Stakeholders Makes the team think objectively Allows you to be brave Can be done quickly and cheaply 13. Building BlocksPresentation Name 14. Building Blocks Guerilla tools 15. Building Blocks 16. Building Blocks Integrate into Design process We design in prototypes Test every week Send to User Testing on a Friday PM Review Monday AM Helps set objectives for the week ahead 17. Building Blocks Content Editor Testing3 18. Building Blocks Internal User UX is as important Customer UX Failure to adopt new CMS can lead to failure of a new website 19. Building Blocks The CMS must be easy to use Every CMS project RFP EVER 20. Building Blocks Create CMS User Stories and Test 21. Building Blocks Test with unexpected content try and break it! 22. Building Blocks Performance Testing4 23. Building Blocks Load testing is a stress test to simulate usage of a live site 24. Building Blocks Testing for Response time Page load time Server resource usage As number of concurrent users hit the website 25. Building Blocks Whats acceptable? 26. Building Blocks Start a test 27. Building Blocks Not that complicated Threads = Users Ramp up = Rate they access the site Pacing = Dwell time on a page And record a user journey in the browser 28. Building Blocks Maths is important Page views are not the same as users 300k page views may be delivered by 30k users Run over an hour 29. Building Blocks Results 30. Building Blocks Monitorserver resource usage Testing performance DURING development can help to size the technical infrastructure that will be needed Also get Developers focused on optimising code Run competitions No surprises on go live 31. Building Blocks A/B Testing5 32. Building Blocks A/B testing 1. Create 2 variations of the same page (or element of a page) 2. Show each variation to the same number of visitors 3. See which one has the best result (e.g. CTR) 4. Keep in the winning variation 33. Building Blocks Easy to create 34. Building Blocks Clear results 35. Building Blocks A/B testing Run lots of tests But no overlaps false positives Little changes can have big affects Use the results to inform future projects Time is required for planning and thinking 36. Building Blocks Testing is fun! 37. Building Blocks Thank you! Building Blocks