P2PP V2.4 Integration Test Plan

Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/P2PP-test-plan-V2-4.html
Дата изменения: Fri Jun 21 19:28:21 2002
Дата индексирования: Sun Apr 13 22:57:35 2008
Кодировка:
Поисковые слова: http www.astronomy.ru forum index.php topic 4644.0.html

DFS Group Home Page
P2PP V2.4 Integration Test Plan

HOME

INDEX

HELP

NEWS

standard testcases
specific testcases

Standard testcases

The following testcases correspond to the minimum set of tests to be run on every new P2PP release. They are not specific to a given release, but are to give some confidence about the fact that all basic functionalities of P2PP work fine, in nominal situations only. This means that all possible tricky or error situations, stress and performances tests as described in the complete P2PP Integration Test Plan are not verified since this is supposed to have been done with a previous testing session (for instance, all query and sorting criteria of the DB browser will not be re-verified here). Usually, a testing session starts first by running the standard testcases.
All standard testcases are run with the debug mode, and debug messages are checked.

1/ START P2PP

*Testcase number*	*Detailed description*	*Expected result*
1.1/	- run in debug mode - check the initial debug messages about the configuration tool (which DB is accessed, which VLT CCS, JRE, external libraries/versions are used, which DB is accessed, path to the cache, impex, IPs, config reports, ...) - verify this against the config files which are under the .../config/ directory, and against the .p2pp.cf if any.	- no error - expected versions
1.2/	- verify the layout: check every menu content (contain expected items ?, any strange layout ?)	- expected layout
1.3/	- run the tool as super-user, run some queries.	- no error
1.4/	- quit, and re-start P2PP. - during the same session, re-login using different users, and check the lockinfo files under the cache directory.	- no error
1.5/	Backward compatibility: - re-start P2PP reading a cache created with a previous P2PP version.	- no error

2/ MANIPULATION OF FOLDERS

*Testcase number*	*Detailed description*	*Expected result*
2.1/	- create a new folder	- folder created
2.2/	- open a folder	- folder opened
2.3/	- rename a folder	- folder renamed
2.4/	- move a folder	- folder moved to another place
2.5/	- delete a folder	- folder deleted (if not an obs run folder)

3/ MANIPULATION OF OBs

*Testcase number*	*Detailed description*	*Expected result*
3.1/	- create an OB (science FORS2 OB) - note on some paper the OB description	- OB created with no error
3.2/	- quit and re-start P2PP - view previous 3.1/ OB (science FORS2 OB) - compare the View content against the paper	- previous OB viewable with original content
3.3/	- duplicate an OB and compare the duplicated one with original OB (science FORS2 OB)	- OB duplicated - original and duplicated OBs have same content
3.4/	- move an OB to another folder (science FORS2 OB) - check its content is the same.	- OB moved to destination, removed from source
3.5/	- verify an OB (science FORS2 OB) without any installed EVM.	- Verify box displayed with expected content
3.6/	- delete an OB (science FORS2 OB)	- OB deleted
3.7/	- same as 3.1/ to 3.6 for a calibration FORS2 OB.	- no error
3.8/	Backward compatibility: - run a previous version of P2PP reading a cache only created with such version. - Select an OB. Note somewhere all his templates, associated values, TP, CS values, ... - Quit, start the new current P2PP version reading the previous cache. - Check the OB content has not changed.	- OB read with latest P2PP version does not differ from the one created with previous version

4/ IMPORT/EXPORT

*Testcase number*	*Detailed description*	*Expected result*
4.1/	- export a science FORS2 OB, compare the *.obx content with the View	- no error
4.2/	- rename the exported OB, and import it. Check the View with the original OB View	- no error
4.3/	- export the OB imported in 4.2/. Compare the 2 *.obx (only the OB name should be different).	- no error
4.4/	- repeat 4.1/ to 4.3/ with a Calibration OB.	- no error
4.5/	Backward compatibility: - read (with the new version) a cache created with a previous version. Select an OB. Export it. Compare the new OBX with the OBX generated with previous P2PP version.	- no difference (expect the Strehl ratio)
4.6/	Backward compatibility: - run the new version of P2PP. Import an OB created and exported with the previous version. - compare its content with previous one. - export it with the new P2PP version, compare the original OBX and this last one.	- no difference (expect the Strehl ratio)

