Comments
SAP NEWS-710-TOOLS documentation, setup help and example usage
Tools in Release 7.0, EhP2
1 ABAP Editor
2 Class Builder
3 ABAP Debugger
4 Coverage Analyzer
5 ABAP Unit
6 Runtime Analysis
7 ABAP Test Cockpit
8 Checkpoint Groups
ABAP_MODIFICATION_1 ABAP Editor
Code Completion has been added to the new ABAP front-end editor. This tool proposes appropriate ABAP words and operands for where you are in your code. By default, you call Code Completion using Ctrl+Space . The following units can be completed:
Data objects including structures and components
Data types and classes
Components of classes
Function modules
Subroutines
Formal parameters
Database tables
ABAP words
You can accept the proposals as they are or as patterns with prefilled parameters.
ABAP_MODIFICATION_2 Class Builder
You can use the Source Code-Based Editor settings to expand the internal include programs of a class pool. This displays the entire source code of a global class like a program in ABAP Editor and you can edit it. When you save, the modified source code is then split among the corresponding include programs.
ABAP_MODIFICATION_3 ABAP Debugger
The following functions have been added to the two-process debugger:
Variable display :
A new tab page, Auto , displays the last return codes of methods.
You can now change long data objects in the detail view.
Table tool :
Support for secondary keys (the key used can be toggled in the debugger).
Tables can be filled with data that was previously downloaded onto the presentation server.
Substructures of structured line types can be expanded in a line.
You can hide and show columns.
Display settings are retained for specific tables.
Breakpoint tool :
Special breakpoints for Web Dynpro ABAP (specification of Web Dynpro component , Web Dynpro controller , or a Web Dynpro method ).
Special breakpoints for simple transformations (debugging of
simple transformations ).
Special breakpoints for a stack change (breakpoint for a program or procedure change).
Special breakpoint for imprecise Decfloat calculation (stops if an imprecise statement or calculation with decimal floating point numbers takes place).
Screen tool :
New tool for analyzing screens (control, properties, layout).
ST debugging :
New tool for debugging simple transformations (step-by-step execution, variables display, breakpoints).
Debugger scripting :
You can use ABAP Debugger scripting to analyze the current ABAP context.
Called using a breakpoint or an automated single step.
You can stop, trace , or change the context of the debuggee
in a script.
An integrated script tool allows you to write, save, load, and execute scripts.
Transaction SAS allows the independent maintenance of
debugger scripts .
Statement debugging :
You can debug multiple statements in one line step by step.
You can also debug logical expressions step by step.
Layer debugging :
The user can define the software layer (package, program, procedure, or interface) that he or she wants to debug.
A layer can be executed as a single step in debugging.
Stack tool :
New setting for displaying the call stack of an internal call mode.
Exception tool :
New tool for displaying and analyzing the last and previous class-based exceptions.
Console tool :
This new tool displays the growing data of serializations from ABAP to XML for CALL TRANSFORMATION and for classic list outputs.
Enhancement concept :
Visualization of enhancements in the stack.
Possibility of skipping or executing enhancement implementations.
ABAP byte code :
In the ABAP byte code or ABAP byte code (debug macro) context menus, you can select what a replacement for a proper macro debugging run can depict.
Functions adopted from the old debugger :
Display of the current generated classic list in debuggee mode.
Possibility of restarting the entire application.
Settings (block sending TRFC , ESI debugging , Shared Objects : Debug automatic area structure, always generate exception object, Control Framework : Automation controller Always processes requests synchronously, check sorting before
ABAP_MODIFICATION_4 Coverage Analyzer
Coverage Analyzer has been modified to include the following:
Code coverage is now measured on the statement level.
The coverage of individual conditions of logical expressions is measured.
The coverage of empty branches is measured.
The coverage of the executed and non-executed statement blocks in control structures is measured (branch coverage).
Code coverage is visualized in different colors in the new ABAP front-end editor. To measure the coverage of test runs,
ABAP_MODIFICATION_5 ABAP Unit
In Release 7.0, EhP2 , the additions introduced for the statement CLASS ... FOR TESTING , namely RISK LEVEL and DURATION , have replaced the pseudo-comments introduced in Release 7.0, namely
An ABAP Unit Browser integrated into the Object Navigator
of the ABAP Workbench allows:
A structured overview of existing unit tests to be displayed.
Multiple test runs to be started at the same time.
Unit tests to be organized in favorites.
For the latter item, test coverage can be measured and displayed using the Coverage Analyzer .
Class CL_ABAP_UNIT_ASSERT replaces class CL_AUNIT_ASSERT . New methods are now assigned to the new class only. Existing module tests do not have to be converted to the new class. However, we recommend that you use the new class only in new tests.
ABAP_MODIFICATION_6 Runtime Analysis
The runtime analysis tool as been switched to the new transaction SAT (the previous transactions were SE30 and ATRA ). The new runtime analysis tool
has a new user interface for analyzing measurements. Like ABAP Debugger, it consists of adjustable Desktops where you organize various tools.
contains additional and more flexible analysis tools than the previous version.
saves the measurement data to the database, which makes it independent of the operating system of the application server.
enables the cross-system comparison of measurement data.
ABAP_MODIFICATION_7 ABAP Test Cockpit
The ABAP Test Cockpit ( ATC ) is a framework that is integrated into the ABAP Workbench to execute various tests for development objects and to show the results of these. The following are some of the tests that are currently integrated:
Extended program checks
Performance tests
Unit tests
Usability tests
Package checks
ABAP_MODIFICATION_8 Checkpoint Groups
A time limit now applies to activation settings for checkpoint groups . When you save an activation setting in transaction SAAB , you have to specify either a validity period (valid for the current day or week), or a validity end date. The default value (valid for the current day) is generally suitable for most applications.
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved
