OSP System Test ScriptsNote: These scripts were originally written for testing OSP 2.4 and now need to be updated and/or validated for use with 2.5. If you are familiar with Confluence and OSP, please consider updating the script texts as you test the software. Before editing the scripts, please familiarize yourself with the Script Conventions. After you've updated/validated the script for 2.5, add a new row to the Script Information table indicating the revision/validation date as shown in the example below:
Full and partial snapshots of the OSP Confluence space (including the 2.4 scripts prior to revision are available for download and review).
Introduction to the Testing Activities and ScriptsOSP system testing is organized into Activities and Scripts. Each of the items below represents a user-centered Activity which is followed by the Script(s) listing the steps required to complete the activity. If you are testing using one of the servers in the public Sakai Test Instances then please make sure you sign up. You may also want to familiarize yourself with the Script Conventions, and possibly get ahead by downloading Testing Resources. |
Activity One: Test Preparation
This is the base activity for all system tests.- ST.Script.01.Access OSP — Open a browser and navigate to the appropriate URL.
- ST.Script.02.Verify access to Jira — It is important that all issues found during testing are logged in OSP Jira . This script ensures that the person testing is able to log in and create Jira issues, and knows where to document the test.
Activity Two: User and Site Preparation
In this activity, the System Administrator logs in and creates users, common interest groups (CIGs), and adds other preparatory data for subsequent tests. Once the test users have been created, they will be able to log in to the application.- ST.Script.01.Add Test Users — The system administrator creates the user accounts that will be required for the rest of the testing scripts.
- ST.Script.02.Add CIGs — The system administrator creates the common interest groups (CIGs) that will be required for the majority of the system tests.
- ST.Script.03.Add Maintainers — The Administrator adds appropriate test users as maintainers in appropriate sites.
Activity Three: Set up CIGs
The Portfolio Administrator, a CIG Coordinator or two, and others set up their respective CIGs and get them prepared for use. This activity should include setting up all the sites/CIGs necessary for testing.- ST.Script.01.Set-up Portfolio Admin CIG — The Portfolio Admin Site is used to manage global Forms, Glossaries, Layouts, Styles, Templates, etc. In this script, the portfolio program administrator logs in and configures the site. This involves setting up a global Glossary, Forms, Portfolio Templates, Layouts, Styles, and Reports. When completed, these global resources will be used in other CIGs in scripts that follow.
- ST.Script.02.Set-up portfolio site — The CIG Coordinator for the portfolio test site logs in, and sets up the Wizards, Matrices, Portfolio Templates, Glossary, etc. for the site.
- ST.Script.03.Set-up course site — The instructor for a course site with portfolio tools logs in, and configures the site with Wizards, Forms, Portfolios, etc.
- ST.Script.04.Set-up project site — The project leader for a project site with portfolio tools logs in, and configures the site with Wizards, Forms, Portfolios, etc.
- ST.Script.05.Add additional sites — This script is a freeform opportunity to create several of each type of site (portfolio, course, and project) with a tester-chosen selection of tools, permissions, and configuration.
- ST.Script.06.Set-up and use the goal management tools
- ST.Script.07.Set-up groups in project site — The project leader for a project site with portfolio tools logs in, configures the site with users, groups, and instructors, then exercises group filtering
Activity Four: Participant Collects Work
Multiple CIG Participants collect work in the sites that have been set up in previous activities. These scripts should include each of the three CIG Participants going through a number of collection-type activities such as: putting items into resources, removing items from resources, completing Forms, etc. In each of the sites which they are a member.- ST.Script.01.CollectWork.Add Files to Resources — The portfolio owner adds the files that will be required for the rest of the testing scripts.
- ST.Script.03.CollectWork.Complete the Form Item in Resources — The portfolio owner completes the forms that will be required for the rest of the testing scripts.
- ST.Script.04.CollectWork.Create a Folder — The portfolio owner creates a folder.
- ST.Script.05.CollectWork.Move Files to a Folder — The portfolio owner moves files to a folder.
- ST.Script.06.CollectWork.Move Files to Another Site — The portfolio owner moves files to another site.
- ST.Script.07.CollectWork.Copy Files to a Folder — The portfolio owner copies files to a folder.
- ST.Script.08.CollectWork.Copy Files to Another Site — The portfolio owner copies files to another site.
- ST.Script.09.CollectWork.Remove Files from Resources — The portfolio owner removes files from Resources.
Activity Five: Participant Uses Wizards
Each of the CIG Participants will use the various Wizards that have been set up in the test sites to collect content. This activity will exercise each type of Wizard (Sequential, Hierarchical, and Matrix) in each type of site (My Workspace, Portfolio, Course, Project). The scripts will involve starting wizards, stopping before they are complete, resuming previously started Wizards, submitting pages for Evaluation, reviewing after Evaluation, viewing Feedback from Reviewers, etc.- ST.Script.01.CIG Participants Add Files in Portfolio Site — CIG Participants log into Portfolio CIG and add files and reflection items to matrix cells and wizards
- ST.Script.02.CIG Participants Add Files to Wizards in Portfolio Site — CIG Participants add files and reflection item to wizard in a Portfolio CIG
- ST.Script.03.Students Add Files to Matrix in Course — Students log into Course CIG and add files and reflection items to matrix cells and wizards
- ST.Script.04.Students Add Files to Wizards in Course — Students add files and reflection item to wizard in a Course CIG
Activity Six: Participant Designs Portfolio
The CIG Coordinator creates portfolio template and CIG participant uses various methods to create, edit, and manage portfolios.- ST.Script.01.Add files to Resources — User should be able to add necessary files for a static portfolio
- ST.Script.02.Add a Form to be used in portfolio — User should be able to add a form that will be used in a portfolio
- ST.Script.03.Create a portfolio template — User should be able to create a portfolio template using the files that were added.
- ST.Script.04.Publish a portfolio template — User should be able to publish a portfolio template so that CIG Participants / Students can use it to create a static portfolio
- ST.Script.05.Export portfolio template — CIG Coordinator exports portfolio template
- ST.Script.06.Create a portfolio — User should be able to create a static portfolio
- ST.Script.07.Download offline copy of portfolio — User can download an 'offline' copy of portfolio for viewing on own computer.
- ST.Script.08.Create a free-form portfolio — User can create a free-form portfolio using portfolio layouts
Activity Seven: Reviewers Review Work
For this activity, the CIG Coordinator/Instructor logs in to be a Reviewer. S/he logs in, reviews work that has been shared through portfolios, and also work in-progress in a Portfolio Owner's Wizards.- ST.Script.01.Reviewer Reviews Student Work in Portfolio CIG — Reviewer logs in and reviews CIG Participant's submitted Matrices and Wizards in a portfolio site.
- ST.Script.02.Reviewer Reviews Matrices and Wizards in Course — Reviewer logs in and reviews student's submitted Matrices and Wizards in a course site.
Activity Eight: Evaluators Evaluate Work
Evaluator logs in and evaluates work from multiple portfolio owners. This set of scripts excercise all of the various review functions and the multiple ways of accessing them. In addition, this sequence of scripts requires multiple iterations between the Portfolio Owner and Evaluator.- ST.Script.01.Evaluator Grades CIG Participant's Work in Portfolio CIG — Evaluator logs in and grades CIG Participant's work in a portfolio CIG
- ST.Script.02.CIG Participants View Evaluations and Resubmit in Portfolio CIG — CIG Participants log in and view evaluations. Then, proceed to re-submit work.
- ST.Script.03.Evaluator Re-evaluates CIG Participant Work in Portfolio CIG — Evaluation logs in and re-evaluates CIG Participant's work
- ST.Script.04.CIG Participant Views Re-evaluation in Portfolio CIG — CIG Participant logs in and views re-evaluation.
- ST.Script.05.Evaluator Grades Student Work in Course — Evaluator logs in and grades student's work in a course CIG
- ST.Script.06.Students View Evaluations and Resubmit Work in Course
- ST.Script.07.Evaluator Re-evaluates Students Work in Course — Evaluation logs in and re-evaluates CIG Participant's work
- ST.Script.08.Student Views Re-evaluation in Course — Student logs in and views re-evaluation.
Activity Nine: Analyzing Reports
This sequence of test scripts exercises the reporting capabilities of OSP. Each of the various roles that may design and/or use reports is involved in this sequence.- Import Report Definitions — This sequence of test scripts exercises the ability to import report definitions into OSP Reports. Each of the various roles that may design and/or use reports is involved in this sequence.
- Setting Up Data Warehouse
System Test Variations
Variation One: Localization
Run through all system test activities with a set of resource bundles for a language other than English.Variation Two: OSP 2.0 Migration
Tests that exercise migrating from OSP 2.0 to OSP 2.1. The migration expectations defined are defined in [ARCHIVE:Design.General.Migration] and are the guideline for these scripts.Miscellaneous Scripts Miscellaneous Scripts
These are miscellaneous scripts that need to be placed somewhere in the sequence. They are already written but their placement in sequence is not yet clear.
- ST.Script.05.Importing Exporting a Wizard — User should be able to import and export a wizard
- ST.Script.07.Importing Exporting Form Definitions — User should be able to export and import a form definition from the Meta Object tool.
- ST.Script.08.Default Permissions — User should be able to verify and change the default permissions
- ST.Script.09.OSP Tool Navigation — User should be able to use the OSP Expand/Contract Tool Navigation