富士通catt.doc

       As the CATT tool enters data in the SAP System via the user interface, the test data causes real database changes. You can use this feature to create data for manual tests or training or demonstrations.  A test module / test procedure has the following components: Attributes: contain flags and management information about a test module or procedure, which could be used as search criteria in the Repository Infosystem. Functions: individual test actions in a test module or test procedure, which are performed when a test procedure is executed. Parameters: pass values to test modules or test procedures. Run: (individual): the execution screen contains the execution conditions (log type, processing mode). This is where you run a test procedure or test module. Log: a log is created for each test run  Header data: test procedure: from 4.0A procedure numbers are assigned externally. short text (required field): enter a short explanation. For a test module you should start with the transaction code of the transaction to be tested. This aids the clarity of the references to test modules in test procedures, where the test module short text is displayed. key word 1 (required field): enter an appropriate term. General data: by assigning your CATTs to applications, subapplications and components, you assign them to the application component structure  Management data: person responsible: the creator of the test procedure is automatically entered in this field when you save. If the creator is not the contact person for this test module/test procedure, change the entry. Dependencies: If your test procedure or test module depends on the frontend, system platform, language or country, set the associated flag. If you need particular settings/additions in your system before running your test procedure (e.g. a second plant when testing stock transfer), the procedure which makes these settings must run before the other CATTs. Set this flag for such a CATT procedure,