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
Copy file name to clipboardExpand all lines: test/spec/sessions/README.rst
+23-3Lines changed: 23 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -9,10 +9,11 @@ Driver Session Tests
9
9
Introduction
10
10
============
11
11
12
-
The YAML and JSON files in this directory are platform-independent tests that
13
-
drivers can use to prove their conformance to the Driver Sessions Spec. They are
12
+
The YAML and JSON files in the ``legacy`` and ``unified`` sub-directories are platform-independent tests
13
+
that drivers can use to prove their conformance to the Driver Sessions Spec. They are
14
14
designed with the intention of sharing most test-runner code with the
15
-
Transactions spec tests.
15
+
`Transactions Spec tests <../../transactions/tests/README.rst#test-format>`_.. Tests in the
16
+
``unified`` directory are written using the `Unified Test Format <../../unified-test-format/unified-test-format.rst>`_.
16
17
17
18
Several prose tests, which are not easily expressed in YAML, are also presented
18
19
in the Driver Sessions Spec. Those tests will need to be manually implemented
@@ -78,7 +79,26 @@ the given session is *not* marked dirty::
78
79
arguments:
79
80
session: session0
80
81
82
+
Snapshot session tests
83
+
======================
84
+
Snapshot sessions tests require server of version 5.0 or higher and
85
+
replica set or a sharded cluster deployment.
86
+
Default snapshot history window on the server is 5 minutes. Running the test in debug mode, or in any other slow configuration
87
+
may lead to `SnapshotTooOld` errors. Drivers can work around this issue by increasing the server's `minSnapshotHistoryWindowInSeconds` parameter, for example:
0 commit comments