Hi!
You have several possibilities to handle ABAP code checking. Here it is test roadmap:
1. Static compilation - for syntax errors check.
2. Extended program check (transaction SLIN) - to analyze the errors, warnings and potential sources of runtime errors and others severe problems that may exist in your code.
3. Code Inspector (transaction SCI) - to perform more sophisticated static checks.
4. ABAP Unit testing - to ensure all modularization units of your program are actually doing what they are supposed to do.
5. Integration tests with eCATT, the extented Computer Aided Test Tool (transaction SECATT) - to verify that the modularization units and application screens work together correctly in a complex application scenario.
6. Coverage analysis (transaction SCOV) - to verify that all relevant parts of your program have been executed and tested before you release it for use in your production system.
More info you can find in Erik Sodtke article "An Integrated Approach to Troubleshooting Your ABAP Programs:
Using Standard SAP “Check” Tools During Development and Testing".
Regards,
Maxim.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.