1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
|
description: "no-heartbeat-command-logs"
schemaVersion: "1.13"
# no heartbeats in load balanced mode.
runOnRequirements:
- topologies:
- single
- replicaset
- sharded
tests:
- description: "Heartbeat commands should not generate log messages"
operations:
- name: createEntities
object: testRunner
arguments:
entities:
- client:
id: &client client
observeLogMessages:
command: debug
observeEvents:
- serverDescriptionChangedEvent
- database:
id: &database database
client: *client
databaseName: &databaseName logging-tests
- name: waitForEvent
object: testRunner
arguments:
client: *client
event:
# a server description change implies that a heartbeat has happened.
serverDescriptionChangedEvent: {}
count: 1
- name: runCommand
object: *database
arguments:
command: { ping: 1 }
commandName: &commandName ping
expectLogMessages:
# since the ping happens after the heartbeat, seeing events for only the ping
# implies the driver did not emit a log message for the heartbeat.
- client: *client
messages:
- level: debug
component: command
data:
message: "Command started"
databaseName: *databaseName
commandName: *commandName
- level: debug
component: command
data:
message: "Command succeeded"
commandName: *commandName
|