You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional, session test specific operations are documented here:
37
-
38
-
assertDifferentLsidOnLastTwoCommands
39
-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
40
-
41
-
The "assertDifferentLsidOnLastTwoCommands" operation instructs the test runner
42
-
to assert that the last two command started events from the test's MongoClient
43
-
have different "lsid" fields. This assertion is used to ensure that dirty
44
-
server sessions are discarded from the pool::
45
-
46
-
- name: assertDifferentLsidOnLastTwoCommands
47
-
object: testRunner
48
-
49
-
assertSameLsidOnLastTwoCommands
50
-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
51
-
52
-
The "assertSameLsidOnLastTwoCommands" operation instructs the test runner
53
-
to assert that the last two command started events from the test's MongoClient
54
-
have the same "lsid" field. This assertion is used to ensure that non-dirty
55
-
server sessions are not discarded from the pool::
56
-
57
-
- name: assertSameLsidOnLastTwoCommands
58
-
object: testRunner
59
-
60
-
assertSessionDirty
61
-
~~~~~~~~~~~~~~~~~~
62
-
63
-
The "assertSessionDirty" operation instructs the test runner to assert that
64
-
the given session is marked dirty::
65
-
66
-
- name: assertSessionDirty
67
-
object: testRunner
68
-
arguments:
69
-
session: session0
70
-
71
-
assertSessionNotDirty
72
-
~~~~~~~~~~~~~~~~~~~~~
73
-
74
-
The "assertSessionNotDirty" operation instructs the test runner to assert that
75
-
the given session is *not* marked dirty::
76
-
77
-
- name: assertSessionNotDirty
78
-
object: testRunner
79
-
arguments:
80
-
session: session0
81
-
82
20
Snapshot session tests
83
21
======================
84
-
Snapshot sessions tests require server of version 5.0 or higher and
22
+
Snapshot sessions tests require server of version 5.0 or higher and
85
23
replica set or a sharded cluster deployment.
86
24
Default snapshot history window on the server is 5 minutes. Running the test in debug mode, or in any other slow configuration
87
25
may lead to `SnapshotTooOld` errors. Drivers can work around this issue by increasing the server's `minSnapshotHistoryWindowInSeconds` parameter, for example:
@@ -92,13 +30,17 @@ may lead to `SnapshotTooOld` errors. Drivers can work around this issue by incre
92
30
93
31
Prose tests
94
32
```````````
95
-
- Setting both ``snapshot`` and ``causalConsistency`` is not allowed
0 commit comments