Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/OT-test-report-V2-2-B3.txt Дата изменения: Wed Nov 22 15:32:05 2000 Дата индексирования: Sun Apr 13 22:54:08 2008 Кодировка: Поисковые слова: п п р р р р р р р р п п п п п п

These tests have been performed on wu0oh / SEGSRV user 52005.
------------------------------------------------------------

1/ HIGH: information messages ALWAYS displayed even if the "-debug"
option is NOT entered. And what is bad is that the entered password is
displayed in CLEAR !
==> item 1020

2/ HIGH: no way to see current release number of OT (should be displayed

in the title of the main OT box).
==> item 1021

3/ CRITICAL: call the DB browser. define a query with 5 columns, run it,

OK, OBs displayed with the 5 columns. But, Select 10 other columns, and
click again on the "query" button : OB list NOT refreshed (new columns
NOT displayed, in particular "instruments" and "templates" columns).
==> item 1022


4/ HIGH: inconsistencies between list of status given in the Queue View
(OBs> Mark) and via the DB browser ("status" button):
- the DB browser allows to choose among 17 status, the Queue View only
16 : the one which is missing is the status "Archived"
- the Queue View gives twice the same abbreviation to status "Partially
defined" and "Paused, during execution", i.e. "P" for both.
- status definitions are sometimes different between the Queue View and
the DB browser : "In prep" seems to correspond to "Partially defined";
"checked in" to "Defined after phase II". It will be better to have
exactly the same definition : the user is not always supposed to be an
OB life cycle expert.
==> item 1023 and 1039


5/ HIGH: DB browser: selection criteria : blank value exists for the
"instrument", "Sky tran", "Mode", "OB Type" and the "QC Grade" buttons,
and the "period" list. But this blank value is missing for the "OptElem"
and "Status" buttons. To set these 2 last buttons to "None" once a value
is already set, no way than "Clear" everything. This remark has already
been defined for P2PP.
==> item 1024


6/ HIGH: "Count" button for DB browser: counts all rows INCLUDING
DUPLICATES. It should ALSO be interesting to give an exact count of OBs
i.e. EXCLUDING duplicates : both figures may be interesting.
==> item 1025


7/ HIGH ? Queue View: it's possible to append OBs previously defined for
FORS2 to a UT1 queue : no warning message displayed as one can expect.
==> item 1026


8/ HIGH ? possible to change the telescope associated to a queue without
any warning message : may be dangerous ?
==> item 1027


9/ HIGH: "selection" button of the Rep browser : "Show queues" opens a
new box NOT displaying the queue actually associated to the current OB,
as it should (?).
==> Cancelled : the selected OB was NOT asssociated to any queue.


10/ CRITICAL: create a queue, save it, close it. Try to open it again in
the same OT session, via the OT>File>Open item : the existing queue is
NOT displayed, as it should (list of queues is empty) ==> impossible to
save a queue.
==> item 1028


11/ LOW: DB Browser box: a "Cancel" or "Close" button is missing.
==> Browsers can be closed with from the window manager, with
File->Close and with the Ctrl-W keybord shortcut, which is enough.


12/ CRITICAL: Following Java exception raised SEVERAL times after Rep
browser/Selection
Exception occurred during event dispatching:
java.lang.ClassCastException
at java.awt.EventQueue$EventQueueMulticaster.remove(Compiled Code)
at java.awt.EventQueue.removeEventQueueListener(Compiled Code)
at java.awt.LightweightDispatcher.stopListeningForOtherDrags(Compiled Code)
at java.awt.LightweightDispatcher.trackMouseEnterExit(Compiled Code)
at java.awt.LightweightDispatcher.processMouseEvent(Compiled Code)
at java.awt.LightweightDispatcher.dispatchEvent(Compiled Code)
at java.awt.Container.dispatchEventImpl(Compiled Code)
at java.awt.Window.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.EventDispatchThread.run(Compiled Code)
Then OT blocked, no way to properly exit (all opened windows blocked),
and same Java exception displayed once every minute approximately ==>
Ctrl-C.
==> item 1029



13/ HIGH : running OT, no new queue created or previous queue opened.
Several menu items should be in grey since there are not valid (or a
warning message should inform the user that they are not valid) : e.g.
File>Reload; File>Close; File>Save; File>SaveAs; File>Dump; File>Delete;
File>View; Edit>Clear; File>Rename)
==> item 1030 and 0884


14/ LOW: Services>CCS Setup : opens a new box to define CCS, but "OK"
and "Cancel" buttons are missing.
==> item 1031


15/ LOW: when creating a new queue, no way to know if the latest version
of the queue has already been saved or not : imagine something similar
to a WORD document: when some changes have been added since the last
save, the icon "SAVE" is set in black (instead of
grey).java.lang.ClassCastException. For P2PP, this feature is not
necessary since P2PP automatically saved each user change.
==> item 1032



