Tips and tricks for creating test cases 

• Do not use external number assignment.
  (Get numbers from the CATT number range with the function module CAT_NUMBER_GET_NEXT)
• Do not specify constant dates.
  Use variables: &JHR, &DAT; date variables
• Use variables and parameters instead of constants in screens to make test modules flexible
• Use text variables (&T01,...,&T99) for language-dependent fields.
  (See also "Language-independence" in Rules for creating and maintaining test procedures)
• Define allowed error messages.
  If this error message is sent, it is not logged.
• Only run parts of a test case in the foreground.
  Enter processing mode A in the REF function detail maintenance for a called test case.
  Enter processing mode A in the TCD function detail maintenance screen for a transaction.
  This part of the test case then runs in the foreground, even if the test started in "background processing".
• You can deactivate individual lines in the CATT function editor.
  If you want to exclude a function temporarily, you do not need to delete it, you can deactivate it to by flagging the I column at the end of the line in the function editor. This function does not then run in the test.
• Use the Field list (function TCD) for changed transactions:
  If dialog transaction changes have removed fields from screens, the field list helps you find the fields used in CATT again.
  Fields which were previously used by CATT are at the end of the list (after the BDC fields), with their previous value, and can so be easily identified.
• You can display all test check data with the SE38 report RSCATPRF.