From 8ed41f3e874f7f9f0f0b0dac1a26a148afd0e332 Mon Sep 17 00:00:00 2001 From: Warit Kosolwattanasombat Date: Sun, 16 Apr 2023 14:01:44 +0700 Subject: [PATCH] Fixes docs --- docs/ExpectAPI.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ExpectAPI.md b/docs/ExpectAPI.md index 7a7722efe2df..6acd9b76a4a9 100644 --- a/docs/ExpectAPI.md +++ b/docs/ExpectAPI.md @@ -750,7 +750,7 @@ This ensures that a value matches the most recent snapshot. Check out [the Snaps You can provide an optional `propertyMatchers` object argument, which has asymmetric matchers as values of a subset of expected properties, **if** the received value will be an **object** instance. It is like `toMatchObject` with flexible criteria for a subset of properties, followed by a snapshot test as exact criteria for the rest of the properties. -By setting the `snapshotName` explicitly (as opposed to letting Jest infer the name from context) it can be guaranteed to be consistent across test runs, whatever the context at the time of evaluation. Jest always appends a number at the end of a snapshot name. +By setting the `snapshotName` explicitly (as opposed to letting Jest infer the name from context) it can be guaranteed to be consistent across test runs, whatever the context at the time of evaluation. Jest always appends a number at the end of a snapshot name. Jest sorts snapshots by name in the corresponding `.snap` file.