Enhancement: @depends rerun #2636
Labels
feature/test-dependencies
Issues related to explicitly declared dependencies between tests
type/enhancement
A new idea that should be implemented
Sometimes
@depends clone
is not what's needed. For instance when the value returned by the provider is tied to a database record that is generated during that depended-upon test. Tests that depend on the value returned by a successful@depends
could be modifying that record. If a second test depends on the same@depends
, the state of the database record could have already changed.To better understand the case, consider that we don't interact directly with the database, but instead we interface with the application through its API or web UI:
Using
@depends
to chain tests would be a great alternative to embedding all the steps in the individual tests.I suggest a
@depends rerun
annotation.Pseudo code:
The text was updated successfully, but these errors were encountered: