You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While writing new tests it allows make a separate check during the main test which doesn't fail all test test a long the way.
Example: if I need to test that price is okay during the swapping - I'm adding a dependant test instead of "expect" during the main test that fails everything due to tiny check.
Example:
When I need to test that price is okay during the swapping - I'm adding a dependant test instead of "expect" during the main test that fails everything due to tiny check.
Benefits:
Independency in execution - we don't waste time to execute new tests (raising new browsers for that) we just isolate dependant tests in scope of one flow. If it has to be separate test - anytime we can set it up
When I need to disable it, I don't just comment an expect - I disable a dependant test with a reason and optional link for an issue. It allows control executable tests
Acceptance criteria:
A dependant test doesn't create a new browser context
A main test block has a dependant property that represents a test interface (name, test, disable)
A dependant test doesn't fail a main test block when it's failed
The text was updated successfully, but these errors were encountered:
Description:
While writing new tests it allows make a separate check during the main test which doesn't fail all test test a long the way.
Example: if I need to test that price is okay during the swapping - I'm adding a dependant test instead of "expect" during the main test that fails everything due to tiny check.
Example:
When I need to test that price is okay during the swapping - I'm adding a dependant test instead of "expect" during the main test that fails everything due to tiny check.
Benefits:
Acceptance criteria:
The text was updated successfully, but these errors were encountered: