Chapter 7. Testing your application
This chapter describes ways of making your applications more error-free.
Often two systems that run perfectly by themselves, when run together cause performance degradation and you begin experiencing “lockouts” or waits. In this case, the scope of each system has not been defined adequately.
The key points in a well-designed application system are: v
At all levels, each function is defined clearly with inputs and outputs well stated. v
Resources that the system uses are well defined. v
Interactions with other systems are known.
Testing applications
The following general rules apply to testing applications: v Don’t test on a production CICS system—use a test system, where you can isolate errors without affecting “live” databases. v
Have the testing done by someone other than the application developer, if possible. v
Document the data you use for testing. v
Test your applications several times, exercising as much program logic as is practical. v
Use the OS/400 and CICS/400 facilities to trace and debug your application
during initial testing. See “Trace” on page 111.
v
Starting the CICS/400 user shell before using OS/400 debug facilities can reduce the size and complexity of the output. v
Use stress or volume testing to catch problems that may not arise in a single-user environment. v
Test whether the application can handle
correct
data and
incorrect
data.
– When correct data is entered, does your program acknowledge its receipt?
– When incorrect data is entered, do you get an appropriate error message?
v
Check whether files and databases are updated correctly. v
Test against complete copies of the related databases. v
Before you move an application to the production system, it is also good practice to run a
final
set of tests against a copy of the production database to catch any errors.
Screen usage, checks and considerations
The following lists some screen considerations for CICS programmers: v
Check whether screens are displayed in the expected sequence. v
All headings and captions should be placed correctly. v
Check for any misspellings. v
Ensure that your screen is easy to read and to use.
© Copyright IBM Corp. 1998, 2004
101
