14.01.2020 Views

ABAP_to_the_Future

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4

ABAP Test Cockpit

option shown at the bottom left of Figure4.11. However, as opposed to the Code

Inspector equivalent in the ATC screen, there are two documentation lines:

왘 Check Title

Gives a description of the general group of errors you’re looking at with a list

of the individual checks.

왘 Check Message

Gives a description of the specific chec k that failed. In lower releases, this

seems not to work all the time; you sometimes only get the description of the

group of checks.

4.2.4 Dismissing False Errors

If you look back briefly at Figure 4.10, you will notice that it shows over 15,000

priority one errors just from one develo per. Unfortunately, when you first run

this for yourself you are likely to get such a result, and some of the check messages

say dire things, like Very Serious Error. When you first see this, you may

be horrified and want to jump off a bridge before anyone else discovers the woeful

state of your code.

In fact, things are in no way as bad as they may appear at first. Obviously, every

error message needs to be looked at, but such messages appear in groups of similar

errors. Although some problems are crying out to be fixed, some of the

“errors” are not in fact problems at all, but just the check tool being overzealous.

This brings us to the subject of false errors and, more specifically, false positives.

A false positive is an alert that an error has oc curred even though everything is

actually fine. To take an example from the real world, it was a false positive when,

in the former Soviet Union, a pigeon flew into a radar dish and triggered a warning

saying that the United States had just launched a massive nuclear attack. (The

rules, which the communication officer broke, said that he should have informed

his superiors—who would have instructed him to counterattack, thus causing a

nuclear war that would have destroyed the world. So it’s lucky he didn’t trust his

country’s own technology.)

Fortunately, in SAP terms, false positives are not that drastic. A common situation

in which a false positive may occur is when you have a variable that should

sometimes, but not always, be changed based on the value of another variable.

In order to make sure that this variable is changed as required, you could use a

188

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!