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
I recently joined a project that uses your framework and came across the following issue.
When I have tests that are using Scenario and Steps structure, test is not failing when it does not find an element. I added below a code snap of how a dummy test method looks:
In the above example, if I run the method and the .exists check returns false, the test continues to check if element is .hittable as well. Snap of logs below:
If I don't use a step in the scenario, just add the code in Given outside of the step, it works properly.
I looked for what could cause this and found that if I comment out lines 85-86 from TABTestCase.swift, the example works as expected.
Can you tell me if this behaviour happened for other projects or if there is a solution? Or can we fix it?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi! I was literally just running some tests to confirm this behaviour.
I started a standard iOS project on xcode without modifying anything, I added TABTestKit pod and created a dummy scenario, similar to what @IoanaRusYnap shows.
I have the same issue. Test execution continues regardless of any failure. There can be multiple failures in a single scenario
This will continue executing past function stepFails that only has XCTFail with a message
Hi,
I recently joined a project that uses your framework and came across the following issue.
When I have tests that are using Scenario and Steps structure, test is not failing when it does not find an element. I added below a code snap of how a dummy test method looks:
In the above example, if I run the method and the .exists check returns false, the test continues to check if element is .hittable as well. Snap of logs below:
If I don't use a step in the scenario, just add the code in Given outside of the step, it works properly.
I looked for what could cause this and found that if I comment out lines 85-86 from TABTestCase.swift, the example works as expected.
Can you tell me if this behaviour happened for other projects or if there is a solution? Or can we fix it?
Thanks!
The text was updated successfully, but these errors were encountered: