docs/testing.txt@8fd77655ff43
docs/testing.txt
Wed, 27 Jul 2011 23:08:32 +0200
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Wed, 27 Jul 2011 23:08:32 +0200
- changeset 13
- 8fd77655ff43
- permissions
- -rw-r--r--
Added tag SCHUR_0.6.2 for changeset 1d13b7bae644
1 ____ _ _ _ _ _
2 / ___| ___ | |__ __ _ ___ | |__ | | | || |__ _ __
3 \___ \ / __|| '_ \ / _` | / __|| '_ \ | | | || '_ \ | '__|
4 ___) || (__ | | | || (_| || (__ | | | || |_| || | | || |
5 |____/ \___||_| |_| \__,_| \___||_| |_| \___/ |_| |_||_|
7 Europalab SchachUhr - Game clock graphical user interface client
9 QUALITY ASSURANCE
11 TEST PLAN
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
20 TEST CASES
22 Cases include specification of test design and test procedure.
24 Case id: #T.01
25 Case name: Test name
26 Assumption: initial screen is displayed
27 Input:
28 Output:
29 Expected behaviour:
31 TEST LOG
33 INCIDENTS
35 SUMMARY
37 NOTES
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.
