1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/docs/testing.txt Fri Jul 08 21:05:20 2011 +0200
1.3 @@ -0,0 +1,41 @@
1.4 + ____ _ _ _ _ _
1.5 + / ___| ___ | |__ __ _ ___ | |__ | | | || |__ _ __
1.6 + \___ \ / __|| '_ \ / _` | / __|| '_ \ | | | || '_ \ | '__|
1.7 + ___) || (__ | | | || (_| || (__ | | | || |_| || | | || |
1.8 + |____/ \___||_| |_| \__,_| \___||_| |_| \___/ |_| |_||_|
1.9 +
1.10 + Europalab SchachUhr - Game clock graphical user interface client
1.11 +
1.12 + QUALITY ASSURANCE
1.13 +
1.14 + TEST PLAN
1.15 +
1.16 + How the testing will be done
1.17 + Who will do it
1.18 + What will be tested
1.19 + How long it will take
1.20 + What the test coverage will be
1.21 + ...what quality level is required
1.22 +
1.23 + TEST CASES
1.24 +
1.25 + Cases include specification of test design and test procedure.
1.26 +
1.27 + Case id: #T.01
1.28 + Case name: Test name
1.29 + Assumption: initial screen is displayed
1.30 + Input:
1.31 + Output:
1.32 + Expected behaviour:
1.33 +
1.34 + TEST LOG
1.35 +
1.36 + INCIDENTS
1.37 +
1.38 + SUMMARY
1.39 +
1.40 + NOTES
1.41 +
1.42 + Whitebox tests, blackbox tests, unit tests, and regression tests are
1.43 + to be automated when possible. Attention must be given to the native
1.44 + test framework of the implementation technology in use.
