/
Inline Edit QA Test Plan - Rich Text

Inline Edit QA Test Plan - Rich Text

Jun 24, 2021

Inline Edit QA Test Plan - Rich Text

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
On This Page
Specification

QA Tests

ProtocolPerform 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.

Inline Edit Jira Filter

 

Unit Test

Protocol

 Launch the following website to execute unit tests.

Site
http://build.fluidproject.org/infusion/tests/component-tests/inlineEdit/html/InlineEdit-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 1-7 and 8-14 in order.

Site
http://build.fluidproject.org/infusion/tests/manual-tests/components/inlineEdit/rich/

Mouse

Test 1: Mouseover

  • Procedure

    1. Open the browser and navigate to the specified URL

    2. Using the mouse, hover over the 'Edit' link

  • Expected Results

    • A message saying "Use the Edit link to make changes." should appear

Test 2: Mouse, Enter Edit Mode

  • Procedure

    1. Complete Test 1

    2. Using the mouse, click the 'Edit' link

  • Expected Results

    • The content should now be in edit mode,

    • A rich-text editor should be open

    • The 'save' and 'cancel' buttons should be visible

    • The pointer should be an i-bar

Test 3: Mouse, Edit

  • Procedure

    1. Complete Test 2, leaving the content in edit mode

    2. Using the mouse, click in the content area to place the cursor in front of the first character

    3. Using the keyboard, tap the 'a' key

  • Expected Results

    • The content should remain in edit mode, with an 'a' at the beginning

Test 4: Mouse, Cancel

  • Procedure

    1. Complete Test 3, leaving the content in edit mode

    2. Using the mouse, click the cancel button

  • Expected Results

    • The content should have left edit mode

    • The rich-text editor should have closed

    • The 'save' and 'cancel' buttons should not be present

    • The content should not have saved the edit. The 'a', added in Test 3, should not be present.

Test 5: Mouse, New Edit

  • Procedure

    1. Complete Test 4

    2. Using the mouse, click the 'Edit' link

    3. Using the mouse, click in the content area to place the cursor in front of the first character

    4. Using the keyboard, tap the 'b' key

  • Expected Results

    • The content should be open in edit mode, with the rich-text editor, save button, and cancel button. There Should be no 'a' at the front of the content

    • The content should remain in edit mode, with a 'b' at the beginning

Test 6: Mouse, Save

  • Procedure

    1. Complete Test 5

    2. Using the mouse, click on the 'save' button

  • Expected Results

    • The content should have left edit mode

    • The rich-text editor should have closed

    • The 'save' and 'cancel' buttons should not be present

    • The content should display the new value. The 'b', added in Test 5, should still be present.