Versions Compared

Old Version 80

changes.mady.by.user Justin Obara

Saved on

compared with

New Version 81

changes.mady.by.user Justin Obara

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Assistive Technology (AT)

Test 15: AT Tests

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the above state tests (Test 1 - 14) as a guide, attempt to navigate through each state of the system
      1. Example ATs
        1. Screen Readers: JAWS, NVDA, VoiceOver, Orca
        2. Built in AT features: Windows, Mac, Linux, iOS, Android
        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 site.

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

Test 1: Edit With Letters

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Edit the text using only alphabetic characters (a - z, A-Z)
    4. 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
  • Stop Test
    • Refresh the browser to return the page to its initial state

Test 2: Edit With Numbers

...

  1. Open the browser and navigate to the specified URL
  2. Using the mouse, click the 'Edit' link
  3. Edit the text using only numbers (0-9)
  4. Using the mouse, click on the 'save' button

...

Description
Tests to ensure compatibility with Assistive Technologies.

Protocol
Perform these tasks on the following site.

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

Include Page
Assistive Technology (AT) QA Test Plan
Assistive Technology (AT) QA Test Plan

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

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Edit the text using only alphabetic characters (a - z, A-Z)
    4. 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
  • Stop Test
    • Refresh the browser to return the page to its initial state

Test 32: Edit With SymbolsNumbers

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' linkEdit the text using only punctuation and other such symbols (e.g. '/', '$' ' link
    3. Edit the text using only numbers (0-9)
    4. 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
  • Stop Test
    • Refresh the browser to return the page to its initial state

Test 43: Edit With Non-Standard Characters/ Symbols

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Edit the text using only non-standard characters and symbols (see examples here: http://www.alanwood.net/unicode/miscellaneous_symbols.htmlpunctuation and other such symbols (e.g. '/', '$' )
    4. 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
  • Stop Test
    • Refresh the browser to return the page to its initial state

Test 54: Edit With Special Non-Standard Characters/Symbols

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Attempt to edit the text by pasting in text containing special characters (e.g. new line, tabEdit the text using only non-standard characters and symbols (see examples here: http://www.alanwood.net/unicode/miscellaneous_symbols.html)
    4. 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
  • Stop Test
    • Refresh the browser to return the page to its initial state

Test 65: Edit With Special Characters Separated by Spaces

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Edit Attempt to edit the text by typing in some number of characters separated by tabs or spaces.pasting in text containing special characters (e.g. new line, tab)
    4. Using the mouse, click 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
  • Stop Test
    • Refresh the browser to return the page to its initial state

Test 76: Edit With Code/ScriptCharacters Separated by Spaces

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Attempt to edit Edit the text by pasting typing in some string of codenumber of characters separated by tabs or spaces.
    4. Using the mouse, click 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, without executing any of the codethe new value
  • Stop Test
    • Refresh the browser to return the page to its initial state

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/

...

    • to return the page to its initial state

Test 7: Edit With Code/Script

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' linkDelete all input values from the content
    3. areaAttempt to edit the text by pasting in some string of code
    4. 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 now read: "Click Edit"display the new value, without executing any of the code
  • Stop Test
    • Refresh the browser to return the page to its initial state

...

    • to its initial state

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

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Edit the text with a large number (e.g. 1000 characters) of characters without any gaps ( generator )Delete all input values from the content area
    4. 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, with the text wrapping to new lines as necessarynow read: "Click Edit"
  • Stop Test
    • Refresh the browser to return the page to its initial state

Test 32: Many Characters (Not Separated)

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Edit the text with a large number (e.g. 1000 characters) of characters with without any gaps between  ( generator )
    4. 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, with the text wrapping to new lines appropriatelyas necessary
  • Stop Test
    • Refresh the browser to return the page to its initial state
    Test

...

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

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. For each state of the system (see: State Tests), validate the HTML markup
      1. Tools for validation
        1. Nu HTML Checker Bookmarklet
  • Expected Results
    • All of the HTML markup should properly validate in all states.
  • Stop Test
    • Refresh the browser to return the page to its initial state
    • Quit the tool you are using to validate

Test 2: WCAG Validation

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. For each state of the system (see: State Tests), ensure that the WCAG guidelines are being met to at least AA level
      1. Tools for validation (Note: Automated tools are not yet capable of catching all issues. It is important to go through the checklist, making use of automated tools where possible, and manual processes otherwise).
        1. WCAG AODA accessibility audit checklist
        2. tota11y Bookmarklet
  • Expected Results
    • Passes WCAG 2.0 AA requirements
  • Stop Test
    • Refresh the browser to return the page to its initial state
      • Quit the tool you are using to validate
    • Refresh the browser to return the page to its initial state

Test 3: Many Characters (Separated)

  • Procedure
    1. Open the browser and navigate to the specified URL
    2. Using the mouse, click the 'Edit' link
    3. Edit the text with a large number (e.g. 1000 characters) of characters with gaps between ( generator )
    4. 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, with the text wrapping to new lines appropriately
  • Stop Test
    • Refresh the browser to return the page to its initial state

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/

Include Page
Validation QA Test Plan
Validation QA Test Plan

Ad-hoc

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

...