This should be possible via a dedicated route (on top of _dev/reset). This should allow to avoid testing multiple times common functionality (registration, login, navigation, etc.) in end-to-end tests.
Maybe one could create dependencies between tests and snapshot the database state of a previous test to be used as the initial state for dependent tests.
This should be possible via a dedicated route (on top of
_dev/reset
). This should allow to avoid testing multiple times common functionality (registration, login, navigation, etc.) in end-to-end tests.Maybe one could create dependencies between tests and snapshot the database state of a previous test to be used as the initial state for dependent tests.