Test Scenarios

From ReservesDirect: Open Source EReserves System

QA Guide edit QA toc (http://www.reservesdirect.org/wiki/index.php?title=Template:QA_toc&action=edit) QA guide Test Scenarios

Scenarios should be written entirely from the user's perspective. The title of the scenario should describe a specific task that the user is trying to accomplish, based on his or her role. Each scenario should consist of a specific set of steps needed to accomplish the task and the expected result of each step.

Table of contents

1 Student scenarios 1.1 New user logs into system or is created 1.2 Student views a class and opens readings 1.3 Student hides readings already viewed 2 Custodian scenarios 3 Proxy scenarios 4 Instructor scenarios 4.1 Create a new class for the current semester and reactivate another 4.2 Change a class's name and add a crosslisting 4.3 Add another instructor and a proxy 4.4 Populate the class with itesm: upload, link, fax, search 4.5 Add a heading and place items in it, then sort the item list 4.6 Change the date on an item, correct a mispelling in it, and add a note for students 4.7 Change the acitve and inactive dates on multiple items 4.8 Add a note to multiple items 4.9 Set multiple items active, then inactive 4.10 Delete several uneeded items from the class 4.11 Take several readings from the current class and copy theme into another class you are teaching 5 Staff scenarios 6 Admin scenarios

Student scenarios

For all of the following scenarios, log into the system as a student.

New user logs into system or is created

1. Log into the system with a user id that is not in use
2. System automatically creates an account and presents user with the "edit profile" page so that they can fill in their name and email address
3. Saving the profile page sends user to page where they can begin adding classes and viewing readings

OR

1. As a staff member, create a new user with a role of student.
2. User receives an email welcoming them to the system and giving them the URL to go to as well as their user name
3. User logs in and does steps 2-3 above

Student views a class and opens readings

1. Adds a class to your profile, looking class up by professor. Add another class, looking up by department
2. Go into class to view complete list of readings
3. Download the necessary helper applications from within the class to view the readings
4. Types of documents should be indicated on the screen
5. Choose a document and launch it
6. Electronic documents should launch their respective viewing applications
7. Physical items should provide a link to the full catalog record (if they are cataloged items and ILS integration is active). Physical items should also display the library where they are on reserve and a call number

Student hides readings already viewed

1. View a class list of readings
2. Select several readings and click on the link to hide them. The readings should disappear from the list
3. Show all the readings. The hidden ones should be indicated as hidden in some way and user should be capable of deselecting them to "unhide" them
4. Hide readings again. The readings selected for hiding should disappear again

Custodian scenarios

Proxy scenarios

Instructor scenarios

Create a new class for the current semester and reactivate another

Change a class's name and add a crosslisting

Add another instructor and a proxy

Populate the class with itesm: upload, link, fax, search

Add a heading and place items in it, then sort the item list

Change the date on an item, correct a mispelling in it, and add a note for students

Change the acitve and inactive dates on multiple items

Add a note to multiple items

Set multiple items active, then inactive

Delete several uneeded items from the class

Take several readings from the current class and copy theme into another class you are teaching

Staff scenarios

Admin scenarios