Skip navigation


Definition of Ready for Testing

To ensure a component is prepared for testing, the following conditions must be met:

  • The organism is created.
  • The organism is integrated into the template (of the current Epic's page).
  • The organism is displayed on the page, mirroring the Zeplin design's visual aspects. For lists, only the initial items are required.
  • All design-specified icons are present.
    which might entail generating several list items to cover them comprehensively.
  • All states within a list are covered
    including scenarios like a product card with or without a "New" badge.
  • All states must be demonstrated within Pattern Lab.
    • If a block is repeated in a list, this demonstration can be done there.
    • If not, each state must be created where the block is initially declared.
    • The approach for state creation should follow the method outlined in Using Pseudo-Patterns - Pattern Lab
  • Links to the specific testable page (not the template) are provided in the task.
  • For blocks with multiple states, links enabling QA to examine all the states are included.
  • The status is changed to "Ready for testing."
  • The task is assigned to the QA team.
    The comment in the ticket should adhere to this template:

    Hi [QA Name]
    Ready for testing.
    URL: [URL for testing]
    [Include any steps, notes, or additional information necessary for testing the ticket.]

Bug Severity Levels

Minor Frontend Bugs

Definition: Minor Frontend bugs encompass issues that can be rectified solely through CSS/JS modifications. They do not necessitate HTML code re-integration and are automatically applied when updating the Frontend package.

Typically, the following issues fall under the category of minor bugs:

  • Font attributes like family, font size, font weight, font style, line height
  • Color
  • Margin/Padding/Gap (spacing between cards)
  • Box shadow
  • Width, height
  • For list items: include some but not all icons in the design
  • Number of columns in grid

Major Frontend Bugs

Definition: Major Frontend bugs require HTML updates for resolution. These issues necessitate re-integration into the backend or they hinder proper user interaction with the site.

Major Frontend bugs include, but are not limited to:

  • Missing elements within a block
  • Element ordering (exept items with same type in the list)
  • Incorrect or missing layouts
  • Blocks or elements that should be clickable (i.e. acting as links to other pages) not functioning as intended
  • Blocks or elements not responding adequately to mouse/keyboard events, or the response deviating from expected behavior.