Add tests for Kommunikation Sync implementation and verification scripts
- Implemented comprehensive tests for the Kommunikation Sync functionality, covering base64 encoding, marker parsing, creation, type detection, and integration scenarios. - Added a verification script to check for unique IDs in Advoware communications, ensuring stability and integrity of the IDs. - Created utility scripts for code validation, notification testing, and PUT response detail analysis to enhance development and testing processes. - Updated README with details on new tools and their usage.
This commit is contained in:
@@ -1,296 +1,155 @@
|
||||
# Beteiligte Structure Comparison Tool
|
||||
# Scripts
|
||||
|
||||
## Purpose
|
||||
Test- und Utility-Scripts für das Motia BitByLaw Projekt.
|
||||
|
||||
This helper script fetches entity data from both **EspoCRM** and **Advoware** to compare their data structures. This helps understand:
|
||||
## Struktur
|
||||
|
||||
- What fields exist in each system
|
||||
- How field names differ
|
||||
- Potential field mappings for synchronization
|
||||
- Data type differences
|
||||
```
|
||||
scripts/
|
||||
├── beteiligte_sync/ # Beteiligte (Stammdaten) Sync Tests
|
||||
│ ├── test_beteiligte_sync.py
|
||||
│ ├── compare_beteiligte.py
|
||||
│ └── README.md
|
||||
│
|
||||
├── kommunikation_sync/ # Kommunikation (Phone/Email) Sync Tests
|
||||
│ ├── test_kommunikation_api.py
|
||||
│ ├── test_kommunikation_sync_implementation.py
|
||||
│ ├── test_kommunikation_matching_strategy.py
|
||||
│ ├── test_kommunikation_kommkz_deep.py
|
||||
│ ├── test_kommunikation_readonly.py
|
||||
│ ├── test_kommart_values.py
|
||||
│ ├── verify_advoware_kommunikation_ids.py
|
||||
│ └── README.md
|
||||
│
|
||||
├── adressen_sync/ # Adressen Sync Tests (geplant)
|
||||
│ ├── test_adressen_api.py
|
||||
│ ├── test_adressen_sync.py
|
||||
│ ├── test_adressen_delete_matching.py
|
||||
│ ├── test_hauptadresse_*.py
|
||||
│ └── README.md
|
||||
│
|
||||
├── espocrm_tests/ # EspoCRM API Tests
|
||||
│ ├── test_espocrm_kommunikation.py
|
||||
│ ├── test_espocrm_phone_email_entities.py
|
||||
│ ├── test_espocrm_hidden_ids.py
|
||||
│ └── README.md
|
||||
│
|
||||
├── analysis/ # Debug & Analyse Scripts
|
||||
│ ├── analyze_beteiligte_endpoint.py
|
||||
│ ├── analyze_sync_issues_104860.py
|
||||
│ ├── compare_entities_104860.py
|
||||
│ └── README.md
|
||||
│
|
||||
├── calendar_sync/ # Calendar Sync Utilities
|
||||
│ ├── delete_all_calendars.py
|
||||
│ ├── delete_employee_locks.py
|
||||
│ └── README.md
|
||||
│
|
||||
└── tools/ # Allgemeine Utilities
|
||||
├── validate_code.py
|
||||
├── test_notification.py
|
||||
├── test_put_response_detail.py
|
||||
└── README.md
|
||||
```
|
||||
|
||||
## Usage
|
||||
## Kategorien
|
||||
|
||||
### 1. Beteiligte Sync ([beteiligte_sync/](beteiligte_sync/))
|
||||
Tests für Stammdaten-Synchronisation zwischen EspoCRM und Advoware.
|
||||
- rowId-basierte Change Detection
|
||||
- CREATE/UPDATE/DELETE Operations
|
||||
- Timestamp-Vergleiche & Konflikt-Handling
|
||||
|
||||
### 2. Kommunikation Sync ([kommunikation_sync/](kommunikation_sync/))
|
||||
Tests für Phone/Email/Fax Synchronisation.
|
||||
- Hash-basierte Change Detection
|
||||
- Base64-Marker System
|
||||
- 6 Sync-Varianten (Var1-6)
|
||||
- Empty Slots (DELETE-Workaround)
|
||||
|
||||
### 3. Adressen Sync ([adressen_sync/](adressen_sync/))
|
||||
⚠️ **Noch nicht implementiert** - API-Analyse Scripts
|
||||
- API-Limitierungen Tests
|
||||
- READ-ONLY Felder Identifikation
|
||||
- Hauptadressen-Logik
|
||||
|
||||
### 4. EspoCRM Tests ([espocrm_tests/](espocrm_tests/))
|
||||
Tests für EspoCRM Custom Entities.
|
||||
- CBeteiligte Structure Tests
|
||||
- Kommunikation Arrays
|
||||
- Sub-Entity Relationships
|
||||
|
||||
### 5. Analysis ([analysis/](analysis/))
|
||||
Debug & Analyse Scripts für spezifische Probleme.
|
||||
- Endpoint-Analyse
|
||||
- Entity-Vergleiche
|
||||
- Sync-Issue Debugging
|
||||
|
||||
### 6. Calendar Sync ([calendar_sync/](calendar_sync/))
|
||||
Utilities für Google Calendar Sync Management.
|
||||
- Calendar Cleanup
|
||||
- Lock Management
|
||||
|
||||
### 7. Tools ([tools/](tools/))
|
||||
Allgemeine Entwickler-Tools.
|
||||
- Code Validation
|
||||
- Notification Tests
|
||||
- Response Analysis
|
||||
|
||||
## Quick Start
|
||||
|
||||
### Beteiligte Sync testen
|
||||
```bash
|
||||
cd /opt/motia-app
|
||||
|
||||
# Basic usage: Compare by EspoCRM ID (will auto-search in Advoware)
|
||||
python bitbylaw/scripts/compare_beteiligte.py <espocrm_entity_id>
|
||||
|
||||
# Advanced: Specify both IDs
|
||||
python bitbylaw/scripts/compare_beteiligte.py <espocrm_entity_id> <advoware_id>
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/beteiligte_sync/test_beteiligte_sync.py
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
### Kommunikation Sync testen
|
||||
```bash
|
||||
# Example 1: Fetch from EspoCRM and search in Advoware by name
|
||||
python bitbylaw/scripts/compare_beteiligte.py 64a3f2b8c9e1234567890abc
|
||||
|
||||
# Example 2: Fetch from both systems by ID
|
||||
python bitbylaw/scripts/compare_beteiligte.py 64a3f2b8c9e1234567890abc 12345
|
||||
|
||||
# Example 3: Using the virtual environment
|
||||
source python_modules/bin/activate
|
||||
python bitbylaw/scripts/compare_beteiligte.py 64a3f2b8c9e1234567890abc
|
||||
python scripts/kommunikation_sync/test_kommunikation_api.py
|
||||
python scripts/kommunikation_sync/test_kommunikation_sync_implementation.py
|
||||
```
|
||||
|
||||
## Requirements
|
||||
|
||||
### Environment Variables
|
||||
|
||||
Make sure these are set in `.env` or environment:
|
||||
|
||||
### Code validieren
|
||||
```bash
|
||||
# EspoCRM
|
||||
ESPOCRM_API_BASE_URL=https://crm.bitbylaw.com/api/v1
|
||||
ESPOCRM_MARVIN_API_KEY=your_api_key_here
|
||||
|
||||
# Advoware
|
||||
ADVOWARE_API_BASE_URL=https://www2.advo-net.net:90/
|
||||
ADVOWARE_API_KEY=your_base64_encoded_key
|
||||
ADVOWARE_USER=your_user
|
||||
ADVOWARE_PASSWORD=your_password
|
||||
ADVOWARE_KANZLEI=your_kanzlei
|
||||
ADVOWARE_DATABASE=your_database
|
||||
# ... (see config.py for all required vars)
|
||||
python scripts/tools/validate_code.py services/kommunikation_sync_utils.py
|
||||
```
|
||||
|
||||
### Dependencies
|
||||
|
||||
### Entity vergleichen
|
||||
```bash
|
||||
pip install aiohttp redis python-dotenv requests
|
||||
python scripts/beteiligte_sync/compare_beteiligte.py --entity-id <espo_id> --betnr <advo_betnr>
|
||||
```
|
||||
|
||||
## Output
|
||||
## Dokumentation
|
||||
|
||||
The script produces:
|
||||
**Hauptdokumentation**: [../docs/SYNC_OVERVIEW.md](../docs/SYNC_OVERVIEW.md)
|
||||
|
||||
### 1. Console Output
|
||||
Für detaillierte Informationen zu jedem Script siehe die README.md in den jeweiligen Unterordnern:
|
||||
- [beteiligte_sync/README.md](beteiligte_sync/README.md)
|
||||
- [kommunikation_sync/README.md](kommunikation_sync/README.md)
|
||||
- [adressen_sync/README.md](adressen_sync/README.md)
|
||||
- [espocrm_tests/README.md](espocrm_tests/README.md)
|
||||
- [analysis/README.md](analysis/README.md)
|
||||
- [calendar_sync/README.md](calendar_sync/README.md)
|
||||
- [tools/README.md](tools/README.md)
|
||||
|
||||
```
|
||||
================================================================================
|
||||
BETEILIGTE STRUCTURE COMPARISON TOOL
|
||||
================================================================================
|
||||
## Konventionen
|
||||
|
||||
EspoCRM Entity ID: 64a3f2b8c9e1234567890abc
|
||||
|
||||
Environment Check:
|
||||
----------------------------------------
|
||||
ESPOCRM_API_BASE_URL: https://crm.bitbylaw.com/api/v1
|
||||
ESPOCRM_API_KEY: ✓ Set
|
||||
ADVOWARE_API_BASE_URL: https://www2.advo-net.net:90/
|
||||
ADVOWARE_API_KEY: ✓ Set
|
||||
|
||||
================================================================================
|
||||
ESPOCRM - Fetching Beteiligter
|
||||
================================================================================
|
||||
|
||||
Trying entity type: Beteiligte
|
||||
|
||||
✓ Success! Found in Beteiligte
|
||||
|
||||
Entity Structure:
|
||||
--------------------------------------------------------------------------------
|
||||
{
|
||||
"id": "64a3f2b8c9e1234567890abc",
|
||||
"name": "Max Mustermann",
|
||||
"firstName": "Max",
|
||||
"lastName": "Mustermann",
|
||||
"email": "max@example.com",
|
||||
"phone": "+49123456789",
|
||||
...
|
||||
}
|
||||
|
||||
================================================================================
|
||||
ADVOWARE - Fetching Beteiligter
|
||||
================================================================================
|
||||
|
||||
Searching by name: Max Mustermann
|
||||
Trying endpoint: /contacts
|
||||
|
||||
✓ Found 2 results
|
||||
|
||||
Search Results:
|
||||
--------------------------------------------------------------------------------
|
||||
[
|
||||
{
|
||||
"id": 12345,
|
||||
"full_name": "Max Mustermann",
|
||||
"email": "max@example.com",
|
||||
...
|
||||
}
|
||||
]
|
||||
|
||||
================================================================================
|
||||
STRUCTURE COMPARISON
|
||||
================================================================================
|
||||
|
||||
EspoCRM Fields (25):
|
||||
----------------------------------------
|
||||
id (str)
|
||||
name (str)
|
||||
firstName (str)
|
||||
lastName (str)
|
||||
email (str)
|
||||
phone (str)
|
||||
...
|
||||
|
||||
Advoware Fields (30):
|
||||
----------------------------------------
|
||||
id (int)
|
||||
full_name (str)
|
||||
email (str)
|
||||
phone_number (str)
|
||||
...
|
||||
|
||||
Common Fields (5):
|
||||
----------------------------------------
|
||||
✓ id
|
||||
✓ email
|
||||
✗ phone
|
||||
EspoCRM: +49123456789
|
||||
Advoware: 0123456789
|
||||
|
||||
EspoCRM Only (20):
|
||||
----------------------------------------
|
||||
firstName
|
||||
lastName
|
||||
...
|
||||
|
||||
Advoware Only (25):
|
||||
----------------------------------------
|
||||
full_name
|
||||
phone_number
|
||||
...
|
||||
|
||||
Potential Field Mappings:
|
||||
----------------------------------------
|
||||
firstName → first_name
|
||||
lastName → last_name
|
||||
email → email
|
||||
phone → phone_number
|
||||
...
|
||||
|
||||
================================================================================
|
||||
Comparison saved to: /opt/motia-app/bitbylaw/scripts/beteiligte_comparison_result.json
|
||||
================================================================================
|
||||
```
|
||||
|
||||
### 2. JSON Output File
|
||||
|
||||
Saved to `bitbylaw/scripts/beteiligte_comparison_result.json`:
|
||||
|
||||
```json
|
||||
{
|
||||
"espocrm_data": {
|
||||
"id": "64a3f2b8c9e1234567890abc",
|
||||
"name": "Max Mustermann",
|
||||
...
|
||||
},
|
||||
"advoware_data": {
|
||||
"id": 12345,
|
||||
"full_name": "Max Mustermann",
|
||||
...
|
||||
},
|
||||
"comparison": {
|
||||
"espo_fields": ["id", "name", "firstName", ...],
|
||||
"advo_fields": ["id", "full_name", "email", ...],
|
||||
"common": ["id", "email"],
|
||||
"espo_only": ["firstName", "lastName", ...],
|
||||
"advo_only": ["full_name", "phone_number", ...],
|
||||
"suggested_mappings": [
|
||||
["firstName", "first_name"],
|
||||
["lastName", "last_name"],
|
||||
...
|
||||
]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## How It Works
|
||||
|
||||
### 1. EspoCRM Fetch
|
||||
|
||||
The script tries multiple entity types to find the data:
|
||||
- `Beteiligte` (custom VMH entity)
|
||||
- `Contact` (standard)
|
||||
- `Account` (standard)
|
||||
- `Lead` (standard)
|
||||
|
||||
### 2. Advoware Fetch
|
||||
|
||||
**By ID (if provided):**
|
||||
- Tries: `/contacts/{id}`, `/parties/{id}`, `/clients/{id}`
|
||||
|
||||
**By Name (if EspoCRM data available):**
|
||||
- Searches: `/contacts?search=...`, `/parties?search=...`, `/clients?search=...`
|
||||
|
||||
### 3. Comparison
|
||||
|
||||
- Lists all fields from both systems
|
||||
- Identifies common fields (same name)
|
||||
- Shows values for common fields
|
||||
- Suggests mappings based on naming patterns
|
||||
- Exports full comparison to JSON
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### "ESPOCRM_API_KEY not set"
|
||||
### Naming
|
||||
- `test_*.py` - Test-Scripts
|
||||
- `analyze_*.py` - Analyse-Scripts
|
||||
- `compare_*.py` - Vergleichs-Scripts
|
||||
- `verify_*.py` - Verifikations-Scripts
|
||||
|
||||
### Ausführung
|
||||
Alle Scripts sollten aus dem Projekt-Root ausgeführt werden:
|
||||
```bash
|
||||
# Check if .env exists and has the key
|
||||
cat .env | grep ESPOCRM_MARVIN_API_KEY
|
||||
|
||||
# Or set it manually
|
||||
export ESPOCRM_MARVIN_API_KEY=your_key_here
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/<category>/<script>.py
|
||||
```
|
||||
|
||||
### "Authentication failed - check API key"
|
||||
|
||||
1. Verify API key in EspoCRM admin panel
|
||||
2. Check API User permissions
|
||||
3. Ensure API User has access to entity type
|
||||
|
||||
### "Entity not found"
|
||||
|
||||
- Check if entity ID is correct
|
||||
- Verify entity type exists in EspoCRM
|
||||
- Check API User permissions for that entity
|
||||
|
||||
### "Advoware token error"
|
||||
|
||||
- Verify all Advoware credentials in `.env`
|
||||
- Check HMAC signature generation
|
||||
- Ensure API key is base64 encoded
|
||||
- Test token generation separately
|
||||
|
||||
## Next Steps
|
||||
|
||||
After running this script:
|
||||
|
||||
1. **Review JSON output** - Check `beteiligte_comparison_result.json`
|
||||
2. **Define mappings** - Create mapping table based on suggestions
|
||||
3. **Implement mapper** - Create transformation functions
|
||||
4. **Test sync** - Use mappings in sync event step
|
||||
|
||||
Example mapping implementation:
|
||||
|
||||
```python
|
||||
def map_espocrm_to_advoware(espo_entity: dict) -> dict:
|
||||
"""Transform EspoCRM Beteiligter to Advoware format"""
|
||||
return {
|
||||
'first_name': espo_entity.get('firstName'),
|
||||
'last_name': espo_entity.get('lastName'),
|
||||
'email': espo_entity.get('email'),
|
||||
'phone_number': espo_entity.get('phone'),
|
||||
# Add more mappings based on comparison...
|
||||
}
|
||||
```
|
||||
|
||||
## Related Files
|
||||
|
||||
- [services/espocrm.py](../services/espocrm.py) - EspoCRM API client
|
||||
- [services/advoware.py](../services/advoware.py) - Advoware API client
|
||||
- [services/ESPOCRM_SERVICE.md](../services/ESPOCRM_SERVICE.md) - EspoCRM docs
|
||||
- [config.py](../config.py) - Configuration
|
||||
### Umgebung
|
||||
Scripts verwenden die gleiche `.env` wie die Hauptapplikation:
|
||||
- `ADVOWARE_API_*` - Advoware API Config
|
||||
- `ESPOCRM_API_*` - EspoCRM API Config
|
||||
- `REDIS_*` - Redis Config
|
||||
|
||||
68
bitbylaw/scripts/adressen_sync/README.md
Normal file
68
bitbylaw/scripts/adressen_sync/README.md
Normal file
@@ -0,0 +1,68 @@
|
||||
# Adressen Sync - Test Scripts
|
||||
|
||||
Test-Scripts für die Adressen-Synchronisation (geplant).
|
||||
|
||||
## Scripts
|
||||
|
||||
### test_adressen_api.py
|
||||
Vollständiger API-Test für Advoware Adressen-Endpoints.
|
||||
|
||||
**Testet:**
|
||||
- POST /Adressen (CREATE) - alle 11 Felder
|
||||
- PUT /Adressen (UPDATE) - nur 4 R/W Felder
|
||||
- DELETE /Adressen (gibt 403)
|
||||
- READ-ONLY Felder (land, postfach, standardAnschrift, etc.)
|
||||
|
||||
### test_adressen_sync.py
|
||||
Test der Sync-Funktionalität (Prototype).
|
||||
|
||||
### test_adressen_delete_matching.py
|
||||
Test für DELETE-Matching Strategien.
|
||||
|
||||
**Testet:**
|
||||
- bemerkung als Matching-Methode
|
||||
- reihenfolgeIndex Stabilität
|
||||
|
||||
### test_adressen_deactivate_ordering.py
|
||||
Test für Adress-Reihenfolge Management.
|
||||
|
||||
### test_adressen_gueltigbis_modify.py
|
||||
Test für gueltigBis/gueltigVon Handling.
|
||||
|
||||
**Testet:**
|
||||
- gueltigBis ist READ-ONLY (kann nicht geändert werden)
|
||||
- Soft-Delete Strategien
|
||||
|
||||
### test_adressen_nullen.py
|
||||
Test für NULL-Value Handling.
|
||||
|
||||
### test_hauptadresse_logic.py
|
||||
Test für Hauptadressen-Logik.
|
||||
|
||||
**Testet:**
|
||||
- standardAnschrift Flag
|
||||
- Automatische Hauptadressen-Erkennung
|
||||
|
||||
### test_hauptadresse_explizit.py
|
||||
Test für explizite Hauptadressen-Setzung.
|
||||
|
||||
### test_find_hauptadresse.py
|
||||
Helper zum Finden der Hauptadresse.
|
||||
|
||||
## Status
|
||||
|
||||
⚠️ **Adressen Sync ist noch nicht implementiert.**
|
||||
|
||||
Diese Test-Scripts wurden während der API-Analyse erstellt.
|
||||
|
||||
## Verwendung
|
||||
|
||||
```bash
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/adressen_sync/test_adressen_api.py
|
||||
```
|
||||
|
||||
## Verwandte Dokumentation
|
||||
|
||||
- [../../docs/archive/ADRESSEN_SYNC_ANALYSE.md](../../docs/archive/ADRESSEN_SYNC_ANALYSE.md) - Detaillierte API-Analyse
|
||||
- [../../docs/archive/ADRESSEN_SYNC_SUMMARY.md](../../docs/archive/ADRESSEN_SYNC_SUMMARY.md) - Zusammenfassung
|
||||
41
bitbylaw/scripts/analysis/README.md
Normal file
41
bitbylaw/scripts/analysis/README.md
Normal file
@@ -0,0 +1,41 @@
|
||||
# Analysis Scripts
|
||||
|
||||
Scripts für Analyse und Debugging von Sync-Problemen.
|
||||
|
||||
## Scripts
|
||||
|
||||
### analyze_beteiligte_endpoint.py
|
||||
Analysiert Beteiligte-Endpoint in Advoware.
|
||||
|
||||
**Features:**
|
||||
- Field-Analyse (funktionierende vs. ignorierte Felder)
|
||||
- Response-Structure Analyse
|
||||
- Edge-Case Testing
|
||||
|
||||
### analyze_sync_issues_104860.py
|
||||
Spezifische Analyse für Entity 104860 Sync-Probleme.
|
||||
|
||||
**Analysiert:**
|
||||
- Sync-Status Historie
|
||||
- Timestamp-Vergleiche
|
||||
- Konflikt-Erkennung
|
||||
- Hash-Berechnung
|
||||
|
||||
### compare_entities_104860.py
|
||||
Detaillierter Vergleich von Entity 104860 zwischen Systemen.
|
||||
|
||||
**Features:**
|
||||
- Field-by-Field Diff
|
||||
- Kommunikation-Arrays Vergleich
|
||||
- Marker-Analyse
|
||||
|
||||
## Verwendung
|
||||
|
||||
```bash
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/analysis/analyze_sync_issues_104860.py
|
||||
```
|
||||
|
||||
## Zweck
|
||||
|
||||
Diese Scripts wurden erstellt, um spezifische Sync-Probleme zu debuggen und die API-Charakteristiken zu verstehen.
|
||||
39
bitbylaw/scripts/beteiligte_sync/README.md
Normal file
39
bitbylaw/scripts/beteiligte_sync/README.md
Normal file
@@ -0,0 +1,39 @@
|
||||
# Beteiligte Sync - Test Scripts
|
||||
|
||||
Test-Scripts für die Beteiligte (Stammdaten) Synchronisation zwischen EspoCRM und Advoware.
|
||||
|
||||
## Scripts
|
||||
|
||||
### test_beteiligte_sync.py
|
||||
Vollständiger Test der Beteiligte-Sync Funktionalität.
|
||||
|
||||
**Testet:**
|
||||
- CREATE: Neu in EspoCRM → POST zu Advoware
|
||||
- UPDATE: Änderung in EspoCRM → PUT zu Advoware
|
||||
- Timestamp-Vergleich (espocrm_newer, advoware_newer, conflict)
|
||||
- rowId-basierte Change Detection
|
||||
- Lock-Management (Redis)
|
||||
|
||||
**Verwendung:**
|
||||
```bash
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/beteiligte_sync/test_beteiligte_sync.py
|
||||
```
|
||||
|
||||
### compare_beteiligte.py
|
||||
Vergleicht Beteiligte-Daten zwischen EspoCRM und Advoware.
|
||||
|
||||
**Features:**
|
||||
- Field-by-Field Vergleich
|
||||
- Identifiziert Abweichungen
|
||||
- JSON-Output für weitere Analyse
|
||||
|
||||
**Verwendung:**
|
||||
```bash
|
||||
python scripts/beteiligte_sync/compare_beteiligte.py --entity-id <espo_id> --betnr <advo_betnr>
|
||||
```
|
||||
|
||||
## Verwandte Dokumentation
|
||||
|
||||
- [../../docs/SYNC_OVERVIEW.md](../../docs/SYNC_OVERVIEW.md#beteiligte-sync-stammdaten) - Beteiligte Sync Details
|
||||
- [../../services/beteiligte_sync_utils.py](../../services/beteiligte_sync_utils.py) - Implementierung
|
||||
45
bitbylaw/scripts/espocrm_tests/README.md
Normal file
45
bitbylaw/scripts/espocrm_tests/README.md
Normal file
@@ -0,0 +1,45 @@
|
||||
# EspoCRM API - Test Scripts
|
||||
|
||||
Test-Scripts für EspoCRM Custom Entity Tests.
|
||||
|
||||
## Scripts
|
||||
|
||||
### test_espocrm_kommunikation.py
|
||||
Test für CBeteiligte Kommunikation-Felder in EspoCRM.
|
||||
|
||||
**Testet:**
|
||||
- emailAddressData[] Struktur
|
||||
- phoneNumberData[] Struktur
|
||||
- Primary Flags
|
||||
- CRUD Operations
|
||||
|
||||
### test_espocrm_kommunikation_detail.py
|
||||
Detaillierter Test der Kommunikations-Entities.
|
||||
|
||||
### test_espocrm_phone_email_entities.py
|
||||
Test für Phone/Email Sub-Entities.
|
||||
|
||||
**Testet:**
|
||||
- Nested Entity Structure
|
||||
- Relationship Management
|
||||
- Data Consistency
|
||||
|
||||
### test_espocrm_hidden_ids.py
|
||||
Test für versteckte ID-Felder in EspoCRM.
|
||||
|
||||
### test_espocrm_id_collections.py
|
||||
Test für ID-Collection Handling.
|
||||
|
||||
### test_espocrm_id_injection.py
|
||||
Test für ID-Injection Vulnerabilities.
|
||||
|
||||
## Verwendung
|
||||
|
||||
```bash
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/espocrm_tests/test_espocrm_kommunikation.py
|
||||
```
|
||||
|
||||
## Verwandte Dokumentation
|
||||
|
||||
- [../../services/ESPOCRM_SERVICE.md](../../services/ESPOCRM_SERVICE.md) - EspoCRM API Service
|
||||
67
bitbylaw/scripts/kommunikation_sync/README.md
Normal file
67
bitbylaw/scripts/kommunikation_sync/README.md
Normal file
@@ -0,0 +1,67 @@
|
||||
# Kommunikation Sync - Test Scripts
|
||||
|
||||
Test-Scripts für die Kommunikation (Phone/Email/Fax) Synchronisation.
|
||||
|
||||
## Scripts
|
||||
|
||||
### test_kommunikation_api.py
|
||||
Vollständiger API-Test für Advoware Kommunikation-Endpoints.
|
||||
|
||||
**Testet:**
|
||||
- POST /Kommunikationen (CREATE)
|
||||
- PUT /Kommunikationen (UPDATE)
|
||||
- DELETE /Kommunikationen (gibt 403 - erwartet)
|
||||
- kommKz-Werte (1-12)
|
||||
- Alle 4 Felder (tlf, bemerkung, kommKz, online)
|
||||
|
||||
### test_kommunikation_sync_implementation.py
|
||||
Test der bidirektionalen Sync-Implementierung.
|
||||
|
||||
**Testet:**
|
||||
- 6 Sync-Varianten (Var1-6)
|
||||
- Base64-Marker System
|
||||
- Hash-basierte Change Detection
|
||||
- Empty Slots (DELETE-Workaround)
|
||||
- Konflikt-Handling
|
||||
|
||||
### test_kommunikation_matching_strategy.py
|
||||
Test verschiedener Matching-Strategien.
|
||||
|
||||
**Testet:**
|
||||
- Base64-Marker Matching
|
||||
- Value-Matching für Initial Sync
|
||||
- kommKz Detection (4-Stufen)
|
||||
- Edge Cases
|
||||
|
||||
### test_kommunikation_kommkz_deep.py
|
||||
Deep-Dive Test für kommKz-Enum.
|
||||
|
||||
**Testet:**
|
||||
- Alle 12 kommKz-Werte (TelGesch, Mobil, Email, etc.)
|
||||
- kommKz=0 Bug in GET (Advoware)
|
||||
- kommKz READ-ONLY bei PUT
|
||||
|
||||
### test_kommunikation_readonly.py
|
||||
Test für Read-Only Felder.
|
||||
|
||||
**Testet:**
|
||||
- kommKz kann bei PUT nicht geändert werden
|
||||
- Workarounds für Type-Änderungen
|
||||
|
||||
### test_kommart_values.py
|
||||
Test für kommArt vs kommKz Unterschiede.
|
||||
|
||||
### verify_advoware_kommunikation_ids.py
|
||||
Verifiziert Kommunikation-IDs zwischen Systemen.
|
||||
|
||||
## Verwendung
|
||||
|
||||
```bash
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/kommunikation_sync/test_kommunikation_api.py
|
||||
```
|
||||
|
||||
## Verwandte Dokumentation
|
||||
|
||||
- [../../docs/SYNC_OVERVIEW.md](../../docs/SYNC_OVERVIEW.md#kommunikation-sync) - Vollständige Dokumentation
|
||||
- [../../services/kommunikation_sync_utils.py](../../services/kommunikation_sync_utils.py) - Implementierung
|
||||
48
bitbylaw/scripts/tools/README.md
Normal file
48
bitbylaw/scripts/tools/README.md
Normal file
@@ -0,0 +1,48 @@
|
||||
# Tools & Utilities
|
||||
|
||||
Allgemeine Utilities für Entwicklung und Testing.
|
||||
|
||||
## Scripts
|
||||
|
||||
### validate_code.py
|
||||
Code-Validierung Tool.
|
||||
|
||||
**Features:**
|
||||
- Syntax-Check für Python Files
|
||||
- Import-Check
|
||||
- Error-Detection
|
||||
|
||||
**Verwendung:**
|
||||
```bash
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/tools/validate_code.py services/kommunikation_sync_utils.py
|
||||
python scripts/tools/validate_code.py steps/vmh/beteiligte_sync_event_step.py
|
||||
```
|
||||
|
||||
**Output:**
|
||||
```
|
||||
✅ File validated successfully: 0 Errors
|
||||
```
|
||||
|
||||
### test_notification.py
|
||||
Test für EspoCRM Notification System.
|
||||
|
||||
**Testet:**
|
||||
- Notification Creation
|
||||
- User Assignment
|
||||
- Notification Types
|
||||
|
||||
### test_put_response_detail.py
|
||||
Analysiert PUT Response Details von Advoware.
|
||||
|
||||
**Testet:**
|
||||
- Response Structure
|
||||
- rowId Changes
|
||||
- Returned Fields
|
||||
|
||||
## Verwendung
|
||||
|
||||
```bash
|
||||
cd /opt/motia-app/bitbylaw
|
||||
python scripts/tools/validate_code.py <file_path>
|
||||
```
|
||||
Reference in New Issue
Block a user