Testing

Quality Assurance

Jira workflow:

  1. TO DO
  2. IN PROGRESS
  3. READY FOR DEPLOYMENT TO TEST SITE
  4. READY FOR QA ON TEST SITE
  5. AMENDS
  6. READY FOR LIVE SITE
  7. DONE

QA is built into our Jira workflow so that we ensure each story meets the spec and is bug free. Once a story is 'Ready for Deployment to Test site' the developer uploads the code to the relevant environment and moves the ticket to the 'Ready for QA on Test site' column in Jira. The QA tester then knows it is ready for test. The tester independently checks that the functionality and design meet the acceptance criteria described in the story, or associated wireframe on the Jira Design board. If it meets this definition of done then the story is moved to the 'Ready for Live Site' column. If it does not then it is reassigned to the relevant party and moved to the Amends column.

Once a story is 'Ready for Live Site', it is assigned the next version number on its Jira ticket. Live versions increase via the major number (eg 5.0, 6.0, 7.0) and the current version number can be found on the Live site. When a deployment to live takes place, the version number on the front of the live site is updated accordingly. The tester will verify new stories on the live site after a deployment and, all being well, will move the ticket to the 'Done' column. If all is not well, the ticket goes back to the Amends column.

We do not apply version numbers to tickets in the QA process; however, version numbers are displayed on the front end of the test site so that all parties know when the site has been updated. Where a build is made to the test site, the minor version number is increased eg 5.01, 5.02... 5.10, 5.11, etc), where the major number reflects the current Live version.

Bugs are entered into Jira as they are found. If they are high priority then we seek to fix them in that sprint; if not, they get added to the backlog. Unfortunately, Jira does not allow a bug to be associated with a user story. Therefore, where we wish to keep similar tickets together, the bug is entered as a sub-task of the story and preceded with the text 'Bug:' in the title. Bugs that are less tightly coupled to a particular story can be entered directly with 'bug' as the ticket type. This process is also an opportunity to highlight any usability or layout issues that have emerged now that the design is in code form.


End to End Testing

We've carried out end to end testing on two colleagues in ICT that are unfamiliar with the product to ascertain if the site is intuitive. Rather than QA that tests individual stories, this is an opportunity to assess entire user journeys. By early-testing with colleagues, we have been able to refine the test scripts we will use with agents later on whilst still gathering valuable insight on how users may behave.

End to end testing has been scheduled to take place with five call agents on Wednesday 14th November. We have set up six tasks around the planned MVP Rent journeys, which we have divided up across the agents.

We will add stories to our backlog if issues come up that we need to incorporate.

User Acceptance Testing

In the final stage before roll-out to live, we carried out UAT in order to double-check that our software can handle real-world scenarios. We first wrote a number of test cases to describe these scenarios, alongside the expected results of the tests in a Google spreadsheet, see screenshot below. The UAT was shared across the team and any bugs, design or usability issues found were captured and assigned to the final sprint (Sprint 9) in Jira. The developers were then tasked with fixing these issues.

As we only had 3 days of UAT, we enacted a freeze whereby only these issues would be fixed and no additional functionality would be added to the sprint.

Device Requirements

As this is an internal solution there is not a range of devices that will access this interface. There will only be the following requirements to meet:

  • Desktop screen with keyboard and mouse.
  • 1080p screen resolution with a 24" size screen.
  • Telephone Headset

This may be subject to change if/when a device refresh is implemented.