[COMPASS-6615] Investigate changes in NODE-4685: Easier debugging with standardized logging: logging specification Created: 17/Mar/23  Updated: 05/Apr/23

Status: Open
Project: Compass
Component/s: Logging
Affects Version/s: None
Fix Version/s: None

Type: Investigation Priority: Major - P3
Reporter: PM Bot Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: node-driver
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on NODE-4685 Easier debugging with standardized lo... Closed
Story Points: 8

 Description   

This ticket was split from DRIVERS-1677, please see that ticket for a detailed description.

This ticket is meant to implement changes to Unified spec test runner to support logging in order to
facilitate the rest of the work for NODE-3974.

Unknowns

  • What exactly should the failures for the CLAM spec tests look like?
    • See Testing Requirements

Acceptance Criteria

Implementation Requirements

  • Implement new operators
    • Implement $$matchAsRoot operator
    • Implement $$matchAsDocument operator
  • Implement matching and interpretation of new properties
    • Implement expectLogMessages property
    • Implement expectedLogMessages property
    • Implement expectedLogMessagesForClient property
    • Implement observeLogMessages property
  • Stub out mechanism for UnifiedMongoClient to be able to collect logs from MongoLogger

Testing Requirements

  • Pull in the CLAM spec tests
  • Ensure that CLAM spec tests fail for "right reasons"
    • For tests that check for log messages using the new matching operators/properties, the tests should fail on the absence of the expected log messages and not because the test runner fails to recognize the new operators/properties.
  • Add unit tests for $$matchAsRoot and $$matchAsDocument operators

Generated at Wed Feb 07 22:43:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.