Versions Compared

Key

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

...

  • Additional Setup Needed
    **Batch admin account (e.g. ssbatchadmin)
    **QA admin account (e.g. QAadmin)
    **Testers have access to testable sites (via SU tool, admin workspace) All login accounts that use kerberos names can be "provided" by the system (e.g. UserDirectoryProvider implemented).
    **SU tool and Quartz tools are available in admin workspace/realm
    **All login accounts that reference kerberos names can be "provided"Testers have access to testable sites (via SU tool, admin workspace)
  • External-Banner Test Data to be Used As Representative Course Scenarios (see each test case)

...

The JUnit tests results are located on the server at:
isaac/var/sakai/ucd-data/course-batch-unit-tests-082006
or..
https://confluence.ucdavis.edu:8443/confluence/display/UCDSAKAI/Course+Batch+Creation+Unit+Test+Results
= All unit tests passed!!

...

TEST PLAN PROCESS

This Course Batching Unit/Integration QA Test Plan will be coordinated by Pat Kava, with assistance from the programming group (e.g. Scott Amerson), and will document the results of unit testing and integration testing for the batching process before handing off to QA. All tests must pass QA testing. It is assumed that all bugs have been documented by the programming group as issues before handing off to QA.

...

Info

*NOTE: The order of the test cases will be as follows.
White List Testing,
Black List Testing,
Provider Id Testing, and
Full Batch Run

  1. Site Functionality Testing, Course Management Testing, and Provider Id testing are each part of the White List testing scenario.
  2. In order to test the Black List functionality, we will need to have a superset of CRNs that are trying to be added at the same time. To accomplish this, we will use the White List scenario with a same CRN that is included in the Black List file. See Black List Test Scenario for more information.

...