Implementing Your Application › Testing › What to Test

What to Test

Critical details to test in your application:

• Do function calls work?
  • Can every function be called?
  • Can every function that is supposed to call another function do so?

  Note: You can set up a menu, using Toolkit menu facilities, to test function calls.

• Do all the function keys work? If a function key is enabled but does not show on the panel, or does not work and does show on the panel, go to the device design and select the command to refresh the function keys from the action diagram.
  • Ensure the YCUAPMT model value is set to *YES or *CALC.
  • Does the F4=Prompt work for fields in which values should be checked?
  • If F4 does not work, the check values entry for the field may specify the default *NONE. Set the value to *ALL values or an appropriate LST condition.
  • If F4 works but you do not get the right list of values, run the Convert Condition Values (YCVTCNDVAL) command.
  • If F4 in a key field does not give you a Select Record (SELRCD), the SELRCD probably did not exist when you generated the function. You can create the SELRCD and regenerate the application that needs it.
• Are before/after image errors occurring? The file definitions in the model may differ from the compiled versions of the file. Regenerate the files and the functions built over those files.
• Are level checks occurring? Files may have been changed but the functions were not regenerated and compiled successfully.
• Is no data being returned for a Retrieve Object (RTVOBJ) function? You may need to code a *MOVE ALL built-in function from a Database File 1 (DB1) into a Parameter (PAR) context.
• Is an error occurring although the program continues? The program is not properly checking for and handling a return code.

For more information:

• On the SELRCD and RTVOBJ functions, refer to Building Applications.
• On YCVTCNDVAL, see the Command Reference Guide.