abapgit-agent 1.15.1 → 1.15.3

package/abap/guidelines/naming-limits.md

@@ -0,0 +1,160 @@
+---
+layout: default
+title: Naming Length Limits
+nav_order: 6
+parent: ABAP Coding Guidelines
+grand_parent: ABAP Development
+---
+
+# ABAP Naming Length Limits
+
+**Searchable keywords**: name length, character limit, 30 characters, 16 characters, 40 characters, too long, truncate, field name, method name, class name, table name, CDS name
+
+> **Rule of thumb**: Most ABAP object names → 30 chars. Table/structure **field names** → 16 chars. CDS/DDLS names → 40 chars. Method names (including test methods) → 30 chars.
+
+---
+
+## Quick Reference
+
+| Object / Element | Max Length |
+|---|---|
+| Class name (CLAS) | **30** |
+| Interface name (INTF) | **30** |
+| Program name (PROG) | **30** |
+| Function Group name (FUGR) | **26** |
+| Function Module name | **30** |
+| Table name (TABL) | **30** |
+| **Table field name** | **16** |
+| Structure name (STRU) | **30** |
+| **Structure field name** | **16** |
+| Data Element name (DTEL) | **30** |
+| Domain name (DOMA) | **30** |
+| Table Type name (TTYP) | **30** |
+| Package name | **30** |
+| **CDS View Entity name (DDLS)** | **40** |
+| CDS Access Control name (DCLS) | **40** |
+| CDS field alias | **30** |
+| Message Class name (MSAG) | **20** |
+| Class method name | **30** |
+| **Test method name** | **30** |
+| Interface method name | **30** |
+| Class attribute name | **30** |
+| Local variable name | **30** |
+| Local type/class name | **30** |
+| Test class name (local) | **30** |
+
+---
+
+## Critical Differences — Don't Confuse These
+
+### Table/Structure Field Names: 16 Characters MAX
+
+This is the **most common mistake**. Field names in TABL and STRU are limited to **16 characters**, not 30.
+
+```xml
+<!-- WRONG — 17 characters -->
+<FIELDNAME>LAST_MODIFIED_AT</FIELDNAME>
+
+<!-- CORRECT — 16 characters or fewer -->
+<FIELDNAME>LAST_MODIFIED</FIELDNAME>
+<FIELDNAME>SYS_CHANGED_AT</FIELDNAME>  <!-- 14 chars ✓ -->
+<FIELDNAME>LAST_PULLED_AT</FIELDNAME>  <!-- 14 chars ✓ -->
+```
+
+When naming table fields, keep names short and descriptive:
+- `CARRID` not `CARRIER_ID_FIELD`
+- `CONNID` not `CONNECTION_IDENTIFIER`
+- `STATUS` not `CURRENT_STATUS_FLAG`
+- `CREATED_AT` not `CREATION_TIMESTAMP`
+
+### CDS View Names: 40 Characters MAX
+
+CDS View Entity (DDLS) names allow up to **40 characters** — more room than regular ABAP objects.
+
+```
+ZC_MY_FLIGHT_BOOKING_REVENUE_SUMMARY     ← 40 chars (at limit)
+ZC_FLIGHT_REVENUE                        ← 17 chars (fine)
+```
+
+However, CDS **field aliases** inside the view are still limited to **30 characters** (ABAP identifier rules).
+
+### Function Group Names: 26 Characters MAX
+
+Function groups (`FUGR`) have a **26-character limit** because ABAP appends a 4-character suffix internally (e.g. `SAPLZMY_FG` prefix + module name). The safe usable name length is 26 characters.
+
+### Test Method Names: 30 Characters MAX — Causes Syntax Error
+
+Test methods (`FOR TESTING`) hit the 30-char limit frequently because the `test_` prefix takes 5 chars before the meaningful content starts.
+
+```abap
+" WRONG — 34 characters → syntax error at activation
+METHODS test_execute_with_minimal_params FOR TESTING.
+
+" CORRECT — abbreviate to stay within 30 chars
+METHODS test_exec_minimal FOR TESTING.     " 18 chars ✓
+METHODS test_exec_with_files FOR TESTING.  " 24 chars ✓
+```
+
+**Counting test method length**: include the full method name — `test_exec_minimal` is 18 characters.
+
+---
+
+## Counting Characters Before You Name Things
+
+Use this mental check before naming any ABAP element:
+
+```
+# Object name: type prefix + your name ≤ limit
+ZCL_             (4 chars) + name ≤ 30  →  name ≤ 26 chars
+ZIF_             (4 chars) + name ≤ 30  →  name ≤ 26 chars
+ZC_              (3 chars) + name ≤ 40  →  name ≤ 37 chars  (CDS)
+Z                (1 char)  + name ≤ 30  →  name ≤ 29 chars  (table/program)
+
+# Project-specific sub-namespace eats more of the budget — plan ahead
+# Example: project uses ZFICO_ prefix for all objects
+ZCL_FICO_        (9 chars) + name ≤ 30  →  name ≤ 21 chars
+ZCL_FICO_PAYMENT_PROPOSAL   = 26 chars  ✓
+ZCL_FICO_PAYMENT_PROPOSAL_V = 27 chars  ✓  (getting tight)
+
+# Field name in TABL/STRU: no prefix, just ≤ 16 total
+PAYMENT_METHOD               = 14 chars  ✓
+PAYMENT_METHOD_CD            = 17 chars  ✗  → shorten to PAYMENT_METH_CD
+
+# Method name: no prefix, just ≤ 30 total
+test_exec_with_files                    →  24 chars ✓
+test_execute_with_minimal_params        →  34 chars ✗
+```
+
+---
+
+## Common Length Violations and Fixes
+
+| Too Long (violates limit) | Fixed Version | Limit |
+|---|---|---|
+| `ZCL_COMMAND_PULL_WITH_RETRY` (30+ chars) | `ZCL_COMMAND_PULL_RETRY` | 30 |
+| `LAST_SUCCESSFULLY_PULLED_AT` (table field, 28 chars) | `LAST_PULLED_AT` | 16 |
+| `test_execute_command_with_files` (test method, 32 chars) | `test_exec_with_files` | 30 |
+| `ZC_MY_VERY_LONG_CDS_VIEW_NAME_EXCEEDS_40_CHARS` (47 chars) | `ZC_MY_LONG_CDS_VIEW_NAME_TRIMMED` | 40 |
+| `ZBIZ_OBJECT_CREATION_SERVICE_MESSAGE_CLASS` (MSAG, 43 chars) | `ZBIZ_CREATE_MSGS` | 20 |
+
+---
+
+## SAP Technical Basis for These Limits
+
+These limits come from the ABAP Dictionary (DDIC) and ABAP kernel:
+
+| Limit Source | Explanation |
+|---|---|
+| 30 chars (most objects) | ABAP uses `RSYN` program name space; objects stored in `TADIR` with `SOBJ_NAME CHAR(40)` but compiler enforces 30 for classes/interfaces/programs |
+| 16 chars (DDIC fields) | Stored in `DD03L.FIELDNAME CHAR(16)` — this is a hard database column width |
+| 40 chars (CDS names) | CDS objects stored in `DD02L.TABNAME CHAR(40)` — intentionally larger for CDS |
+| 20 chars (MSAG) | Message class name stored in `T100A.ARBGB CHAR(20)` |
+| 26 chars (FUGR) | Function group internally prefixed with `SAPL` (4 chars) for the main include |
+
+---
+
+## See Also
+
+- **Naming Conventions** (objects.md) — prefixes per object type
+- **Object Creation** (object-creation.md) — which files to create
+- **Testing** (testing.md) — test method naming (30-char limit detail)

