Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-ESI-SIW (Application Component) Service Implementation Workbench⤷
S_SIW_TYPES (Package) SIW: Global Type definitions
Basic Data
| Data Element | SIW_DTE_FLAG_ABAP_UNIT |
| Short Description | Execute ABAP Unit Tests of Generated Objects? |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SIW_DOM_FLG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | ABAP Unit |
| Medium | 15 | With Unit Test |
| Long | 20 | With ABAP Unit Test |
| Heading | 31 | With Unit Test |
Documentation
Definition
This flag indicates that ABAP unit tests of generated reports and classes shall be executed when available. You use ABAP unit tests to ensure that changes of ABAP source code and names do not influence the functionality of the corresponding program in an unplanned manner.
Use
Dependencies
If the project check finds unit tests in a project and if at least one of them fails, the project will be considered erroneous.
You can trigger that check manually at the generated objects' view of transaction SIW. The SIW transaction helps you to analyze the single object check result.
Note: SIW can only execute unit tests that reside within the generated development objects. If your unit tests reside elsewhere, use another tool like Unit Test Cockpit (transaction code FS83) or the ABAP Unit Browser (transaction code SE80) to execute these tests regularly.
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 730 |
