ABAP_to_the_Future

4
ABAP Test Cockpit
4.2.1 Setting Up Mass Checks
In an ideal world, you would run a ma ss check on the custom development
objects in the test system on a regular ba sis via a batch job. In order to achieve
this, there is some configuration that needs to be done, both in the master (test)
system and in every development system that can transport objects to the test system.
Start at the beginning: Transactio n ATC. When you run this transaction,
you’ll see a nice menu tree on the left, with pretty icons related to setting up configuration
and scheduling batch jobs (Figure 4.4).
Figure 4.4 Transaction ATC
Start by configuring the master/test syst em. Follow the menu path for general
configuration—ATC Administration 폷 Setup 폷 Configure ATC —which has the
Variant Configuration icon. Figure 4.5 shows the screen for setting up configuration.
In the Global Check Variant field, specify the Code Inspector variant that is to
be used by the ATC mass check. As might be expected, this defaults to DEFAULT.
However, most companies copy the DEFAULT variant to a Z version via Transaction
SCI and change some of the checks that are run. I strongly recommend doing
this; naturally, you want to make sure that all the checks you are interested in are
active (for example, unit tests). Note that your Z variant has to be a global variant
before it appears in the ATC list.
180