ALEPH Service Pack Module Testing Teams
Circulation:   Nancy, Rick, Melissa
 
Circulation: Ed, Kathy, Tammy
 
Course Reserves: Rich, Becca, Alex
 
Cataloging/Items: Rita, Carolyn, Jill, Jenica
 
Acq/Serials: Sue, Tammy, Rita
 
CDC Reports: Jenica, Holly, Rudy, David
Schedule
March 5-9   Teams meet and discuss rep changes.  Sooner than later is better. Note that CDC Report testers do not need to meet to review the rep changes.  There do not appear to be any that should affect CDC reports.
March 6-12   Module assignment testing.  Sooner than later is better. Specific assignments and tasks within each module will be forth coming.
March 5???  DEV may be back up.  MH is off campus all day.  If DEV is up, SLD will test the repackaged client.  If it works, she will let you know it is OK to proceed.
 
Teams are expected to meet at least once to review the rep changes, and to identify pertinent module features that may change due to the service pack upgrade.  OK to invite MH to your team meeting if you think it would be helpful.
Service Pack rep changes are on HELIOS, Excel HTML spreadsheet sorted by module:
AUTOMATION\Documents\ALEPH\Upgrades\Service Packs\SP1851\SP1169 to 1851
Note that rep change descriptions are cryptic.  There is no additional documentation.  If team members have any questions, feel free to ask MH, but expect a big HUH? for some of them.  I have looked at many of the rep changes, but not all 682.  If it seems like the rep change is not pertinent to any of the features we currently use, OK to ignore it.  If it does seem to be pertinent, then plan to add testing tasks to your assignment to cover the new features.  Tip: Use the find feature of your browser to locate rep changes by keyword.
Focus of testing should be on module functions (e.g. check out an item, pay a fine, edit a bib record).  Testers should also make note of work flow changes within a module that may be necessitated by the upgrade.  Workflow and documentation changes should be coordinated with Team Leaders.
Exhaustive DATA testing should not be necessary, but testers should take a quick look at data in their assign module(s) for any unexpected or missing text.