1. System Test Design The Location of Test Design Test Design Structure
TCON
The Location of Test Design
Test Design Structure
Test Design Content by ANSI/IEEE-829
System Test Requirements
System Test Approaches
Random Testing
Architectural Testing
Use Case Testing
Calender Use Cases
Live Testing
Regression Testing
System Test Scenarios
Defining Test Scenarios
Calender Test Scenarios
System Test Objects
Calender Test Objects
Potential Test End Criteria
Calender Test End Criteria
Test case / Requirement Table
Test case / Use Case Table
Test case / Test object Table
Test case / Database Table
Requirement/Test case Table for Calender
Use case /Test case Table for Calender
Test Object / Test case Table for Calender
Test Design of a Data Feed Process 1 14 2 15 3 16 4 17 5 18 6 19 7 20 8 21 9 22 10 23 11 24 12 25 13 26

2. Location of Test Design in the Test Process
SYST
TCON-1
Activity of Designing the System Test
Init
Test-
planning
Test Plan
Test
design
Test
Design
Test
spec.
Test
Cases
Test
execution
Result of
Test Design
Test
Results
Test
evaluation
Closure
Test
Docu.

3. Structure of Test Design
SYST
TCON-2
Test
Design
Test
Goals
Test
Require-
ments
Test
Functions
Test
Objects
Test
End Criteria
Test-
scenarios
Test
Cases
Test
Cycles
Test
Metrics
Relationship of Test Design Entities

4. Test Design Content according to ANSI/IEEE-829
SYST
TCON-3 1
Test Design Id (Calender\Test\Design\Header.doc) Test Requirements (Calender\Test\Design\Require.doc) Test Approaches (Calender\Test\Design\Approach.doc) Test Scenarios (Calender\Test\Design\Scenario.doc) Test Objects (Calender\Test\Design\Objects.doc) Test End Criteria (Calender\Test\Design\Criteria.doc) 2 3 4 5 6

5. System Test Requirements
TCON-4
Requirements need to be validated
Functional Requirements Non-functional Requirements
 Create a Calender  Bad inputs should be tested
 Open a week  Table overflow should be tested
 Open a day  Network disruption should be tested
 Insert Activities  Database deadlock should be tested
 Delete aktivities  Response time should be tested
 Close a day  Recovery/Restart should be tested
 Close a week  Transaction Load should be tested
Print a calender  Usability should be tested
 Delete a calender  Security should be tested

6. System Test Approaches
TCON-5
System Test Approaches
Ways to validate the Test Requirements
Random Testing
Arbitrary Test against randomly selected data
Architectural Testing
Systematic Test of the System Design
Functional Testing
Systematic Test of the System Use Cases
Live Testing
Test of the System in the Production Environment
Regression Testing
Test of the System against the preceeding system.

7. Random Testing System spits out random results
TCON-6
System spits out random results
S y s t e m
Mouse runs over the User Interface
There is no real way to
Validate random results
Parameter
Random
data
Data
Generator
Random test leads to random results in the Database
Data
Structure

8. Architectural Testing
SYST
TCON-7
Terminal
Inputs
Outputs
Paths
User Interface
Path to
traverse
S y s t e m
Control Module
Module
Module
Access Module
Data
Editor
Selected Data DB

9. Use Case Testing Pre Conditions Post Condiutions Steps Exceptions
SYST
TCON-8
Pre Conditions
Post Condiutions
Steps
Exceptions
Actor
Actor
Use Case
Use Case
Use Case
Use Case

10. Calender Use Cases Mitarbeiter Create Calender Open a Week Open a Day
SYST
TCON-9
Mitarbeiter
Create
Calender
Open a
Week
Open a
Day
Insert an
Activity
Preconditions:
calender does not exist Calender exists Woche exits Day exists Week does not exist Day does not exist Time slot is free Post conditions:
Calender stored new Week is stored new day is stored new Activity stored Error Message Error Message Error Message Error Message
Calender Processing

11. Live Testing ------------------ From Production To Production Input
SYST
TCON-10
From Production
To Production
Input
Script
Output
Script
Production Inputs
Produktion Outputs
S y s t e m
User interface
Import
Files
Export
Files
Import Function
Export Function
Access Functions
Production data
Mutations
Master data
Test-DB
Prod-DB
Compare

12. Regression Testing ------------------ Replay- script Capture script
SYST
TCON-11
Replay-
script
Capture
script
S y s t e m
Masken
Old
Input
Files
New
Output
Files
Input Functions
Output Functions
Access Functions
Old Data
Test-DB
New Data

13. System Test Scenarios What should be tested when  Test Goals?
TCON-12
What should be tested when  Test Goals?
Test Scenario
Test of the
Data Entry
Correctness, Error Handling Data Overflow Response Time
Test of the
Data Update
Correctness, Error Handling, Deadlocking
Test of ther
Data Queries
Correctness, Data Overflow Response Time
Test of the
Report
Generation
Preciseness, Layout Correctness

