Skip to end of metadata
Go to start of metadata
Icon

This page has special characters in it:

  • Please edit only in Wiki Markup mode, and be careful when doing so.
  • If the special characters are displayed as question marks (?), an rtf document is attached to this page with the correct symbols. To see the attachment either use this link or in the top right corner of this page, click "Tools" -> "Attachments" and click the Specialchartestplan.rtf attachment.

Helpful Links:

Keyboard Accessibility under Mac:

  1. OS X limits keyboard access to only text boxes and lists, this can and should be changed when testing the keyboard accessibility.

    From within System Preferences -> Keyboard -> Keyboard Shortcuts tab there is a setting for allowing Full Keyboard Access. Default is "Text boxes and lists only" and this should be changed to "All Controls". Additionally, this can be enabled via keyboard shortcut: ctrl+F7

    (More info: http://abilitynet.wetpaint.com/page/Mac+OS+X+-+Enabling++keyboard+access+in+web+browsers)

  2. In at least some version(s) of Mac Safari, you must navigate to top-level tabs and secondary tabs via Option-Tab, rather than Tab.

  3. In at least some version(s) of Mac Chrome, you can navigate to top-level tabs and secondary tabs by enabling this option:

    In Settings -> Show advanced settings ... -> Web Content
    "Pressing Tab on a webpage highlights links, as well as form fields"

Relevant wiki pages:

UI Layer

Test 1: ASCII Special Characters in UI
  • Actions:
    1. Create a new cataloging record
    2. Add number in Identification Number field
    3. Variation A: In one single and one multiline text area, copy and paste "This sentence is wrapped in double quotes."
    4. Variation B: In one single and one multiline text area, copy and paste 'single quotes'
    5. Variation C: In one single and one multiline text area, copy and paste [square brackets]
    6. Variation D: In one single and one multiline text area, copy and paste {curly braces}
    7. Variation E: In one single and one multiline text area, copy and paste <angle brackets>
    8. Variation F: In one single and one multiline text area, copy and paste <!-- XML comment -->
    9. Variation H: In one single and one multiline text area, copy and paste "quoted" segment & ampersand
    10. Variation I: In one single and one multiline text area, copy and paste "A "quoted" segment; & (entity); wrapped in quotes"
    11. Variation J: In one single and one multiline text area, copy and paste backslashes and colon: \c:\mydocs
    12. Variation K: In one single and one multiline text area, copy and paste back-quote: Hawai`i
    13. Variation L: In one single and one multiline text area, copy and paste hash: #20
    14. Variation M: In one single and one multiline text area, copy and paste escaped slash: \/
    15. Save the record
  • Expected:
    • After the successful save message appears, all fields should contain the same value as you entered
Test 2: Strings of over 500 characters
  • Actions:
    1. Continue from Test 1 (or open an existing cataloging record)
    2. In at least one text area (multiline text field), type more than 500 characters
      example: I am typing in more than 500 characters of text to test whether the more than 500 characters are cut off or if they display correctly. 500 characters is a lot of text. I am typing in more than 500 characters of text to test whether the more than 500 characters are cut off or if they display correctly. 500 characters is a lot of text. I am typing in more than 500 characters of text to test whether the more than 500 characters are cut off or if they display correctly. 500 characters is a lot of text.
    3. Save the record
  • Expected:
    • After the successful save message appears, text area should contain the same characters as you entered and should not be cut off
Test 3: Non-ASCII Characters in UI
  • Actions:
    1. Continue from Test 2 (or open an existing cataloging record)
    2. In one single and one multiline text area, copy and paste: café
      Be sure characters paste as shown
    3. In one single and one multiline text area, copy and paste:
    4. Save the record
  • Expected:
    • After the successful save message appears, all fields should contain the same value as you entered
Test 4: ASCII Special Characters and Non-ASCII Characters in fields with autocomplete behavior
  • Actions:
    1. Continue from Test 3 (or open an existing cataloging record)
    2. In a repeating authority field, such as the Content->Person field in Cataloging, enter each of the following Person names, each in a separate instance of that repeating field:
  • Repeat these steps for each name above:
    1. Enter the Person name
    2. When prompted, add your newly-entered Person name to a vocabulary (such as "Local Persons" or "ULAN Persons")
    3. Click the "+" button to add a new Person field
  • When you are done, Save the Cataloging record.
  • Expected:
    • After saving you should expect to see the field still contains all of the names you entered (correctly encoded)
Test 5: Special Characters in Search
  • Actions:
    1. Continue from Test 4
    2. In the Search area in upper right, select Person from the Record Types list
    3. In the Search field, successively enter each of the authority names you previously entered in Test 4, one by one, and click Search:
  • Repeat this step for each name above:
    1. Enter the Person name
    2. Click the Search button
  • Expected:
    • The record containing that term should appear in the results
Test 9: Spend 3 minutes trying to break something and uncover bugs:
  • Spend a few minutes forcing the program to expose buggy behavior by:
    • using the system in ways not covered by the testplan
    • using the system in unexpected ways
    • doing whatever you can think of that will produce bugs and unexpected behavior.
    • Be creative!
    • feel free to extend this to behavior related to this testplan

Known bugs:

Loading
Key Summary P Assignee Status Updated
CSPACE-5788 User cannot search for terms including two question marks Major Unassigned Open Nov 06, 2014

  • No labels

1 Comment

  1. Test 1: After clicking on the Save button (top of form or bottom of form), the form 'goes white' and the progress indicator does not appear.  As a result, it is not clear what is happening, if anything. The record is being saved however, and a 'Record successfully saved message' appears after a short time.

    Test 3: Created new catalog record.  Entered the text string ñó? ä?çíì / / Huáy?; ?? Zh?ngwén ???????? Lech Wa??sa æøå in both the Title field and the Comments field.  Error message received: Error creating record: parseerror.  Click on OK button and the progress indicator starts up again but, the record is not saved, the progress indicator continues without any resolution.

    Also, as reported yesterday, relationships are not being saved for name authority records associated with catalog records.

    I did not have problems with jiras 3717 and 3849 listed above. Diacritics and double quotes when used in person authority search worked just fine.