Advanced Search - Condition Check - QA Test Plan

Test 1: Advanced Search Fields

• Actions:
  1. Create a new Condition Check record
  2. Fill in the following fields:
     1. Reference number
     2. Check/assessment date
     3. Object audit category
     4. Conservation treatment priority
     5. Next check/assessment date
     6. Condition description
  3. Enter textbook into the Condition Check Assessment Note field
  4. Save the record
  5. Print out the record to remember what you entered in each field
  6. Navigate to advanced search via the top menu bar item
  7. Select Condition Checks from the record type drop down
  8. Enter what you previously entered into the Object Audit Category field in the record into the Object Audit Category field in advanced search
  9. Click search
• Expected:
  • The Condition Check record you just created should appear in the search results

• Actions:
  1. Do this for each of the fields listed above
• Expected:
  • The Condition Check record you just created should appear in the search results

• Actions:
  1. Search the Edit Date field for today's date
• Expected:
  • The Condition Check record you just created should appear in the search results

• Actions:
  1. Search the Edit username field for your username (admin@core.collectionspace.org)
• Expected:
  • The Condition Check record you just created should appear in the search results

Test 2: Boolean Field-based Search

• Actions:
  1. Create a new Condition Check record
  2. Enter a Reference Number and write it down for reference
  3. Select Low from the Object audit category dropdown
  4. Select Needs no work from the Condition dropdown
  5. Write testtest in the Condition Check/Assessment Note field
  6. Save the record
  7. Create another new Condition Check record
  8. Enter a Reference Number and write it down for reference
  9. Select Low from the Object audit category dropdown
  10. Select Needs no work from the Condition dropdown
  11. Write testtest in the Display Recommendations field
  12. Save the record
  13. Create another new Condition Check record
  14. Enter a Reference Number and write it down for reference
  15. Select Low from the Object audit category dropdown
  16. Select In jeopardy from the Condition dropdown
  17. Write testtest in the Handling recommendations field
  18. Save the record
  19. Navigate to advanced search
  20. Select Condition Checks from the record type drop down menu
  21. Select Any from the boolean drop down menu
  22. Select Low from the Object audit category dropdown
  23. Select Needs no work from the Condition dropdown
  24. Click Search at the bottom of the page
• Expected:
  • All three new Condition Check records should appear in the results

• Actions:
  1. Navigate back to advanced search
  2. Choose Condition Checks from the record type drop down menu
  3. Select All from the boolean drop down menu
  4. Select Low from the Object audit category dropdown
  5. Select Needs no work from the Condition dropdown
  6. Click Search at the bottom of the page
• Expected:
  • Only the first two new Condition Check records created above should appear in the search results

Test 3: Boolean and Keyword Search

• Actions:
  1. Navigate to advanced search
  2. Select Condition Checks from the record type drop down menu
  3. In the keyword search field, write testtest
  4. Select Any from the boolean drop down menu
  5. Select Low from the Object audit category dropdown
  6. Select Needs no work from the Condition dropdown
  7. Click Search at the bottom of the page
• Expected:
  • All three new Condition Check records created in Test 2 should appear in the results

• Actions:
  1. Navigate back to advanced search
  2. Select Condition Checks from the record type drop down menu
  3. In the keyword search field, write testtest
  4. Select All from the boolean drop down menu
  5. Select Low from the Object audit category dropdown
  6. Select Needs no work from the Condition dropdown
  7. Click Search at the bottom of the page
• Expected:
  • Only the first two new Condition Check records created in Test 2 should appear in the search results

Test 4: Spend 3 minutes trying to break something!

• 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