Planeteria Media Logo

Complete Quality Assurance

Phase Four: Deployment

Quality Assurance Overview

Quality Assurance is the phase of the project where your team members review all uploaded site content for accuracy and log any bugs, minor design edits, or functionality issues with our ticketing system.

Who’s Involved?

Al though we ask that only 1-2 people submit defects, you are able to share your test link with whomever you would like for a thorough review of the site. Some of these people may be:

  • IT
  • Department heads
  • Customer service staff
  • Board members
  • Communications staff
  • Additional stakeholders

Before the assigned due date, review each page of the website to make sure the functionality, designs, and content are working as you imagined.

To log/report/ any findings, you will be using “BugHerd”, which is a plug-in used to make logging defects easy.

If you come across content updates to log and have been trained (or will be soon), you can submit these items in BugHerd. Please prefix each defect with “Assign to Client.” Your technical lead will redirect these items to your board, enabling your team to manage content updates directly as you progress through the site.

This approach builds familiarity with the backend and helps ensure nothing slips through the cracks.

If you have more questions about this activity, please tag your project manager under the “Updates” tab above.

For directions on how to log defects, please read the box below.

Install BugHerd

  1. Look for the invitation – email from BugHerd in your inbox
  2. Accept the invite – so that you may create an account
  3. Install BugHerd – browser extension. Look for the button that says “Add to (Chrome, Firefox, Safari)”
  4. Open your dashboard – after the extension is installed.
  5. Click on your new website – you will see a BugHerd tab appear in the bottom right hand side of your screen

Logging Defects

  1. Click on the BugHerd tab – to open the menu
  2. Click on the “+” element – you are now able to hover over any element and select exactly where you would like to log a defect.
  3. Be descriptive – in your defect log. Although a pin is placed exactly where the defect is, it is still helpful to describe what you are clicking, what you are experiencing and what you are expecting to see instead.
  4. Limit BugHerd access – to 1-2 users so that you do not log duplicate defects, or contradictory instructions. Instead ask for feedback from as many people as you wish, consolidate those defects, and have one or two people actually submit the defect.