Here are the most current testing scripts (revised Jan. 20).
Here is the latest version of the module delivery tasks document. It reflects recent milestones reached by WebCT support.
Here is the revised project task list. Items in yellow highlighting indicate tasks the team is currently working on or needs to consider next. Turquoise highlighting indicates CSH tasks to do in the next phase.
I want to make sure that we at the Center aren't missing any tasks that we should be doing, so I went through my task list and documented where I think things are and highlighted tasks that I think are on the critical path and remain to be done. This is the link below.
Here is a quick summary of key points. Please feel free to supply more information and correct me if necessary.
--The three test courses have been created in Vista 3, but there is still some functionality that isn't working yet and some bugs.
--CCE has created the registration sites for the test, but the feed from these sites to Vista 3 is not yet in place. Thus, I can register for a course, but I don't get access to it yet. This means that CSH can't test the whole system yet.
--Related to this last point-- I don't know if the WebCT folks have created a CSH entry page solution that avoids making CSH an institution.
--CSH just sent CCE the merchant account information (we finally got it last week), and CCE is working to install this information. CSH will test this functionality as soon as we learn that it is done.
--There are a few features in NCRS that don't appear to be fully working yet: the feature that allows CSH to charge separately for CMEs and the feature that allows university students and staff with current x.500 to register at the public registration site without needing to pay.
Here is the updated task list with the dates agreed to in the July 29 meeting. All critical path tasks have been highlighted in yellow.
This document is Louise's start at creating a scenario that CCE and WebCT can use to build the registration URL and test all the functionality.
What other data do we need to start a test case of functionality?