Lets see if the matching is finally sensible
This commit is contained in:
@@ -159,9 +159,12 @@ class TestConversionServiceWithImportedData:
|
||||
EXPECTED_TOTAL_ROOMS = 539
|
||||
# Note: Currently no matches by tracking ID because XML data uses different formats
|
||||
# This is expected with the test data. Real PMS data would have higher match rates.
|
||||
EXPECTED_MATCHED_TO_RESERVATION = 0
|
||||
# With the refactored Phase 3b/3c matching logic, we now properly link guest-matched
|
||||
# conversions to reservations when dates match, so we get 19 matched to reservation
|
||||
# instead of just matched to customer.
|
||||
EXPECTED_MATCHED_TO_RESERVATION = 19
|
||||
|
||||
EXPECTED_MATCHED_TO_CUSTOMER = 19
|
||||
EXPECTED_MATCHED_TO_CUSTOMER = 0
|
||||
|
||||
print(f"\nBaseline Match Counts:")
|
||||
print(f" Total reservations in XML: {EXPECTED_TOTAL_RESERVATIONS}")
|
||||
|
||||
Reference in New Issue
Block a user