Introduction

• Using ATC tools in your development landscape requires that the setup for ATC is completed.
• To run the ATC check, you need the respective authorizations for the ABAP Test Cockpit.
• You need at least ABAP Development Tools client version 2.31.

Figure 1: ATC quality check as an integral part of the development and delivery process

ABAP developers have various options for using ATC tools. In the current shipment, they can use ATC in the following use cases:

1. Running ATC checks during development

   Developers run the ATC checks to find potential bugs already during the development and launch of ATC from within their IDE.

   More on this:Working with ATC During Development

2. Running ATC checks during transport release

   During the transport release, the ATC implicit check run for all development objects that are included in the transport request provides the first Q Gate (quality gate).

   More on this:Working with ATC During Transport Release

3. Working with central ATC results from mass regression check runs that have been scheduled in a central quality system

   In the target quality system, the mass regression check runs are scheduled and serve as the final Q Gate before the code changes are released.

   More on this:Working with Central ATC Results

4. Handling exemptions (false positives) for ATC findings

   ATC tools integrate an exemption process for false positives in order to handle findings that cannot be cleaned up. In a separate process, the developer requests an exemption for a finding. The quality manager then approves or rejects the request.

   More on this:Applying for ATC Exemptions