package/abap/guidelines/object-creation.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Object Creation
-nav_order: 19
+nav_order: 22
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---
@@ -17,26 +17,29 @@ Replace `<name>` with the actual object name from this project's naming conventi
 
 | Object Type | ABAP Source File | XML File | Details |
 |-------------|-----------------|----------|---------|
-| Class | `<name>.clas.abap` | `<name>.clas.xml` | See `guidelines/abapgit.md` |
-| Interface | `<name>.intf.abap` | `<name>.intf.xml` | See `guidelines/abapgit.md` |
-| Program | `<name>.prog.abap` | `<name>.prog.xml` | See `guidelines/abapgit.md` |
-| **CDS View Entity** | `<name>.ddls.asddls` | `<name>.ddls.xml` | **Use by default** - See `guidelines/cds.md` |
-| CDS View (legacy) | `<name>.ddls.asddls` | `<name>.ddls.xml` | Only if explicitly requested - See `guidelines/cds.md` |
-| Table (TABL) | *(none — XML-only)* | `<name>.tabl.xml` | See `guidelines/abapgit.md` |
-| Structure (STRU) | *(none — XML-only)* | `<name>.stru.xml` | See `guidelines/abapgit.md` |
-| Data Element (DTEL) | *(none — XML-only)* | `<name>.dtel.xml` | See `guidelines/abapgit.md` |
-| Table Type (TTYP) | *(none — XML-only)* | `<name>.ttyp.xml` | See `guidelines/abapgit.md` |
-
-> **XML-only objects (TABL, STRU, DTEL, TTYP)**: create only the `.xml` file — there is no `.abap` source file.
+| Class (CLAS) | `<name>.clas.abap` | `<name>.clas.xml` | `ref --topic abapgit` |
+| Interface (INTF) | `<name>.intf.abap` | `<name>.intf.xml` | `ref --topic abapgit` |
+| Program (PROG) | `<name>.prog.abap` | `<name>.prog.xml` | `ref --topic abapgit` |
+| CDS View Entity (DDLS) | `<name>.ddls.asddls` | `<name>.ddls.xml` | **Use by default** — `ref --topic abapgit` |
+| CDS Access Control (DCLS) | `<name>.dcls.asdcls` | `<name>.dcls.xml` | `ref --topic abapgit` |
+| Function Group (FUGR) | `<name>.fugr.abap` + includes | `<name>.fugr.xml` | `ref --topic abapgit` |
+| Table (TABL) | *(none — XML-only)* | `<name>.tabl.xml` | `ref --topic abapgit-xml-only` |
+| Structure (STRU) | *(none — XML-only)* | `<name>.tabl.xml` ⚠️ NOT `.stru.xml` | `ref --topic abapgit-xml-only` |
+| Data Element (DTEL) | *(none — XML-only)* | `<name>.dtel.xml` | `ref --topic abapgit-xml-only` |
+| Table Type (TTYP) | *(none — XML-only)* | `<name>.ttyp.xml` | `ref --topic abapgit-xml-only` |
+| Domain (DOMA) | *(none — XML-only)* | `<name>.doma.xml` | `ref --topic abapgit-xml-only` |
+| Message Class (MSAG) | *(none — XML-only)* | `<name>.msag.xml` | `ref --topic abapgit-xml-only` |
+
+> **XML-only objects (TABL, STRU, DTEL, TTYP, DOMA, MSAG)**: create only the `.xml` file — there is no `.abap` source file.
 > After committing and pushing, pull with: `pull --files <folder>/<name>.tabl.xml --sync-xml`
 
