System Test Scripts

OSP System Test Scripts

Note:  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:

Description Open a browser and navigate to the appropriate URL.
Role(s) List roles
Dependencies Start computer with Internet connection
Time required > 1
Updated/validated for 2.5 09/14/2007

Full and partial snapshots of the OSP Confluence space (including the 2.4 scripts prior to revision are available for download and review).

Description Link
XML Export (complete space) http://confluence.sakaiproject.org/confluence/OSP-20070913-13_05_26.zip
HTML Export (complete space) http://confluence.sakaiproject.org/confluence/OSP-20070913-12_55_46.zip
PDF Export (complete space) http://confluence.sakaiproject.org/confluence/OSP-20070913-12_43_51.pdf
HTML Export (system test scripts only) OSP-20070914-10_10_08.zip
PDF Export (system test scripts only) OSP-20070914-10_10_53.pdf

Introduction to the Testing Activities and Scripts

OSP 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.

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 UsersThe system administrator creates the user accounts that will be required for the rest of the testing scripts.
  • ST.Script.02.Add CIGsThe system administrator creates the common interest groups (CIGs) that will be required for the majority of the system tests.
  • ST.Script.03.Add MaintainersThe 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 CIGThe 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 siteThe 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 siteThe 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 siteThe 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 sitesThis 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 siteThe 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.

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.

Activity Six: Participant Designs Portfolio

The CIG Coordinator creates portfolio template and CIG participant uses various methods to create, edit, and manage portfolios.

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.

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.

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.

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.


Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.