Userback UAT process

Lynsey Jackson
Lynsey Jackson
  • Updated

During the UAT testing phase, we require you to validate the deliverables and key functionality through an online feedback tool called Userback. Userback is a tool integrated into your browser by an extension which allows you to collect feedback using screenshots and recordings.

For each site that you are testing, there will be a separate Userback project set up to add bugs to. 

It's important to understand that Userback is most effective when used through the browser extension. The use of the browser extension may require internal approval for installation on tester devices. We recommend starting any approval processes ASAP to avoid delays.

Please note, Userback does not have the functionality to store test cases or scenarios to test against. 

Overall process 

  1. We will create a Userback project for each URL needing testing
  2. You will nominate up to three testers for Userback accounts
  3. We will send email invitations to those testers to set up usernames and passwords. Note, invitations expire after 72 hours.
  4. Testers will record bugs against the relevant project/site
  5. Bugs you submit will show in the Userback tool for us to assess, validate and triage. We can make comments on your bugs and may request more information or a screensharing session.
  6. Once the bugs are resolved, they will be marked ‘Resolved’ in Userback

Top tips for effective bug recording

  • Make sure to expand on expected behaviour vs. seen behaviour so we can understand how to validate your bug.
  • We appreciate any advice and pointers from testers on possible resolutions included as a comment on the bug.

Recording bugs in the app

If you have a full Userback account, bugs can be recorded manually by logging into the app: 

  1. Log into https://app.userback.io/
  2. Select the relevant site/project then choose Feedback
  3. Click the + button on the top right corner
  4. Fill in the Add Feedback form; expanding the session info section to fill in the page URL
  5. Click Create

 

Unregistered tester feedback using Extension Keys

In the case where a tester wants to submit feedback to a project without a Userback account, we have the ability to establish a unique Extension Key per site/project. Note, to use an extension key, the Browser Extension will need to be installed. See Userback Browser Extension Setup for the download link and instructions.

Once a project has an Extension Key created, this key is shared with testers to allow them to log into the browser extension and submit feedback to the nominated project. 

If testers are working across multiple projects they will need to sign out and sign in again using the relevant extension key each time. 

mceclip2.png

Recording bugs through the browser extension

  1. Install the extension into your browser. See Userback Browser Extension Setup for the download link and instructions.
  2. Log into the browser extension with your Userback credentials.
  3. Ensure the Userback icon is visible in the toolbar for easy use. To do this click on the Extensions icon, then switch on ‘Show in toolbar’.
    mceclip0.png
  4. To report feedback, go to the page you would like to report feedback on then click on the Userback icon.
    mceclip1.png
  5. This will present you with the option to report feedback via Screenshot or Video Recording.
  6. A panel will appear on the right-hand side of the page for you to complete the details of the bug:
    • Select the correct site/project from the top of the panel
    • Leave the ‘Assign to’ field on Automatic
    • Fill out the details including ‘Title’ and ‘Leave a comment’
    • You can use the toolbar at the bottom of the screen to draw and add text to the screenshot
    • Click ‘Submit’

Viewing and tracking bugs

  • For the best visibility, we recommend using Board View
  • Under Status, ensure Open, Under Review and Resolved are ticked. 
  • The flow of bugs goes in order from:
    1. Open - Dataweavers owns these and works on them
    2. Under Review - you will own these and re-test bugs until you consider them resolved
    3. Resolved - you will mark them Resolved OR move them back to Open with comments and screenshots if they are not fully resolved
  • Dataweavers will mark bugs as High priority (orange flag) or Urgent priority (red flag) to identify blockers for go-live. You can filter on Priority if you like.

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request