Right now, deprecations are turned into ExampleException\ErrorException like notices and warnings, which interrupts the execution (turning deprecations into breaks instead, which defeats their purpose).

Deprecations should be collected and reported (potentially failing the suite depending on how the runner is configured if configuration is relevant) without turning them into exceptions (so that the behavior can still be asserted).

To allow covering deprecated methods (testing BC layers is also important), individual specs should be able to opt-out of the deprecation reporting (and any associated suite failure). I would suggest doing that thanks to a #[AllowDeprecations] attribute on the spec method.