-**IMPORTANT: When user says "create CDS view", create CDS View Entity by default.**
+**IMPORTANT: When user says "create CDS view", create CDS View Entity (DDLS) by default.**
 
 **Why:** Modern S/4HANA standard, simpler (no SQL view), no namespace conflicts.
 
 **For complete XML templates, DDL examples, and detailed comparison:**
-- **CDS Views**: `guidelines/cds.md`
-- **XML templates**: `guidelines/abapgit.md`
+- **CDS Views + DCLS + FUGR**: `abapgit-agent ref --topic abapgit`
+- **XML-only objects**: `abapgit-agent ref --topic abapgit-xml-only`
 
 ---
 

package/abap/guidelines/objects.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Naming Conventions
-nav_order: 7
+nav_order: 5
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---
@@ -15,12 +15,13 @@ grand_parent: ABAP Development
 | | SAP Namespace | Customer Namespace |
 |---|---|---|
 | **Object prefix** | `CL_*`, `IF_*`, `/NAME/CL_*`, `/NAME/IF_*`, etc. | `Z*`, `Y*` |
-| **Package prefix** | SAP-delivered (e.g. `SFIN`, `CA_*`, `/NAME/*`) | `Z*`, `Y*`, `$*` |
+| **Package prefix** | SAP-delivered (e.g. `SFIN`, `CA_*`, `/NAME/*`) | `Z*`, `Y*`, `$*` (local/non-transportable) |
 | **Ownership** | Delivered and maintained by SAP | Owned by the customer |
 | **In git repo** | Objects from an SAP-delivered package | Custom development objects |
 
 > **Rule**: Never add customer-created objects (including PoC/probe classes) into SAP namespace
 > packages. PoC objects always use `Z*`/`Y*` prefix and always go in a `Z*`, `Y*`, or `$*` package
