IPACMAN V2.4 Integration Test Plan

Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/IPACMAN-test-plan.html
Дата изменения: Mon Oct 14 20:36:15 2002
Дата индексирования: Sun Apr 13 22:57:34 2008
Кодировка:
Поисковые слова: arp 220

DFS Group Home Page
IPACMAN V2.5 Test Plan (or more)

Environment

OS: SunOS 8
Machine: dmdsol8b
Login: khaggouc
JRE: 1.1.8
Accessed DB: TESTSRV

Summary

Count of testcases entirely executed**	(100%)
Total specified testcases**

**Be aware: this is a cumulative count considering ALL different platforms used for this testing.
Anyway, results given hereafter are related to one plaform only (the one mentioned on the top).

Criticity	Failed testcases count	Failed testcases list
Critical
High
Minor

standard testcases
specific testcases

Standard testcases

The following testcases correspond to the minimum set of tests to be run on every new IPACMAN release (alpha, beta, final, ...). They are not specific to a given release, but are to give some confidence about the fact that all basic functionalities of IPACMAN work fine, in nominal situations only. This means that all possible tricky or error situations, stress and performances tests 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 IPACMAN

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
1.1/	- run in debug mode - check the initial debug messages about the configuration tool (which DB is accessed, which JRE, external libraries/versions are used, which DB is accessed, - verify this against the config files which are under the .../config/ directory.	- no error - expected versions
1.2/	- verify the layout: check every menu content (contain expected items ?, any strange layout ?)	- expected layout

2/ INSERT IP

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
2.1/	- insert an IP with a correct filename for the zip. Done for every of the currently operational instruments.	- no error - inserted IPs appear in the main grid
2.2/	- insert an IP with an incorrect filename for the zip (verify the convention <INST>-rel.rev-date.zip for some basic error situations: <INST> name not consistent with the zip content; wrong rel value; wrong rev value).
2.3/	- insert an IP whose zip filename is correct (<INST>-rel.rev-date), but the VERSION keyword value in default.isf is different from "rel.ver".
2.4/	- insert an IP which has already been inserted.	- error message saying it's impossible
2.5/	- insert an IP via the CTRL+I short key.

3/ IPACMAN DB BROWSER

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
3.1/	- verify a new inserted IP gives a new entry in the browser grid: check that the displayed values of the Instrument, Version, Added by, IP date and Comments columns are consistent with the IP filename components and Comments entered when inserting the IP.
3.2/	- check that every "Selected Columns" (Added by, IP date and Comments) appears in the grid with expected values.
3.3/	- check the "Selection Criteria": run several queries choosing every value displayed in the corresponding List box; check that the List box is updated when inserting an IP for a new instrument.
3.4/	- check the 4 "Sort By" check boxes: the Query and Sort buttons return results which are consistent with the selected Sort criteria.
3.5/	- check the Count button, .
3.6/	- check the Clear button.

4/ DELETE IP

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
4.1/	- File>DeleteIP	- the entry is removed from the DB grid
4.2/	- CTRL+D	- the entry is removed from the DB grid
4.3/	- try to delete 2 IPs at the same time	- error message saying that the delete can not be performed
4.4/	- try to run CTRL+D when no IP is selected in the DB grid	- error message saying that the delete can not be performed
4.5/	- try to run File>DeleteIP when no IP is selected in the DB grid	- error message saying that the delete can not be performed

5/ EXTRACT IP

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
5.1/	- extract an IP via File>ExtractIP	- IP copied on disk to the specified location
5.2/	- extract an IP via CTRL+E	- IP copied on disk to the specified location
5.3/	- extract an IP via File>ExtractIP when no IP is selected in the DB grid	- error message saying that the extract can not be performed
5.4/	- extract an IP via CTRL+E when no IP is selected in the DB grid	- error message saying that the extract can not be performed
5.5/	- insert IP1, rename on disk the corresponding <INST> directory to <INST-orig>, extract IP1 from the DB (retrieve the zip somewhere on disk, and unzip it), and compare the default.isf of the <INST> directory with the default.isf of the <INST-orig> directory (comparison is done with the UNIX diff command). Same comparison for every TSF file.	- no difference found

6/ EDIT IP

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
6.1/	- File>Edit IP, change the: "Added by" "Comments" "Period"	- new values accepted and displayed by the grid
6.2/	- TSF Report: select a TSF and run CTRL+T .

7/ VERIFY REPORTS

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
7.1/	- Verify IP: select an IP on disk and run Reports>verify IP
7.2/	- Verify IP: select an IP on disk and run CTRL+V
7.3/	- Verify IP: select an IP in DB and run Reports>verify IP
7.4/	- Verify IP: select an IP in DB and run CTRL+V
7.5/	- Verify IP: select an IP on disk and run Reports>verify IP. Get the related report. Now, run P2PP in engineering mode, and verify the same IP. Compare at random the 2 reports (the one from IPACMAN with the one from P2PP): at random, means select 2 TSF and compare the warnings or errors reported in the 2 cases (they should be the same).

8/ IP DIFFERENCES REPORTS

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Conclusion
8.1/	- IP Diff: select an IP on disk, another one in the DB, and run Reports>IP Diff
8.2/	- IP Diff: select two IPs in the DB, and run Reports>IP Diff
8.3/	- IP Diff: select two IPs on disk, and run Reports>IP Diff
8.4/	- IP Diff: select two IPs on disk, and run CTRL+F
8.5/	- IP Diff: select two IPs on disk, and run Reports>IP Diff and check manually the results: verify the differences reported on the default.isf with the real content of the files on disk (parameters only in IP1, parameters only in IP2, parameters in both IPs). Also, verify the differences reported on the TSF files: for 2 TSF files selected at random, verify the reported differences with the real content of the files on disk (parameters only in IP1, parameters only in IP2, parameters in both IPs).

top of the page

Specific testcases

The following testcases correspond to the set of tests to be run on this specific IPACMAN 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 :
.

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
11.1/
11.2/
11.3/

12/ Release note item :
.

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
12.1/
12.2/
12.3/

13/ Release note item :
.

*Testcase number*	*Detailed description*	*Expected result*	*Effective result*	Symptoms	Conclusion
13.1/
13.2/
13.3/

top of the page