TEST PLAN DATE
TEST PLAN OVERVIEW
https://jira.ucdavis.edu:8444/jira/browse/SAK-132
Scope of testing
Primarily this test should be a regression test for provider functions; however, the code does not effect the usage of the 'Update Participants' button in Worksite Setup Tool. In fact, the code mimics it's usage. That is because the code mod's simply throttle the usage test should cover varification that
Purpose for this testing
Additional Items slated for testing
KNOWN ISSUES / PREVIOUS BUGS FIXED
- There is one known issue for this testing, related to the Home Page web content displayed for course sites. Currently, the Course Description information displays course title, which will be changed to description when the external data is mapped to a description field.
JIRAs that explain features to be tested in this plan
JIRAs that reference test scenarios described in this test plan
TEST ENVIRONMENT
- Hardware Setup
Server Type
Location
database
application
web server
- Note: The application does not need to be stopped for these tests to occur
- Software Setup
- Additional Setup Needed
- External-Banner Test Data to be Used As Representative Course Scenarios (see each test case)
DEPENDENCIES
ROLES AND RESPONSIBILITIES
COURSE SITE BATCHING DOCUMENTATION
JUNIT TEST RESULTS
TEST PLAN PROCESS
TEST CASES
Key for Test Case Scenarios
test 1
test 1 Testing
Description =
Category of Testing = unit, integration
Prerequisite Steps
Test Scenario
- Data to Be Used:
Scenario
Course
Roster Count
Instructor Kerb Name
Course Details (Catalog Root, Suffix, Section, Description)
Test Case Used In
File Associated
Test Cleanup
test 1 Test Results
Test |
User Role |
User Acting As |
Result |
Expected Result |
Pass/Fail |
|---|---|---|---|---|---|
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.