Page Comparison

...

These tests specifically address UCD Data Providers Testing listed under SAK-308: Upgrade providers and distauth code from 2.2 to work in 2.3313: Port course batching functionality (Course Batching, White List, Course Set Provider Id) from v2.1.x to v2.3.x or any other functionality that is dependent on the data provider process to be run before the tests can be performed.

...

• Course that are white listed can be created anytime regardless of enrollment
• Courses that are black listed are not automatically provisioned
• Batch provisioning generated a UCD-defined default toolset
• Ability to customize pages and tools aded when provisioning course sites
• Return of up-to-date provider information during provisioning

Per Scott's documentationThomas, setup required to run and test functionality includes:

• Batch admin account (e.g. ssbatchadmin)
• Programmers have access to testable sites (via SU tool, admin workspace)
• SU tool and Quartz tools are available in admin workspace/realm
• All login accounts that reference kerberos names can be "provided"
• External-Banner Test Data to be Used As Representative Course Scenarios (see each test case)Update of the white-list.txt file and valid Quartz tool run
• External-Banner test data defined and shared with QA tester prior to the test run
• A few test course sites need to be created in advance so that the batch job can modify these sites with a respective provider Id

Conduct these tests in multiple OS/browser combinations and note any issues in the Jira specified in the first column.
Under Test Plan, a star indicates that the test is ready for use. A blue star indicates that any user can perform this test; a yellow star means the test is limited to tester's with administrative user access onlyAll data provider tests require admin access and are designated with a yellow star .
These tests require coordination of new course generation from white list with Thomas. First whitelist run was completed on February 7, 2007.