docs/testing.txt

changeset 11
f83d5d4b7088
equal deleted inserted replaced
-1:000000000000 0:c749e539bf90
1 ____ _ _ _ _ _
2 / ___| ___ | |__ __ _ ___ | |__ | | | || |__ _ __
3 \___ \ / __|| '_ \ / _` | / __|| '_ \ | | | || '_ \ | '__|
4 ___) || (__ | | | || (_| || (__ | | | || |_| || | | || |
5 |____/ \___||_| |_| \__,_| \___||_| |_| \___/ |_| |_||_|
6
7 Europalab SchachUhr - Game clock graphical user interface client
8
9 QUALITY ASSURANCE
10
11 TEST PLAN
12
13 How the testing will be done
14 Who will do it
15 What will be tested
16 How long it will take
17 What the test coverage will be
18 ...what quality level is required
19
20 TEST CASES
21
22 Cases include specification of test design and test procedure.
23
24 Case id: #T.01
25 Case name: Test name
26 Assumption: initial screen is displayed
27 Input:
28 Output:
29 Expected behaviour:
30
31 TEST LOG
32
33 INCIDENTS
34
35 SUMMARY
36
37 NOTES
38
39 Whitebox tests, blackbox tests, unit tests, and regression tests are
40 to be automated when possible. Attention must be given to the native
41 test framework of the implementation technology in use.

mercurial