[152] in Tooltime
HelpDesk Application 1.0b3 testing
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Wed Jul 3 15:05:49 1996
Date: Wed, 3 Jul 1996 15:08:14 -0400
To: helpstaff@MIT.EDU, helpsummer@MIT.EDU, tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
----------------------------------------
Subject: Scopus 1.0b3 Testing
There are six parts to this email:
- Introduction
- Timetable
- Revisions since 1.0b2
- Things which haven't been fixed or other helpful hints
- Testing Remarks
- Testing Reply Form
----------------------------------------
INTRODUCTION
The purpose of this email is to prepare you for testing 1.0b3. This
version attempts to represent the functions needed for release 1.0. We
will continue to keep a list of items for release 2.0 and beyond.
There is a list of 50 prioritized issues that came out of a post 1.0b2
testing discussion. Not all of them will be addressed before version 1.0
gets released.
There will be a feedback session to address new items and issues found in
this release.
We have completed the items identified as critical or "easy fix". The list
of 50 items is available on the Web
http://web.mit.edu/tooltime/www/scopus_notebook.html/implementation.html
and in discuss menelaus:/usr/spool/discuss/tooltime transaction [142]
Accounts should be setup and software distributed. See Lynne if there are
any problems.
--------------------
TIMETABLE
* dates which effect students and staff
Wednesday July 3 - Wednesday July 10 *** NOON CUTOFF ***
Meeting to asses feedback, prioritize items to be fixed
open to all testers Wednesday July 10, 2:00 pm
(location TBA)
--------------------
REVISIONS SINCE 1.0B2
See
http://web.mit.edu/tooltime/www/scopus_notebook.html/implementation.html or
discuss menelaus:/usr/spool/discuss/tooltime transaction [151]
--------------------
THINGS WHICH HAVEN'T BEEN FIXED OR OTHER HELPFULL HINTS
- Automated thaw of frozen date has not been written
- Locks should work, with the exception, the Close under the File
pull down menu and the Window Close bar (that thing on the left
most corner of the Window) do NOT cause a locked record to be
unlocked. So, please use the Close or Clear buttons on the Window
to navigate.
- Training hints from the 1.0b2 release: use the % for wildcarding,
Use PF7 for date/time stamp in the History field
- Profile find has 18,7xx records from the warehouse, including students
and staff. There may be some differences in the appearance of information
between students and staff. For example, the phone numbers display
differently. Title and department for students also display different
than staff.
- 853 records have been copied from Filemaker into the Scopus/HelpDesk
application. You will notice formatting problems with the history
field. In addition, the Housecall and Netinstall screens are not
filled in, although there are main logs for this information. Records
from Filemaker have a log id number less than 60000, new records start
after 60000.
If you get errors saving one of the records from Filemaker, it's
most likely due to one of the fields (e.g. software) not matching
the list in the lookup table. Just pick a valid item from the
pull down list and continue.
--------------------
TESTING REMARKS (from Bryn)
- don't flame
If you really think something is "broken" in the database, explain why.
Well supported arguements get alot more support than comments like "This
sucks - it will make my life harder."
- explain problems clearly
If we don't understand your error, we won't be able to recreate it or fix
it. Or we may decide it's simply a training issue (ie. you didn't
understand how to use the function). So explain things clearly.
- make sure you understand what the questions are really asking
The first question is simply a "title" for your problem.
The second question asks you to rate how critical your problem is.
The third question asks what you expected to happen, or how it should work
once "fixed". It is not a request for database redesigns.
The fourth question asks you to explain the problem, what didn't work, what
you did.
The fifth question is justification for why we should fix your problem.
The sixth question is simply for anything we may have left out.
Good luck!
--------------------
TESTING REPLY FORM
Please submit any problems to tooltime-bugs@mit.edu in the following format:
1. What activitiy in the database didn't work? [in 10 words or less]
2. How critical is this function for the first release?
Rate on a scale of 1-5
1 = critical to the function of the helpdesk
3. How should the function work?
4. How did the function fail?
(how can we recreate it, too)
5. In what way would the lack of this function effect your work?
(constructive comments please - flaming will be ignored)
6. Comments
(if any)
