Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

results: Recorded in Jira https://jira.ucdavis.edu:8444/jira/browse/SAK-146, and is a part of White List Test https://jira.ucdavis.edu:8444/jira/browse/SAK-119

Provider Id Update Test Results
Would yield an example Summary Test Result of (both batch and manual updates):

...

results: Recorded in Jira https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/Batch+Course+Creation+Integration+Test+Results%2C+Sept+5%2C+2006

...

Case 4 #Site Functionality

Note
titleSite functionality

Description = Test the capability of the system to add sites with the correct pages, tools, tabs, and look and feel.

Category of Testing = unit, integration, functionality

Prerequisite Steps
Results Recording Steps summarized in:
**perform functionality test https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/Course+Site+Functionality+Tests%2C+SmartSite+Batch+Integration+Testing+Matrix for each site
looking for expected results
Test Scenario

Panel
borderColor#ccc
bgColorF7D6C1
titleBGColor#efefef
titleIndividual Functionality Tests
borderStyledashed
  • -Look and Feel- *
  • Pages *
  • Tools on each page *
  • Click-through on tools *
  • Order *
  • Tabs *

Test Cleanup

  1. Scott will remove all sites created in this step when all test cases are completed.

...

Jiras covered in this test case:
https://jira.ucdavis.edu:8444/jira/browse/SAK-121 = Tools and Pages
https://jira.ucdavis.edu:8444/jira/browse/SAK-23 = Tools configurable

...

Case 5 #Course Management Data Presented in Admin Tools

Note
titleCourse Management data present

Description = Test the course management content displayed in admin tools.

Category of Testing = unit, integration, functionality

Prerequisite Steps
Results Recording Steps summarized in:
**perform course management test https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/SmartSite+Course+Site%2C+Course+Management+Integration+Test+Matrix for each site
looking for expected results

Panel
borderColor#ccc
bgColorwhite
titleBGColorefefef
titleTest Scenario
borderStyledashed
  • Site navigation *
  • WorkSite Setup navigation *
  • Site Info tool *

Test Cleanup

  1. Scott will remove all sites created in this step when all test cases are completed.

...

Jiras covered in this test case:
https://jira.ucdavis.edu:8444/jira/browse/SAK-136 = Course Management Data (Description) details

#Full Batch Run on Term

Note
titleFull Batch Run

Description = Test the batch method for a whole term

Category of Testing = unit, integration, performance

Prerequisite Steps

  • After all tests have been run, Scott will recompile the Batch code to run for 2004 Winter
  • Scott will add the black list file that contains one CRN from Winter 2004 into the /var/sakai/ucd-data directory.
  • This test will run in the evening of test day
  • Scott and Thomas will analyze the Sakai internal db to check for errors in creation
  • Data to Use:

    Scenario

    Course

    Roster Count

    Instructor Kerb Name

    Course Details (Catalog Root, Suffix, Section, Description)

    Term Identifier

    Test Case Used In

    File Associated

    Valid Term

    Term with large number CRNs

    2004-01

    NA

    NA

    32573 sites

    Winter Quarter 2004

    Full Batch Run

    NA

    Valid CRN

    2004-01-40200,2004-01-42003

    NA

    NA

    NA

    NA

    White List

    black-list.txt

Test Cleanup

  1. Scott will ask Geeta to drop the devel schema when this test is completed.

results: Recorded in Jira https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/Batch+Course+Creation+Integration+Test+Results%2C+Sept+5%2C+2006

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

...

Recording Results

The test results will be recorded in Jira by QA testers. They can be of table form or text form.

Feedback Mechanism

The above results will be analyzed by the QA team, SmartSite programming team, and SmartSite management to determine the quality of code. Results of this test should be discussed as near to the Monday meetings as possibleand/or Code Migration meetings when available.