The primary intended audience of this article is any QA Engineer at Cantilever. However, Project Managers may also find it useful since it provides an insight into what QA Engineers do for (and expect from) the rest of their team when performing a QA test.

QA Engineer Tools

The basic set of tools for every QA Engineer at Cantilever includes:

• Site Documentation
• Any source material to be compared against
• Issues repository for where to report any issues may found
• Task Details (provided by the person assigning the task)
• BrowserStack, in addition to any direct access you may have to various machines and browsers
• Issue-Reporting template (You already have this: See below.)
• Screen capture media app(s)

Types of Tests

You will always run one of two types of browser tests in a QA pass:

• (Basic) Functionality Test
• Full Browser Test

Optional Testing Requested:

• Regression Testing

Running QA Tests and Reporting Issues

• Use the Project Documentation to guide testing in the appropriate browsers
• Report issues clearly and in a consistent format

Naming/Labeling Issues

A Word on Re-Testing (Fixed) Issues

Accessibility Audits

Accessibility audits are different from but related to QA tests. The purpose of an audit is to find areas where a site or feature is not in compliance with WCAG standards (WCAG AA is typically considered the threshold for "ADA Compliant"). The QA engineer may make recommendations to improve or fix these issues.

There are two different kinds of Audits:

• Design Accessibility Audits