Open
Description
Story:
- a user has a test where they are taking multiple snapshots that have the same name
- such as calling
toMatchDisk()
twice in one test
- such as calling
- the snapshots happen to be the same, so they get away with it
- something about the code being tested changes, and now the snapshots are different, so the test fails with this error message
- The
hotToFix
is completely buried. It should come first! - We should also advertise the
allow_multiple_equivalent_writes_to_one_location
property