+> (use `$*` only for throwaway probes — non-transportable)
 > — even on a project where production objects use SAP namespace.
 
 ## How to Determine This Project's Naming Convention
@@ -43,7 +44,8 @@ Applied when no `objects.local.md` exists:
 | Class | `ZCL_` | `ZCL_MY_CLASS` |
 | Interface | `ZIF_` | `ZIF_MY_INTERFACE` |
 | Program | `Z` | `ZMY_PROGRAM` |
-| Package | `$` | `$MY_PACKAGE` |
+| Package | `Z` or `Y` | `ZMYPROJECT` |
+> **Note**: `$` packages (e.g. `$TMP`) are local/non-transportable — use only for throwaway probe objects, never for real development.
 | Table | `Z` | `ZMY_TABLE` |
 | CDS View Entity | `ZC_` | `ZC_MY_VIEW` |
 | Data Element | `Z` | `ZMY_ELEMENT` |
@@ -83,3 +85,4 @@ Default package:  /MYNAMESPACE/MAIN
 
 → For file structure (what files to create): `abapgit-agent ref --topic object-creation`
 → For XML templates: `abapgit-agent ref --topic abapgit`
+→ For name **length limits** (30/16/40 char rules): `abapgit-agent ref --topic naming-limits`

package/abap/guidelines/testing.md

@@ -1,14 +1,14 @@
 ---
 layout: default
 title: Unit Testing
-nav_order: 4
+nav_order: 7
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---
 
 # Unit Testing
 
-**Searchable keywords**: unit test, AUnit, test class, cl_abap_unit_assert, FOR TESTING, setup, teardown, RISK LEVEL, DURATION, CDS test double, CL_CDS_TEST_ENVIRONMENT
+**Searchable keywords**: unit test, AUnit, test class, cl_abap_unit_assert, FOR TESTING, setup, teardown, RISK LEVEL, DURATION, WITH_UNIT_TESTS, testclasses
 
 ## TOPICS IN THIS FILE
 1. Local Test Classes - line 22
@@ -16,8 +16,6 @@ grand_parent: ABAP Development
 3. Required Elements - line 35
 4. Naming Conventions - line 67
 5. Common Mistake: DDLS Testing - line 133
-6. CDS Test Doubles - line 163
-7. CDS with Aggregations - line 247
 
 ## Unit Testing with Local Test Classes
 
@@ -169,206 +167,10 @@ Or via abapGit: Pull the files and run tests in the ABAP system.
 
 ## Unit Testing CDS Views
 
