TEST PLAN OVERVIEW

Scope of testing

JIRA references

UCD Jira keys: SAK-135 (SAK-153 SAK-181 SAK-156)
Sakai Foundation Jira keys: REQ-2, REQ-76, SAK-5444

Purpose for this testing

Test final grade downloading to (aka, direct submission to) the final grading tool.

This test plan covers the opration of downloading course final grades from Gradebook to the UDC Final Grading Tool using the configuration planned for Smartsite production.
This test does not cover full testing of confurable aspects of the underlying coded changes to gradebook. More comprehensive testing will be in a forthcoming test plan.

Additional Items slated for testing

TEST ENVIRONMENT

  • Hardware Setup

  1. Note: The application does not need to be stopped for these tests to occur

  • Software Setup
    Sites must have enrollments for the grade submission to be enabled.

  • Additional Setup Needed
    Tested knames that must be su'd in MyUCDavis should be su'd before the test begins for grade submission.

  • External-Banner Test Data to be Used As Representative Course Scenarios (see each test case)

DEPENDENCIES

Courses with merged CRN's will cause data to be added to the grade files that the Final Grading Tool will find to have inconsistent CRN information: submitted files will reach the UCD Final Grade Submission tool, but will contain errors.

ROLES AND RESPONSIBILITIES

Courses that were used to pilot gradebook during Summer session of 2006 should have 'real' grade numbers for assignements and so bogus test data may not be neceessary:

FNP/PA

FAP 300A SU06
FAP 331A SU06

Testers will need to SU on MyUCD and on Smartsite when not Instructors of Record for the courses used for the test.

Unit test and first level integration test results

TEST PLAN PROCESS

(See 'TEST CASES')

TEST CASES

Test Case Scenarios

  • test 1: Courese Grade Direct submission to Final Grade Tool

  • test 2: Grading modes [postponed]

test 1

Description = Course Grade Direct submission to Final Grade Tool

Category of Testing = integration, functional

Prerequisite Steps

  1. Course site must be available with the gradebook added in one of the tool pages.

  2. The site must have enrollments (site members that are 'students' or with 'access' role.

Test Scenario

General test instructions

  1. MyUCDavis (skip to login to Sakai if no su required)

    1. login to my.ucdavis.edu (note that MyUCD SU propagates to ips.ucdavis.edu from my.ucdsavis.edu)

    2. select admin tool icon

    3. select SU Tool

    4. search for user (eg, Virginia Haas)

    5. select user

    6. open a new browser window

  2. Sakai (http://littlejohn.ucdavis.edu)

    1. click login

    2. enter kname of tester (skip to 'select tab for site' if SU Tool not required)

    3. select Administration Workspace Tab

    4. select SU tool

    5. enter SU-target kname

    6. select tab for site (eg, FAP 300A SU06)

    7. select Gradebook page

      1. Course Grades

        1. Click on the words 'Course Grade' at the bottom of the list of Assignments (if any)

        2. click on Button with label 'Send Grade to UCD Final Submission Tool'

      2. Roster Grades

        1. Click on word 'Roster' in Menu Bar of Gradebook frame

        2. Click 'Export Excel' and/or 'Export CSV' button(s)

Exprected outcome
2.7.1 = Course Grades: SS iFrame (the Gradebook Tool frame) is replaced with the Final Grade Submission Tool and there are no exceptional errors.
2.7.2 = Roster Grades: File contains Assignments grades, one per column, after the student and course data:

test configuration

student_name,export_student_id,course_or_roster,assignments configuration order results in roster download having assignments being listed after their cumulative score ....

this will Likely have to change for production

Test Cleanup
None

Recording Results

The test results will be recorded in the above summary tables by integration testers, and a summary of this data will be ready for QA and the Sakai Development team to review.

Feedback Mechanism

The above results will be analyzed by the SmartSite programming team, and management to determine the steps needed and whether or not to hand off to QA. Results of this test should be discussed as near to the Monday meetings as possible.