Show TOC

Setting Up the ABAP Test Cockpit in Your Development LandscapeLocate this document in the navigation structure


This document explains how to implement a best-practices recommendation for ABAP quality checking with the ABAP Test Cockpit (the ATC).

The best-practices recommendation for quality checking is shown in this diagram:

Figure 1: Best Practice Quality Checking with the ABAP Test Cockpit

In this best-practices recommendation, ATC quality checking takes place at four levels:

  • Starting from the development system, individual developers run local checks of the code that they are working on, directly from the development transactions.

  • Also in the development system, the development team checks the code for which it is responsible with automatic ATC checks.

  • Automatic transport checking provides a Q-Gate when code leaves the development system at transport release.

  • In the consolidation or test/quality system (aka the ATC master system), the quality manager runs mass quality checks with the ATC. These checks are published to the development systems as the current, active ATC results.

    Developers can use these central results for clearing quality problems. If necessary, developers can request exemptions against these results. The management and persistence of exemptions takes place on the ATC master system.

The result is an efficient multi-layered approach to ensuring quality in ABAP development. The approach combines quick ad hoc testing close to the developer with a robust centralized system for managing official quality checking.


Putting this best-practices recommendation into action requires these activities:


  1. Choose the systems to be your ATC master systems. On master systems you can do central ATC quality checking.

  2. Define and distribute a standard Code Inspector check variant, if you do not already have one.

  3. Set up RFC communications between each ATC master system and its satellite development systems.

  4. Prepare users for the ATC.

Setting up the ATC master system:

  1. Set up the ATC on the central system with transaction ATC.

  2. Register namespace settings from each development landscape at the landscape's ATC master system.

  3. Define the object set for ATC central quality checks in the master system.

  4. Schedule ATC central check runs and set up other automated procedures.

Setting up ATC satellite development systems:

  1. Configure the ATC on a development system and replicate the configuration to other development systems with transaction ATC.

  2. Set up ATC checking of objects in transports at transport release.

  3. Schedule ATC quality checks for development teams or departments.

  4. Establish local ATC quality checking routines in development systems.