Inline Edit QA Test Plan - Rich Text

Environments
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


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

Test 2: Mouse, Enter Edit Mode

Test 3: Mouse, Edit

Test 4: Mouse, Cancel

Test 5: Mouse, New Edit

Test 6: Mouse, Save

Test 7: Verify Edit

Keyboard

Test 8: Keyboard, Enter Edit Mode

Test 10: Keyboard, Edit

Test 11: Keyboard, Cancel

Test 12: Keyboard, New Edit

Test 13: Keyboard, Save

Test 14: Keyboard, Verify Edit

Assistive Technology (AT)

Test 15: AT Tests

Task Oriented Functional Tests

Description

 Ensures that the component is able to handle expected input.

Protocol

 Perform these tasks on the following site.

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

Test 1: Edit With Letters

Test 2: Edit With Numbers

Test 3: Edit With Symbols

Test 4: Edit With Non-Standard Characters/Symbols

Test 5: Edit With Special Characters

Test 6: Edit With Characters Separated by Spaces

Test 7: Edit With Code/Script

Boundary Tests

Description

 Ensures proper functionality at the input limits 

Protocol

 Perform these tasks on the following site.

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

Test 1: Empty

Test 2: Many Characters (Not Separated)

Test 3: Many Characters (Separated)

Test-to-Fail

Description

 Tests which should cause errors or not be accepted as input

Protocol

 Perform these tasks on the following site.

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


*no tests yet*

Validation

Description
Tests to ensure that specifications are being met

Protocol
Perform these tasks on the following site.

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

Test 1: HTML Validation

Test 2: WCAG Validation

Ad-hoc

Description
Improvised tests for quickly discovering critical issues, and uncovering ones that may be outside of formalized testing.

Protocol
Attempt to use the tool in various situations, using your imagination and freedom to explore the interface and interactions.

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