Roles & responsibilities

The typical tasks of the Testing Co-ordinator are to:

• Manage the end to end UAT process on behalf of the client (see the process map for more information)
• Identify testers and schedule their time to undertake UAT (according to the project milestones provided by Frank)
• Review and understand the website requirements (Initiation Call Summary and Kick Off Pack)
• Prepare structured test scripts for the testers to follow, using both positive and negative test scenarios – see examples provided by Frank at the end of this page
• Prepare scripts for the administrators of the site – in addition to ordinary user tests, these scripts will cover the CMS dashboard, adding and amending content and other administator tasks. It is therefore important that the Administrator testers have been trainined in the site.
• Confirm that each requirement is covered by a test script (multiple requirements can be covered by 1 script)
• Provide an overview of the site to the testers, ahead of testing commencement
• Be the sole contact point between the testers and Frank
• Triage all defects to ascertain whether they are:
  • A misunderstanding of the requirement e.g. the site is not supposed to do this
  • A new requirement and as such out of scope for this phase of the build – note these requests for future developments
  • Not actually a defect i.e. it is meant to work this way
  • Genuine defects (e.g. something is not working as expected)
• Collect genuine defects raised by the teams into a spreadsheet and share with Frank at the end of each day via Basecamp – If a defect is preventing the tester from moving onto another test then raise ad-hoc to Basecamp
• Collect the URL of the page where the defect arose
• Collect a screen shot of the defect especially if error messages are displayed
• Understand the steps taken to invoke the defect, including what browser or device the tester was using
• Manage and monitor the fixes, feeding back to Frank to confirm acceptance of the solutions

"General user" testers represent whoever will typically be using your site, such as patients, carers, members of the public, GPs or employees.  These testers could in fact be patient representatives (e.g. from your patient participation groups) or could be members of staff acting on their behalf.  

The typical tasks of the general user tester are to:

• Read and understand the test scripts provided by the testing co-ordinator. Ask any questions to mitigate the risk of non-defects being raised
• Schedule time available to undertake the testing
• Attend the site overview session
• Work through the test scripts capturing the necessary information requested
• Click on moving parts through out the site to check that they are all working correctly i.e. check all search categories and links (these should form part of the test scripts)
• Raise defects through the test co-ordinator
  • Collect the URL of the page where the defect arose
  • Collect a screen shot of the defect especially if error messages are displayed
  • Note down the steps taken to invoke the defect, including what browser and device was being used at the time
• Provide overall feedback and impressions of the site

Administrative testers represent the staff who will be editing and managing the website CMS.  

The typical tasks of the Administrator tester are to:

• Review the kick-off pack scope/out of scope section to understand the deliverables of the project (e.g. what the website is supposed to do)
• Attend the content management training (CMS)
• Use the resulting video as a reference point to triage any knowledge gaps
• Read and understand the test scripts provided by the testing co-ordinator. Ask any questions to mitigate the risk of non-defects being raised
• Add content to the site to ensure they are familiar with using the CMS
  • If no relevant content available use the ‘demo’ area of the site (this will be made apparent during the training) to see how all of the widely used blocks operate/are set up. Have a go at setting up more demo pages utilising the different blocks
• Work through the test scripts capturing the necessary information requested
• Help each other and share knowledge
• Click on moving parts through out the site to check that they are all working correctly i.e. check all search categories and links (these should form part of the test scripts)
• Raise defects through the test co-ordinator
  • Collect the URL of the page where the defect arose
  • Collect a screen shot of the defect especially if error messages are displayed
  • Note down the steps taken to invoke the defect, including the browser and device used at the time
• Do not be afraid to move around and try all of the site and the dashboard. However always be wary before deleting anything that you have not added

The typical tasks of the Project Manager are to:

• Advise and support the client throughout the UAT process (see process map for more details)
• Be the sole contact point between the client's testing co-ordinator and Frank developers
• Review all defects raised by the client to ascertain whether they are:
  • A misunderstanding of the requirement e.g. the site is not supposed to do this
  • A new requirement and as such out of scope for this phase of the build – note these requests for future developments
  • Not actually a defect i.e. it is meant to work this way
  • Genuine defects (e.g. something is not working as expected)
• Assign developer resource to fix the defects in a timely manner
• Communicate with the client if further information is required regarding the defect
• Manage and monitor the fixes, feeding back to the client to confirm delivery of solutions

The typical tasks of the developer are to:

• Fix assigned defects
• Explain why a defect may not be able to be fixed (for example, the browser being used is out of date, the solution is out of scope)
• Update the project manager on progress