5/ SYNCHRONIZATION (Copy done from the OB View)

*Testcase number*	*Detailed description*	*Expected result*
5.1/	- Copy/Paste the OD	- pasted OD equal to the original one
5.2/	- Copy/Paste the AT	- pasted AT equal to the original one
5.3/	- Copy/Paste the TP	- pasted TP equal to the original one
5.4/	- Copy/Paste the CS	- pasted CS equal to the original one
5.5/	- Copy/Paste the OD for a Calib OB	- pasted OD equal to the original one

6/ VERIFY

*Testcase number*	*Detailed description*	*Expected result*
6.1/	- run the Verify on one Science FORS2 OB with no EVMs installed: check any error/debug message, verify the content of the Verification log box.	- Verify box is displayed
6.2/	- same as 6.1/ with a Calibration OB.	- Verify box is displayed
6.3/	- same as 6.1/ and 6.2/ with some recent EVMs.	- Verify box is displayed and it mentions EVMs are applied

7/ CHECK-IN/CHECK OUT

*Testcase number*	*Detailed description*	*Expected result*
7.1/	- export a science FORS2 OB.	- OBX created
7.2/	- check it in (directly accessing the DB, not via an AppServer).	- the OB gets an ID - status changed to D - field values displayed in grey, and not modifiable, in OB View
7.3/	- run the DBB, select it, and check it out.	- OB visible in DBB - OB View from DBB displays same content as the main OB View
7.4/	- rename the OB, export it again, and compare the 2 *.obx (only the OB name should differ).	- no difference between the OBX files
7.5/	Backward compatibility: - run the previous version of P2PP. Check-in an OB. Quit. Note somewhere its content. - run the new version of P2PP. Check-out the OB previously checked-in. Verify its content via the View box. - apply a modification on some AT value, and TP, TI and CS values. Check-in the OB. - via the DBB, verify the new content. - check it out again and verify its content via the View box.	- new OB has same content as original OB - modifications appear - modifications appear

8/ PARAMFILES

*Testcase number*	*Detailed description*	*Expected result*
8.1/	- using uptodate paramfiles, create an OB attaching paramfiles.	- no error
8.2/	- In particular, attach a paramfile containing coordinates	- the CS coordinates are updated accordingly.
8.3/	- modify the coordinates in the CS, and reload the p_targ paramfile: coordinates extracted again from the paramfile.	- the CS coordinates refreshed with values coming from the p_targ file

9/ REPORTS

*Testcase number*	*Detailed description*	*Expected result*
9.1/	- Execution Time report on several OBs: generate it, verify its content, print it.	- no error
9.2/	- ObsBreakdown report on one OB: generate it, verify its content, print it.	- no error
9.3/	- Verify report on several OBs: generate it, verify its content, print it.	- no error
9.4/	- Display in OBD format on one OB: generate it, verify its content, print it.	- no error
9.5/	- backward compatibility: run a previous version of P2PP. Select an OB, generate all types of reports. Run the new current version, and select same OB, generates same reports, check any difference between old and new reports.	- no error

10/ INTERFACE WITH BOB

*Testcase number*	*Detailed description*	*Expected result*
10.1/	- fetch an OB from BOB	- no error
10.2/	- load some OBD files from BOB	- no error

top of the page

Specific testcases

The following testcases correspond to the set of tests to be run on this specific P2PP release. In principle, here, every item mentioned in the Release Note is verified, in the nominal situation, and as far as it is possible, error situations as well.
Unless explicitely mentioned, all following specific testcases are run with the debug mode, and debug messages are checked.