16/ CRITICAL: very similar to previous remark 12/ DBbrowser/selection,
but Java exception name is different here.
Select different columns, query, redo it several times, then Java
exception raised (Problem on the DBB ?)
at
org.eso.ohs.gui.docview.DegreeAdaptor.fromMetaLevelObject(Compiled Code)
at
org.eso.ohs.ot.gui.RepositoryBrowserView$DbaseAngle.fromDatabaseData(Compiled Code)
at
org.eso.ohs.dbb.client.DbbDataTypeRenderer.getTableCellRendererComponent(Compiled Code)
at javax.swing.JTable.prepareRenderer(Compiled Code)
at javax.swing.plaf.basic.BasicTableUI.paintCell(Compiled Code)
at javax.swing.plaf.basic.BasicTableUI.paintRow(Compiled Code)
at javax.swing.plaf.basic.BasicTableUI.paint(Compiled Code)
at javax.swing.plaf.ComponentUI.update(Compiled Code)
at javax.swing.JComponent.paintComponent(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JViewport.paintViaBackingStore(Compiled Code)
at javax.swing.JViewport.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JLayeredPane.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at java.awt.Container.paint(Compiled Code)
at sun.awt.motif.MComponentPeer.handleEvent(Compiled Code)
at java.awt.Component.dispatchEventImpl(Compiled Code)
at java.awt.Container.dispatchEventImpl(Compiled Code)
at java.awt.Window.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.EventDispatchThread.run(Compiled Code)
java.lang.ClassCastException
at org.eso.ohs.dbb.client.Coordinate.fromDatabaseData(Compiled Code)
at org.eso.ohs.dbb.client.MoonDistance.fromDatabaseData(Compiled Code)
at org.eso.ohs.dbb.client.DbbDataTypeRenderer.getTableCellRendererComponent(Compiled Code)
at javax.swing.JTable.prepareRenderer(Compiled Code)
at javax.swing.plaf.basic.BasicTableUI.paintCell(Compiled Code)
at javax.swing.plaf.basic.BasicTableUI.paintRow(Compiled Code)
at javax.swing.plaf.basic.BasicTableUI.paint(Compiled Code)
at javax.swing.plaf.ComponentUI.update(Compiled Code)
at javax.swing.JComponent.paintComponent(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JViewport.paintViaBackingStore(Compiled Code)
at javax.swing.JViewport.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at javax.swing.JLayeredPane.paint(Compiled Code)
at javax.swing.JComponent.paintChildren(Compiled Code)
at javax.swing.JComponent.paint(Compiled Code)
at java.awt.Container.paint(Compiled Code)
at sun.awt.motif.MComponentPeer.handleEvent(Compiled Code)
at java.awt.Component.dispatchEventImpl(Compiled Code)
at java.awt.Container.dispatchEventImpl(Compiled Code)
at java.awt.Window.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.EventDispatchThread.run(Compiled Code)

==> item 1033



17/ LOW : DB browser. "Clear" button : clear the selected columns, the
selection criteria and the sorting criteria, but should also clear the
OB grid content ? Maybe confusing, especially if running a count just
after the clear : if all selected columns are cleared, the user doesn't
know anymore wat kind of objects he displays : basic rows (ie 1 row=1
template/1 Optelem) or OBs. Not so obvious since 1 OBs may have several
rows.
==> item 1034


18/ LOW Change request : I logged in using the account 52005 : it should
be displayed somewhere in the main OT box title.
==> item 1035


19/ LOW Change request : in order to be consistent with P2PP V2.2, the
File menu should also contain a "Login as ..." item : change username in
the same OT session.
==> item 1036


20/ CRITICAL: comparing OB definition between P2PP and OT :
- create a FORS2 OB with V2.2.1beta1 P2PP, save it. Check in it. save it as OBD file.
- create an OT queue containing this OB. Dump the queue into an OBD file.
- Compare the OT OBD and the P2PP OBD files.

Several differences:
- OBS.ID is 10237803 for OT; -96824299603 for P2PP.
- this OB contains 3 paramfiles which are correctly displayed in the
P2PP OBD file, but NOT IN THE OT OBD file : the value for INS.GBR.SETUP,
INS.TARG.SETUP and INS.FOCF.SETUP keywords is set to "NODEFAULT" on the
OT side ...
==> item 1037


21/ CRITICAL : when launching OT, no way to know the database server
which is accessed : the name of this DB server should be added in the
main box title (?) to be sure that we do NOT unvoluntarily access PROBS
...
==> item 1038


22/ LOW: To be consistent with the OB View refresh mode in P2PP (OB View
automatically refreshed when selected another OB), the DISPLAY button of
the OT QUEUE VIEW should display the content of the OB which is
currently selected in the OB grid of this Queue View. In fact, it would
be simpler if OB content is ALWAYS displayed in the Queue View ... (i.e.
the DISPLAY button should not be useful in that case).
==> item 1040


23/ HIGH: pb on sorting OBs via the OT DB browser : sort criteria not
applied ...
==> item 0748


24/ CRITICAL: the OT Queue View displays rows directly extracted from
the DB browser INSTEAD of displaying OBs only (i.e. if an OB contains 2
templates, it is displayed twice by the QV and, which is bad, treated as
2 separate OBs by OT).
Then, if the user saves the queue, a Java exception is raised (and an
error message "an error occured while writing the queue") because OT
tries to insert twice the same OB :

INSERT INTO schedules (sch_id, user_id, item_name, item_description,
item_start, item_duration, tel_code) VALUES
(102411,102411,'queue-KH10','',969040800,2764800,'UT1')
INSERT INTO schedule_items (sch_id, ob_id, sequence,
start_time,end_time) VALUES (102411,102357,0,0,0)
INSERT INTO schedule_items (sch_id, ob_id, sequence,
start_time,end_time) VALUES (102411,102356,1,0,0)
INSERT INTO schedule_items (sch_id, ob_id, sequence,
start_time,end_time) VALUES (102411,102356,2,0,0)
org.eso.ohs.persistence.ObjectIOException: Attempt to insert duplicate
key row in object 'schedule_items' with unique index 'pk_schedule_items'
at org.eso.ohs.dbase.DbaseStorageMgr.store(Compiled Code)
at org.eso.ohs.dbase.DbaseStorageMgr.update(Compiled Code)
at org.eso.ohs.persistence.ObjectManager.putBusObj(Compiled Code)
at org.eso.ohs.ot.gui.QueueViewManager.saveQueue(Compiled Code)
at org.eso.ohs.ot.gui.QueueViewManager$16.actionPerformed(Compiled Code)
at javax.swing.AbstractButton.fireActionPerformed(Compiled Code)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Compiled Code)
at javax.swing.DefaultButtonModel.fireActionPerformed(Compiled Code)
at javax.swing.DefaultButtonModel.setPressed(Compiled Code)
at javax.swing.AbstractButton.doClick(Compiled Code)
at javax.swing.plaf.basic.BasicMenuItemUI$MenuDragMouseHandler.menuDragMouseReleased(Compiled Code)
at javax.swing.JMenuItem.fireMenuDragMouseReleased(Compiled Code)
at javax.swing.JMenuItem.processMenuDragMouseEvent(Compiled Code)
at javax.swing.JMenuItem.processMouseEvent(Compiled Code)
at javax.swing.MenuSelectionManager.processMouseEvent(Compiled Code)
at javax.swing.plaf.basic.BasicMenuUI$MouseInputHandler.mouseReleased(Compiled Code)
at java.awt.AWTEventMulticaster.mouseReleased(Compiled Code)
at java.awt.Component.processMouseEvent(Compiled Code)
at java.awt.Component.processEvent(Compiled Code)
at java.awt.Container.processEvent(Compiled Code)
at java.awt.Component.dispatchEventImpl(Compiled Code)
at java.awt.Container.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.LightweightDispatcher.retargetMouseEvent(Compiled Code)
at java.awt.LightweightDispatcher.processMouseEvent(Compiled Code)
at java.awt.LightweightDispatcher.dispatchEvent(Compiled Code)
at java.awt.Container.dispatchEventImpl(Compiled Code)
at java.awt.Window.dispatchEventImpl(Compiled Code)
at java.awt.Component.dispatchEvent(Compiled Code)
at java.awt.EventDispatchThread.run(Compiled Code)
==> item 1041



25/ CRITICAL: it's possible to save 2 different queues with the same
name (but different content) : does not complain, when it can be
dangerous ....
==> item 1042


26/ HIGH: the Telescope selection list (Queue View) has NO effect ...
what is it supposed to do ?
==> item 1043


27/ HIGH ? Queue View OBs : it's possible to change the OB status into
any value. No check seems to be done, which is not so good for me:
possible to set the status to executed even if the OB (or the queue) has

not beeb fetched by BOB. It seems dangerous to me if the OT user can do
anything withour any warning message, isn't it ?
==> The OB life-cycle proposal was never formally accepted ...


28/ some functionalities are not yet implemented here :
- verify OB
==> item 0760

- Sort items by OB_ID
- Sort items by PROG_ID and OB_ID
==> item 0748

- print detailed area
==> item 0759





--
---------------------------------------
Karim HAGGOUCHI E-mail : khaggouc@eso.org
ESO - European Southern Observatory Phone : +49 89 32 00 65 07
Karl Schwarzschild Strasse, 2 Fax : +49 89 32 00 64 80
D-85748 Garching bei MЭnchen - Germany Room : 428