Platform (all, jvm, js, android): all
Extension (none, kotlin 1.3): none

Code related feature

See robstoll/atrium-roadmap#15 for the full background.

We want to be able to state the reason for an assertion (could also be additional context to explain the assertion etc.).

expect(proposeAFileName())
  .because("? is not allowed in file names on Windows") {
    containsNot("

Is there a way to switch to strict/eager assertion fail mode, so that one can use --pdb on demand?

Is your feature request related to a problem? Please describe.
Currently Snapper returns the error A snapshot does not exist when a snapshot does not exist. The user then has to go and set the UpdateSnapshots attribute and re-run the tests. This is cumbersome and an extra step that can be avoided to improve developer experience.

Describe the solution you'd like
If the environment

Let's make sure the matcher was called with supported parameters, fail fast otherwise.

There should be no need in console.error usage.