11/ Release note item 1766:
SPR DFS001031: import fails when OBSERVATION.DESCRIPTION.NAME is empty

*Testcase number*	*Detailed description*	*Expected result*
11.1/	- create an OB - clear the OBSERVATION.DESCRIPTION.NAME field - export the OB - import it again	- no "reading/writing data" error message
11.2/	- create an OB - enter a quite complex name for the OBSERVATION.DESCRIPTION.NAME field, mixing alphabetical, numerical, and special characters - export the OB - import it again	- the value displayed in the *.obx files is the one entered by hand. - after import, the value displayed in the View box is also the original one.
11.3/	- repeat 11.2/ until the maximum allowed of the OBSERVATION.DESCRIPTION.NAME field is reached	- error message if the size of OBSERVATION.DESCRIPTION.NAME exceeds the maximum limit.
11.4/	- repeat 11.1/ and 11.2/ but with the 'OB name' field.	- same as 11.1/ and 11.2/
11.5/	- repeat 11.1/ and 11.2/ but with the 'TP name' field.	- same as 11.1/ and 11.2/
11.6/	- repeat 11.1/ but with other TP fields: * 'Equinox' * 'Epoch' * 'proper motion RA' * 'proper motion DEC' * 'diff RA' * 'diff RA'	- same as 11.1/
11.7/	- repeat 11.1/ and 11.2/ but with the 'CS name' field.	- same as 11.1/ and 11.2/
11.8/	- repeat 11.1/ but with other CS fields: * 'Seeing' * 'Airmass' * 'Lunar illumination' * 'Moon angular distance'	- same as 11.1/

12/ Release note items 1515, 1492:
Violated constraint when trying to check-out an OB already belonging to a queue.