-When testing code that uses CDS view entities, you can use the **CDS Test Double Framework** (`CL_CDS_TEST_ENVIRONMENT`) to create test doubles for CDS views. This allows you to inject test data without affecting production data.
-
-### When to Use CDS Test Doubles
-
-- Testing code that reads from CDS views
-- Need controlled test data (not production data)
-- Testing CDS view logic with specific scenarios
-
-### CDS Test Double Framework
-
-Use `CL_CDS_TEST_ENVIRONMENT` for controlled test data:
-
-```abap
-"-------------------------
-" CLASS DEFINITION
-"-------------------------
-CLASS ltcl_cds_test DEFINITION FOR TESTING RISK LEVEL HARMLESS DURATION SHORT FINAL.
-
-  PRIVATE SECTION.
-    " IMPORTANT: Use interface type, not class type!
-    DATA mo_cds_env TYPE REF TO if_cds_test_environment.
-
-    " IMPORTANT: class_setup/teardown must be CLASS-METHODS (static)!
-    CLASS-DATA mo_cds_env_static TYPE REF TO if_cds_test_environment.
-
-    METHODS setup.
-    METHODS test_cds_with_doubles FOR TESTING.
-
-    CLASS-METHODS: class_setup,
-                   class_teardown.
-
-ENDCLASS.
-
-"-------------------------
-" CLASS IMPLEMENTATION
-"-------------------------
-CLASS ltcl_cds_test IMPLEMENTATION.
-
-  METHOD class_setup.
-    " Create CDS test environment - framework auto-creates doubles for dependencies
-    mo_cds_env_static = cl_cds_test_environment=>create(
-      i_for_entity = 'ZC_MY_CDS_VIEW' ).
-  ENDMETHOD.
-
-  METHOD class_teardown.
-    " Clean up test environment
-    mo_cds_env_static->destroy( ).
-  ENDMETHOD.
-
-  METHOD setup.
-    " IMPORTANT: Assign static env to instance and clear doubles
-    mo_cds_env = mo_cds_env_static.
-    mo_cds_env->clear_doubles( ).
-  ENDMETHOD.
-
-  METHOD test_cds_with_doubles.
-    " IMPORTANT: Must declare table type first, cannot inline in VALUE!
-    DATA lt_test_data TYPE TABLE OF zc_my_cds_view WITH EMPTY KEY.
-    lt_test_data = VALUE #(
-      ( field1 = 'A' field2 = 100 )
-      ( field1 = 'B' field2 = 200 ) ).
-
-    " Insert test data using named parameter
-    mo_cds_env->insert_test_data( i_data = lt_test_data ).
-
-    " Select from CDS view
-    SELECT * FROM zc_my_cds_view INTO TABLE @DATA(lt_result).
-
-    " Verify results
-    cl_abap_unit_assert=>assert_not_initial(
-      act = lt_result
-      msg = 'Result should not be empty' ).
-
-    cl_abap_unit_assert=>assert_equals(
-      act = lines( lt_result )
-      exp = 2
-      msg = 'Expected 2 rows' ).
-  ENDMETHOD.
-
-ENDCLASS.
-```
-
-### Testing CDS Views with Aggregations (SUM, COUNT, GROUP BY)
-
-For CDS views with aggregations, insert test data into the **base tables** (SFLIGHT, SCARR, SBOOK), not directly into the CDS view:
-
-```abap
-METHOD test_aggregation.
-  " Insert data into base tables via CDS test doubles
-  DATA lt_scarr TYPE TABLE OF scarr WITH EMPTY KEY.
-  lt_scarr = VALUE #( ( carrid = 'LH' carrname = 'Lufthansa' currcode = 'EUR' ) ).
-  mo_cds_env->insert_test_data( i_data = lt_scarr ).
-
-  DATA lt_sflight TYPE TABLE OF sflight WITH EMPTY KEY.
-  lt_sflight = VALUE #( ( carrid = 'LH' connid = '0400' fldate = '20240115'
-                          seatsmax = 200 seatsocc = 100 ) ).
-  mo_cds_env->insert_test_data( i_data = lt_sflight ).
-
-  DATA lt_sbook TYPE TABLE OF sbook WITH EMPTY KEY.
-  lt_sbook = VALUE #(
-    ( carrid = 'LH' connid = '0400' fldate = '20240115' bookid = '0001' forcuram = 1000 )
-    ( carrid = 'LH' connid = '0400' fldate = '20240115' bookid = '0002' forcuram = 2000 )
-    ( carrid = 'LH' connid = '0400' fldate = '20240115' bookid = '0003' forcuram = 3000 ) ).
-  mo_cds_env->insert_test_data( i_data = lt_sbook ).
-
-  " Select from CDS view - aggregations will use test double data
-  SELECT * FROM zc_flight_revenue INTO TABLE @DATA(lt_result).
-
-  " Verify aggregations
-  cl_abap_unit_assert=>assert_equals(
-    exp = 3
-    act = lt_result[ 1 ]-numberofbookings
-    msg = 'Should have 3 bookings' ).
-
-  cl_abap_unit_assert=>assert_equals(
-    exp = '6000.00'
-    act = lt_result[ 1 ]-totalrevenue
-    msg = 'Total revenue should be 6000.00' ).
-ENDMETHOD.
-```
-
-### Testing CDS Views that Select from Another CDS View
-
-> **Note:** This pattern applies when your design **already has** a CDS view that selects from another CDS view. It does NOT mean you should split a single view into two — use a single CDS view with GROUP BY / JOIN when the business logic fits.
-
-When your CDS view selects from **another CDS view** (not a base table), `create` will raise `CX_CDS_FAILURE`. Use `create_for_multiple_cds` instead and list all CDS entities in the dependency chain.
-
-```abap
-METHOD class_setup.
-  " ZC_TopView selects from ZC_IntermediateView (another CDS view entity)
-  " → must use create_for_multiple_cds and list all CDS entities
-  mo_cds_env_static = cl_cds_test_environment=>create_for_multiple_cds(
-    i_for_entities = VALUE #(
-      ( 'ZC_TOPVIEW' )           " the view under test
-      ( 'ZC_INTERMEDIATEVIEW' )  " the CDS view it selects from
-    ) ).
-ENDMETHOD.
-```
-
-Insert test data into the intermediate CDS view (not the base tables), since that is what the top-level view reads:
-
-```abap
-METHOD test_read.
-  DATA lt_source TYPE TABLE OF zc_intermediateview WITH EMPTY KEY.
-  lt_source = VALUE #(
-    ( field1 = 'A' field2 = 100 )
-    ( field1 = 'B' field2 = 200 ) ).
-  mo_cds_env->insert_test_data( i_data = lt_source ).
-
-  SELECT * FROM zc_topview INTO TABLE @DATA(lt_result).
-
-  cl_abap_unit_assert=>assert_equals(
-    exp = 2  act = lines( lt_result )  msg = 'Expected 2 rows' ).
-ENDMETHOD.
-```
-
-**Rules:**
-- List the view under test **and all CDS views it depends on** in `i_for_entities`
-- Insert data into the **direct source** of the top-level view (the intermediate CDS view)
-- Order in `i_for_entities` does not matter
-- If you get `CX_CDS_FAILURE` when using `create`, switch to `create_for_multiple_cds`
-
----
-
-### Key Classes for CDS Testing
-
-| Item | Type/Usage |
-|------|------------|
-| `CL_CDS_TEST_ENVIRONMENT` | Class with `CREATE` method |
-| `IF_CDS_TEST_ENVIRONMENT` | Interface (CREATE returns this type) |
-| `CLASS-METHODS` | `class_setup` and `class_teardown` must be static methods |
-| `CL_OSQL_TEST_ENVIRONMENT` | Test doubles for database tables (use for aggregations) |
-| `CL_ABAP_UNIT_ASSERT` | Assertions |
-
-### Key Methods
-
-| Method | Purpose |
-|--------|---------|
-| `CL_CDS_TEST_ENVIRONMENT=>create( i_for_entity = ... )` | Create test environment for a CDS view over base tables |
-| `CL_CDS_TEST_ENVIRONMENT=>create_for_multiple_cds( i_for_entities = ... )` | Create test environment when the CDS view selects from another CDS view |
-| `insert_test_data( i_data = ... )` | Insert test data into test doubles |
-| `clear_doubles` | Clear test data before each test method |
-| `destroy` | Clean up after test class |
-
-### Important Usage Notes
-
-1. **Use interface type**: `DATA mo_cds_env TYPE REF TO if_cds_test_environment` - the CREATE method returns an interface reference
-2. **CLASS-METHODS required**: `class_setup` and `class_teardown` must be declared with `CLASS-METHODS` (not `METHODS`)
-3. **Table type declaration**: Must declare `DATA lt_tab TYPE TABLE OF <type> WITH EMPTY KEY` before using `VALUE #()`
-4. **Auto-created dependencies**: When the CDS view selects only from **base tables**, the framework auto-creates test doubles — do not specify `i_dependency_list`. When the CDS view selects from **another CDS view**, use `create_for_multiple_cds` instead (see section below).
-5. **Aggregations**: For CDS views with SUM/COUNT/GROUP BY, insert test data into base tables (SFLIGHT, SCARR, etc.)
-6. **Clear doubles**: Call `clear_doubles` in `setup` method before each test
-7. **Enable associations**: Set `test_associations = 'X'` only if testing CDS associations
-8. **Exception handling**: Declare test methods with `RAISING cx_static_check` for proper exception handling
-
-### Search Reference for More Details
+For full CDS test double patterns (basic setup, aggregations, CDS-on-CDS), see:
 
 ```bash
-abapgit-agent ref "cl_cds_test_environment"
-abapgit-agent ref --topic unit-tests
+abapgit-agent ref --topic cds-testing
 ```
 
 ---

package/abap/guidelines/unit-testable-code.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Unit Testable Code
-nav_order: 13
+nav_order: 8
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/workflow-detailed.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Development Workflow (Detailed)
-nav_order: 18
+nav_order: 21
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "abapgit-agent",
-  "version": "1.15.1",
+  "version": "1.15.3",
   "description": "ABAP Git Agent - Pull and activate ABAP code via abapGit from any git repository",
   "files": [
     "bin/",