Proposal to Update Test Handbook Homepage

This is a proposed update to the Test Team Handbook homepage. The new content is located here for review:

Handbook Homepage Refresh

Over the past couple years, the Test Team has evolved from a focus on UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. workflows to include additional aspects of software testing, including bug reproduction and patch testing, betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. release testing, and automated unit and E2E testing.

As part of a key initiative to improve accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( to testing, this Test Handbook update seeks to clarify the current “duty of care” for the Test Team, and provide a less intimidating introduction on where contributors can get started. This is the first of several page updates toward this goal.

Updates to the handbook homepage include:

  • Clarify the scope of today’s Test Team and areas of impact.
  • Welcome contributors from any experience level.
  • Provide links to get started with testing.
  • Remove reference to “flows” testing that is no longer practiced or applicable.

Please review the updated homepage content here:

Leave feedback in the comments below by 10 January 2023.

Thank you to @boniu91 for peer review of this post.