Testability Tips
ü Transaction flow should be implemented as a primary specification and design tool
ü Use separate transaction control blocks for primary control
ü Build all instrumentation as a part of system design
ü Transaction dispatcher should be centralized, table driven
ü In between the transaction flow paths, there should not be any one-to-one correspondence
ü In transaction flows, avoid jumping statements, GOTO statements, deeply nested loops etc., to the maximum extent possible
ü Keep the total number of paths, number of covering paths and number of feasible paths as close as possible to one another
ü Try to design a transaction control language that needs to be validated for correctness of the syntax and semantics
0 comments:
Post a Comment