ABAP_to_the_Future

4
ABAP Test Cockpit
related to the Code Inspector. What you’re doing is defining which tool is going
to be called when someone tries to release a transport; that is, you have to choose
either the Code Inspector or the ATC as the transport release check tool by disabling
the one you don’t want.
For this example, select Disable “Code Inspector” as Test Driver , because SAP
recommends that you use the ATC. You could have chosen the Code Inspector as
the tool to use by setting the ATC box to Disable “ATC” as Test Driver.
In the dropdown box for whichever tool you have selected, there are two options
aside from Disable. You can select Inform on Error , which means that when
someone is trying to release a transport, the ATC or Code Inspector is run; the user
gets a pop-up box with the warnings and errors, and the release can be aborted if
the user wants. If you choose Block on Error, then the same pop-up box appears,
but the transport cannot be released if any priority one errors remain.
Once you’ve set up mass checks, it’s time to run them and review them.
4.2.2 Running Mass Checks
To set up a periodic batch job to review all custom objects, you once again call up
good old Transaction ATC and follow the menu path ATC Administration 폷 Runs
폷 Schedule Runs 폷 Create. You will be asked for a name. Enter something like
“ZSC_MONSTERS”, click the green checkm ark, and then you’ ll see the screen
shown in Figure 4.6.
Figure 4.6 Defining a Mass Check Run
182