Progress QA Test Plan

Progress QA Test Plan

Progress QA Test Plan

Environments

BrowserVersion
ChromeLatest Stable Release
FirefoxLatest Stable Release
MS EdgeLatest Stable Release
Safari [fluid:1]Latest Stable Release

[fluid:1] keyboard a11y can be slightly improved if you select the "all controls" option from "Keyboard Shortcuts" under the "Keyboard & Mouse" settings. May also need to use "option + tab" for tab navigation.

General QA Guidelines

General Use

  • Does the tool behave the way that you would expect
  • Are you surprised by anything
  • Does something take longer than you would expect
  • When the tool does something unexpected or takes too long to do something, does the tool provide appropriate feedback

QA Tests


Protocol
Perform the following tests using each browser/system environment

Report issues at: http://issues.fluidproject.org/secure/Dashboard.jspa

Please search for issues before reporting them, so as to limit the number of duplicate entries.

Progress Jira Filter

 

Unit Test

Protocol
Launch the following website to execute unit tests.

Site
http://build.fluidproject.org/infusion/tests/component-tests/progress/html/Progress-test.html

State Tests

Description
Ensures that the component properly traverses through the various states. 

Protocol
Perform these tasks on the following site, perform the tests in order.

Site
Demo

Mouse

*no tests yet*

Keyboard

*no tests yet*

Assistive Technology (AT)

Description
Tests to ensure compatibility with Assistive Technologies.

Protocol
Perform these tasks on the following site.

Site
Demo

Test 1: AT Tests

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the state tests as a guide, attempt to navigate through each state of the system
      1. Example ATs
        1. Screen Readers: JAWSNVDAVoiceOverOrca
        2. Built in AT features: WindowsMacLinuxiOSAndroid
        3. Others ATs: Speech Recognition, Screen Magnifiers, switch access, etc.
  • Expected Results
    • All states of the system should be reachable and usable while using the AT

Task Oriented Functional Tests

Description
Ensures that the component is able to handle expected input.

Protocol
Perform these tasks on the following sites.

Site
Demo

Test 1: Continuous Progress Animation

  • Procedure

    1. Open the browser and navigate to the specified URL

    2. Using the mouse, click the 'Submit' button

  • Expected Results

    • After clicking the "Submit" button, a progress bar should appear

    • The progress bar should gradually fill to 100%

    • As the progress bar fills, the percentage complete should be displayed

    • After the progress has reached 100%, it should gradually fade away

  • Stop Test

    • Refresh the browser to return the page to its initial state.

Test 2: Continuous Progress Animation

  • Procedure

    1. Open the browser and navigate to the specified URL

    2. Using the keyboard, tab to the the 'Submit' button and tap the "enter" key

  • Expected Results

    • After clicking the "Submit" button, a progress bar should appear

    • The progress bar should gradually fill to 100%

    • As the progress bar fills, the percentage complete should be displayed

    • After the progress has reached 100%, it should gradually fade away

  • Stop Test

    • Refresh the browser to return the page to its initial state.

Assistive Technology (AT)

Test 3: AT Tests

  • Procedure

    1. Open the browser and navigate to the specified URL

    2. Using the above tests (Test 1 - 2) as a guide, attempt to navigate through each state of the system

      1. Example ATs

        1. Screen Readers: JAWSNVDAVoiceOverOrca

        2. Built in AT features: WindowsMacLinuxiOSAndroid

        3. Others ATs: Speech Recognition, Screen Magnifiers, switch access, etc.