Common Sense QA

To say that the digital analysts at RXA have QA experience would be an understatement. Here are some common sense tips that they have picked up along the way and think are worth sharing. (After all, sometimes common sense isn't so common.)

  • The first and most important thing is to document your results.
  • Second, follow up on your results to ensure they are fixed and that the respective parties are notified of unfixed bugs, how they will affect their reports and when to expect a fix.
  • Highlight your specification document sections where errors were found along with documenting your QA results.
  • As you go through your QA, it is very important that you document issues as you find them. Don't try to stuff them all in your memory for later. Try to record three or four at a time.
  • Be very focused during QA. Remove the things that you know distract you. For example, you might find it hard listening to certain types of music when you work because your ears are distracted. Turn off Slack notifications for a while.
  • Be alert. Fortunately, no one is likely to die if you miss something, but it could cost your company money if they lose the ability to gain insight into their process or an invalid analysis is provided.
  • Make sure that you have the necessary block of time to get through your QA or at least a good chunk of it. It can sometimes take five to ten minutes just to get set up for QA . Allow time for logging into the client's VPN, accessing the correct page, setting up your QA results document and opening and configuring your packet sniffer.
  • Get a second set of eyes. It is very easy to simply miss a bug, especially if you were the developer. To borrow from the construction idiom, "QA twice, fix once".
  • QA on your most widely used platforms and browsers.
  • Use a QA platform like Observe Point to automate your QA and perform regression testing. No one likes to test the same thing over and over with every release.
  • Last, be nice when you find bugs. No one likes to find out they missed something. Having a good rapport with your developers is a huge key to success in digital analytics.