14. Defining Test Scenarios
SYST
TCON-13
Initialize the Database with a batch process 1 2
Enter initial data via a Dialog process 3
Generate reports via a Batch process 4
Import the Import files via a Batch process 5
Update the Data via a Dialog process 6
Generate reports via a Batch process 7
Query the Database in a Dialog process 2

15. Calender Test Scenario
SYST
TCON-14.1
Calender Test 1
create a Calender 11
for unauthorized persons 12
for authorized persons
121
Open week with an invalid week
122
Open week with a valid week
1221
Open day with an invalid day
1222
Open day with a valid day
123
Close the week

16. With an inavlid Description
SYST
TCON-14.2
12221
Insert activities
122211
With a bad start time
122212
With a bad end time
122213
With an inavlid Description
122214
With a valid Description
122215
Delete an activity
122216
Insert too many activities
1223
Close a day 13
Close the calender

17. Test Objects Test Objects Was is to be tested  What Objects? Systems
TCON-15
Test
Objects
Was is to be tested  What Objects?
Systems
Components
Modules
Interfaces
Classes
Data Base
Tables

18. Calender Test Objects ------------------ User Interface Name Number
SYST
TCON-16
User Interface
Name Number
Calender
Week
Error Message
Day
Start Time
End Time
Description
Activity

19. Potential Test End Criteria
SYST
TCON-17
Functional
Coverage
Data
Coverage
Architectural
Coverage
Security
Coverage
Performance
Coverage
Projected
Error Coverage
Erfüllungsgrad =
Ist Soll

20. Calender Test End Criteria
SYST
TCON-18 1
All 4 use cases have been tested. All 16 use case steps have been tested. All 26 data attributes have been validated All 8 error messages have been provoked. System was tested with 20 simultaneous users. Response Time is in 90% of the cases under 2 Seconds. 8 of 9 predicted errors were found.. 2 3 4 5 6 7

21. Test Case/Requirement Relationship Table
SYST
TCON-19
R E Q U I R E M E N T S
TEST CASES REQU_1 REQU_2 REQU_3 REQU_4 REQU_5 REQU_6 REQU_7 REQU_8
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X X

22. Test Case / Use Case Relationship Table
SYST
TCON-20
U S E C A S E S
TEST CASES CASE_1 CASE_2 CASE_3 CASE_4 CASE_5
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X
TEST-CASE X

23. Test Case / Test Object Relationship Table
SYST
TCON-21
T E S T O B J E K T E
TEST CASES OBJ_A OBJ_B OBJ_C OBJ_D OBJ_E OBJ_F OBJ_G OBJ_H OBJ_I
TEST-CASE X X
TEST-CASE X X X
TEST-CASE X X X
TEST-CASE X X X X
TEST-CASE X X X X
TEST-CASE X X
TEST-CASE X X
TEST-CASE X X X
TEST-CASE X X X X
TEST-CASE X X X X
TEST-CASE X X X X X
TEST-CASE X X X X X X
TEST-CASE X X X X X X
.....

24. Test Case / Database Table Relationship Table
SYST
TCON-22
D A T A B A S E S
TEST CASES DB_1 DB_2 DB_3 DB_4 DB_5 TAB_A TAB_B
TEST-CASE-1 R U
TEST-CASE R U R
TEST-CASE R U R
TEST-CASE R D R U
TEST-CASE R U R U
TEST-CASE R R
TEST-CASE R R U
TEST-CASE R R D
TEST-CASE R R U
TEST-CASE R R D
TEST-CASE R R R U
TEST-CASE R R U U
TEST-CASE R R U D
.....

25. Requirement / Test Case Relationships for the Calender
SYST
TCON-23
A N F O R D E R U N G E N
TEST CASES Create Open Open Insert Delete Provoke Table Calender Week Day Activity Activity Error Overflow
Invalid Name
Valid Name of user
Invalid week
Valid week
Invalid day of week
Valid day of week
Invalid start time
Invalid end time
Valid activity
> Max Activities

26. Use Case / Test Case Relationships for the Calender
SYST
TCON-24
U S E C A S E S
TEST CASES Create open a open a Insert an Calender Week Day Activity
Invalid Name
Valid Name of User
Invalid Week
Valid Week
Invalid day
Valid day of week
Invalid start time
Invalid end time
Valid Activity
> Max Activities

27. Test Object / Test Case Relationsships for Calender
SYST
TCON-25
T E S T O B J E C T S
TEST CASES Calender Week Day Aktivity Error Msg
Invalid Name
Valid Name of User
Invalid Week
Valid Week
Invalid Day
Valid Day of week
Invalid start time
Invalid end time
Valid Activity
> Max Activities

28. Test Design of a Data Feed Process
SYST
TCON-26
Test Design of a Data Feed Process
To be validated
by WSDLVal
To be generated
by XMLGen
XML
Import Interface
WSDL
Export Interface
Use Cases
UC-01
UC-16
UC-17
Input
Messages
Update
Event
XML
WSDL
BaseEvent
Benach-
richtigung
Nachricht
Manschaft
Liga
Regel
FeedEvent
Delivered
FeedEvent
Benach.
Typ
To be validated by
CSVVal
To be generated by
CSVGen