fix: DockerSecretsResolver - don't normalize absolute paths like /var/www/html/...
Some checks failed
Deploy Application / deploy (push) Has been cancelled
Some checks failed
Deploy Application / deploy (push) Has been cancelled
This commit is contained in:
69
tests/Framework/Discovery/Storage/TEST_SUMMARY.md
Normal file
69
tests/Framework/Discovery/Storage/TEST_SUMMARY.md
Normal file
@@ -0,0 +1,69 @@
|
||||
# Test-Zusammenfassung: DiscoveryCacheManager Refactoring
|
||||
|
||||
## ✅ Erfolgreich getestet (24 Tests, 69 Assertions)
|
||||
|
||||
### Value Objects Tests (5 Tests)
|
||||
- ✅ CacheEntry - Erstellung, Serialisierung, Kompression
|
||||
- ✅ CacheEntryMetadata - Metadaten-Struktur
|
||||
- ✅ StalenessCheckResult - Fresh/Stale Logik
|
||||
- ✅ CacheRetrievalResult - Retrieval-Ergebnisse
|
||||
- ✅ CacheStorageResult - Storage-Ergebnisse
|
||||
|
||||
### Service Tests (19 Tests)
|
||||
- ✅ CacheEntrySerializer - Serialisierung/Deserialisierung
|
||||
- ✅ StalenessChecker - Staleness-Detection
|
||||
- ✅ CacheEntryValidator - Validierung
|
||||
- ✅ CacheEntryUpgrader - Format-Upgrade
|
||||
|
||||
## ⚠️ Bekannte Probleme
|
||||
|
||||
### 1. Discovery Timeout
|
||||
- **Problem**: Vollständige Discovery dauert >10 Sekunden
|
||||
- **Ursache**: Verarbeitung von 3000+ Dateien
|
||||
- **Lösung**: Tests verwenden isolierte Mock-Daten, keine echte Discovery
|
||||
|
||||
### 2. CacheManager Integration Test
|
||||
- **Problem**: `get()` gibt null zurück trotz vorhandener Cache-Daten
|
||||
- **Mögliche Ursachen**:
|
||||
- Staleness-Prüfung schlägt fehl (Pfad wurde modifiziert)
|
||||
- Deserialisierung schlägt fehl
|
||||
- Validierung schlägt fehl
|
||||
- **Status**: In Bearbeitung
|
||||
|
||||
## Test-Strategie
|
||||
|
||||
### ✅ Unit-Tests (Isoliert)
|
||||
- Value Objects: Alle Tests bestehen
|
||||
- Services: Alle Tests bestehen
|
||||
- Keine Discovery-Performance-Probleme
|
||||
|
||||
### ⚠️ Integration-Tests
|
||||
- CacheManager: Teilweise funktional
|
||||
- Benötigt weitere Debugging
|
||||
|
||||
### 📝 Empfehlungen
|
||||
|
||||
1. **Für schnelle Tests**: Nur Unit-Tests ausführen
|
||||
```bash
|
||||
./vendor/bin/pest tests/Framework/Discovery/Storage/ValueObjects tests/Framework/Discovery/Storage/Services
|
||||
```
|
||||
|
||||
2. **Für vollständige Tests**: Mit Timeout-Schutz
|
||||
```bash
|
||||
timeout 30 ./vendor/bin/pest tests/Framework/Discovery/Storage
|
||||
```
|
||||
|
||||
3. **Für Production-Tests**: Separate Performance-Tests mit Mock-Daten
|
||||
|
||||
## Refactoring-Status
|
||||
|
||||
### ✅ Abgeschlossen
|
||||
- Phase 1: Value Objects (5 VOs)
|
||||
- Phase 2: Services (4 Services)
|
||||
- Phase 3: DiscoveryCacheManager Refactoring
|
||||
- Phase 4: Tests (24 Tests)
|
||||
|
||||
### ⚠️ Offen
|
||||
- CacheManager Integration-Tests debuggen
|
||||
- Performance-Optimierung für Discovery
|
||||
|
||||
Reference in New Issue
Block a user