You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/INTEGRATION_TESTS.md
+64-59Lines changed: 64 additions & 59 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,42 +26,42 @@ uv sync --all-extras
26
26
27
27
Integration tests require specific environment variables to be configured. These are managed through the `.env_integration_tests` file in the project root.
28
28
29
-
### ObjectStore Integration Tests
30
-
31
-
For ObjectStore integration tests, configure the following variables in `.env_integration_tests`:
**Note**: AuditLog integration tests are cloud-only and require real SAP Audit Log Service credentials. The secret resolver automatically loads configuration from `/etc/secrets/appfnd` or environment variables - no manual configuration parsing needed in test code.
42
+
`CLOUD_SDK_CFG_ADMS_DEFAULT_URI` points the tests at the target ADM service. The other `CLOUD_SDK_CFG_ADMS_DEFAULT_*` variables hold the IAS service-binding credentials used by the SDK to fetch Bearer tokens. Tests are skipped automatically when any of these are missing.
53
43
54
-
### Destination Integration Tests
44
+
### Agent Gateway Integration Tests
55
45
56
-
For Destination integration tests, configure the following variables in `.env_integration_tests`:
46
+
Agent Gateway integration tests use the LoB agent flow via the Destination Service. Configure the following variables in `.env_integration_tests`:
57
47
58
48
```bash
59
-
# Destination Configuration
49
+
# Destination Service (required by the LoB agent flow)
**Note**: AuditLog integration tests are cloud-only and require real SAP Audit Log Service credentials. The secret resolver automatically loads configuration from `/etc/secrets/appfnd` or environment variables - no manual configuration parsing needed in test code.
88
+
77
89
### Data Anonymization Integration Tests
78
90
79
91
For Data Anonymization integration tests, configure the following variables in `.env_integration_tests`:
The destination must be configured with `ClientCertificateAuthentication` and reference a certificate bundle containing the client certificate and private key.
98
110
111
+
### Destination Integration Tests
112
+
113
+
For Destination integration tests, configure the following variables in `.env_integration_tests`:
**Note**: The test fixture automatically onboards test repositories (standard and version-enabled) at session start and cleans them up on teardown. No pre-existing repositories are required.
110
140
111
-
### ADMS Integration Tests
112
-
113
-
For ADMS (Advanced Document Management Service) integration tests, configure the following variables in `.env_integration_tests`:
`CLOUD_SDK_CFG_ADMS_DEFAULT_URI` points the tests at the target ADM service. The other `CLOUD_SDK_CFG_ADMS_DEFAULT_*` variables hold the IAS service-binding credentials used by the SDK to fetch Bearer tokens. Tests are skipped automatically when any of these are missing.
125
-
126
-
### Agent Gateway Integration Tests
141
+
### ObjectStore Integration Tests
127
142
128
-
Agent Gateway integration tests use the LoB agent flow via the Destination Service. Configure the following variables in `.env_integration_tests`:
143
+
For ObjectStore integration tests, configure the following variables in `.env_integration_tests`:
129
144
130
145
```bash
131
-
# Destination Service (required by the LoB agent flow)
0 commit comments