*Testcase number*	*Detailed description*	*Expected result*
12.1/	- check-in an OB	- Status is "D" in the P2PP OB View and in the P2PP DBB.
12.2/	- via the new OT 2.4, select an OB whose status is not "D". Set the status to "D".	- status gets updated in the P2PP OB View and in the P2PP DBB.
12.3/	- via the new OT 2.4, select an OB whose status is not "-". Set the status to "-".	- status gets updated in the P2PP OB View and in the P2PP DBB.
12.4/	- check-out an OB whose status is "D" and attached to a queue.	- no more any "violation constraint" error message, but a more meaningful one (such as 'OB belongs to a queue' - check-out not performed
12.5/	- check-out an OB whose status is "-" and attached to a queue.	- no more any "violation constraint" error message, but a more meaningful one (such as 'OB belongs to a queue' - check-out not performed

13/ Release note item ???:
Support NAOS/CONICA.

*Testcase number*	*Detailed description*	*Expected result*
13.1/	- create someNAOS science and calibration OBs - verify it - export it - rename it, import it, compare the original and the exported *.obx - check-in, check-out, verify the OB View and the DBB content - generate reports about	- strehl ratio constraint displayed in the OB View, and in the DBB grid (?) - no error or debug message
13.2/	- same as 13.1/ attaching files provided by the NAOS Preparation Software tool	- no error or debug message
13.3/	- test on HP 11.0 (on wu0dhs) only: run the "standard P2PP tests" having the NAOS Preparation Software tool running in parallel. Check the top command, and the 'Glance' tool	- no performance problem detected

14/ Release note item ???: ==> cancelled
AppServer should use port 80 or a proxy.

*Testcase number*	*Detailed description*	*Expected result*
14.1/

15/ Release note item ???: ==> Cancelled
P2PP allows to check-in OBs whose obs run is not in DB while it should not.

*Testcase number*	*Detailed description*	*Expected result*
15.1/	- retrieving an old cache, try to check-in an OB whose Obs Run is not in DB.	- check-in not allowed - appropriate error message

16/ Release note item 1064
Do not display separate comment areas for Observation Block, Target
and Constraint Set; instead, only the Observation Block area would be
used.

*Testcase number*	*Detailed description*	*Expected result*
16.1/	- create a new OB with comments. - verify - export - import the same *.obx - check-in the OB	- no separate comment areas in the OB View (on the User comments) - no error or debug message - no separate comment areas in the *.obx file - no separate comment areas in the OB View - OB checked-in
16.2/	- duplicate the OB, export it. Compare last *.obx with original	- OB duplicated, no difference between the last *.obx and the original one.
16.3/	- synchronize the TP	- no error (previously the TP comment was synchronized, as well)
16.4/	- synchronize the CS	- no error (previously the CS comment was synchronized, as well)
16.5/	- save as OBD file - load the OBD file via BOB - fetch the OB via BOB	- no separate comment areas in the OBD file - OBD file loaded without error - OB fetched without error
16.6/	- generate an ObsBlock breakdown report	- no separate comment areas in the report (on the User comments)
16.7/	- same as 16.1/ to 16.6/ with a Calib OB

17/ Release note item : ==> cancelled

*Testcase number*	*Detailed description*	*Expected result*
17.1/

18/ Release note item 1763:
Time intervals end date set to 'now', while it should remain to the 2038 year.

*Testcase number*	*Detailed description*	*Expected result*
18.1/	- Time intervals: click into the start or end field	- does not lead anymore to an update of the right field (=end_interval) to the current date.

19/ Release note item 1332:
Shift-click (to complete selection) causes an exception.

*Testcase number*	*Detailed description*	*Expected result*
19.1/	- select several OBs. - Without clicking the grid, move the mouse pointer to the scroll bar. - Move the scrollbar to the down most position. - press shift and select the last OB in the grid, so that all between the first and the last are selected	- no IndexOutOfBoundsException Java exception

20/ Release note item 1408, 1536:
Download->XXXTargets should work with multiply selected OBs.

*Testcase number*	*Detailed description*	*Expected result*
20.1/		-"Download" in Download Phase 1 Targets is renamed to "Duplicate OB", with the submenus "with selected Targets" and "with all Targets".
20.2/	- select Duplicate OB detect if the user has more than one OB selected in P2PP	- an option message saying that 'only the first OB in the list will be duplicated and Synchronize should be a used if the user wants to paste a target into multiple OBs' is displayed.

21/ Release note item 0919:
support for FLAMES.

*Testcase number*	*Detailed description*	*Expected result*
21.1/	- export an OB - save as OBD - fetch from BOB	- OBS.EXECTIME is re-introduced

22/ Release note item 1197,1749:
Introduced new "Strehl ratio" constraint for NACO in the Constraint Set panel.

*Testcase number*	*Detailed description*	*Expected result*
22.1/	- create a NACO OB. Verify, check-in, check-out. - export the OB	- "Strehl ratio" constraint for NACO in the Constraint Set panel. - The SIM.PERF.MINSR keyword will be recognised when attaching a PS file to a NACO Acquisition Template, and it will be used to update the Constraint Set -- much like TEL.TARG.ALPHA, etc. for the Target

23/ Release note item 1195:
Full validation of OBs through P2PP AppServer.

*Testcase number*	*Detailed description*	*Expected result*
23.1/	- run P2PP in Service Mode (connected to the P2PP Application Server)	- a new menu item File->ExternalVerification is displayed. - The corresponding menu option executes Stage2 verification without the need for the user having EVMs loaded in their instrument directory. - The Verify menu option and button still are accessible to do Stage1 verification. - External verification is also performed before any OBs are checked into the repository.

top of the page

24/ Release note item :
Font size is now configurable.

*Testcase number*	*Detailed description*	*Expected result*
24.1/	- edit the site.cf or ~/.p2pp.cf. - take any integer value between -4 and 4, to increase or decrease font sizes, and re-start P2PP.	- the optional keyword FONT.OFFSET.SIZE is added to site.cf or ~/.ot.cf. The displayed font size is the expected one.
24.2/	- change font size while P2PP is running	- no impact, since the config file is read only at start-up
24.3/	- specify values out of range	- no impact. The default one is considered.
24/4	- introduce an error (missing ")	- error message

25/ Release note item 1655:
Added standard [clear] option to multiple selection pulldown menus.

*Testcase number*	*Detailed description*	*Expected result*
25.1/	- check that a standard [clear] option is added to ANY multiple selection pulldown menus in the Repository Browser, which deselects all currently selected options. - use it	- all currently selected options are deselected. - - the current Ctrl-Click unctionality remains available, to select/deselect individual options.

26/ Release note item 0930:
New horizontal scrollbar for the templates grid in the details view.

*Testcase number*	*Detailed description*	*Expected result*
26.1/		- New horizontal scrollbar for the templates grid in the details view. - The switch from auto-resizing columns to scrollbar takes place when grid has more than 6 columns

27/ Release note item 1418:
Operations Mode: New confirmation dialog for Save action.

*Testcase number*	*Detailed description*	*Expected result*
27.1/	-	- Operations Mode: New confirmation dialog for Save action.

28/ Release note item 1568:
Improved error message when an instrument is no available to server: it was "the server is busy or unavailable".

*Testcase number*	*Detailed description*	*Expected result*
28.1/	-	- Improved error message when an instrument is no available to server: it was "the server is busy or unavailable".

29/ Release note item 1634:
Eliminated hard-coded port numbers for the Application Server. Added APPSERVER.PORT and APPSERVER.DATAPORT to config/site.cf (for ESO internal use only).

*Testcase number*	*Detailed description*	*Expected result*
29.1/	-	- Eliminated hard-coded port numbers for the Application Server. - Added APPSERVER.PORT and APPSERVER.DATAPORT to config/site.cf (for ESO internal use only).

30/ Release note item 0388:
Solved "double CCS server" problem: if a CCS server called "schedule" is already defined, a second P2PP process with that name will not be allowed to run.

*Testcase number*	*Detailed description*	*Expected result*
30.1/	-run P2PP while while a CCS server called schedule is already defined.	- error message - P2PP does not start

31/ Release note item 1672:
DBB: select a column by clicking on the widget itself.

*Testcase number*	*Detailed description*	*Expected result*
31.1/	- In the Repository Browser, select a column by clicking on the widget itself.	- no way to select a column when clicking on a much larger area.

32/ Release note item 1650, 0876:
Browser column width calculation is reviewed.

*Testcase number*	*Detailed description*	*Expected result*
32.1/	-	- Browser column width calculation is reviewed; some columns should have a more reasonable size.

33/ Release note item 1729:
Improved performance of some EVMs.

*Testcase number*	*Detailed description*	*Expected result*
33.1/	-	- Improved performance of some EVMs

34/ Release note item 1727:
Fixed bug: EVMs would not run if instruments directory was redefined in ~/.p2pp.cf.

*Testcase number*	*Detailed description*	*Expected result*
34.1/	- run P2PP if no instruments dir is available (but defined in the .p2pp.cf) - run P2PP if no instruments dir is specified in the .p2pp.cf - run EVMs if instruments dir is redefined in ~/.p2pp.cf	- Verify reports EVM messages

35/ Release note item 1765:
Fixed bug: definitions found in configuration file in home directory ($HOME/.p2pp.cf) were not overriding those of site.cf.

*Testcase number*	*Detailed description*	*Expected result*
35.1/	- change any entry of the .p2pp.cf	- .p2pp.cf is considered not the site.cf

36/ Release note item 1332:
Fixed bug: in a Database Browser, shift-clicking (to complete selection) was not working right after completing a query: one needed to first click, although one row was already selected..

*Testcase number*	*Detailed description*	*Expected result*
36.1/	- shift-click in DBB right after completing a query	- shift-click works as expected

37/ Release note item 1747:
Updated list of supported keyword categories.

*Testcase number*	*Detailed description*	*Expected result*
37.1/	-	- New list includes: ADA AOS COU DEL DET DPR INS ISS OCS SEQ TEL

top of the page