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
Based on a reported test failure in CircleCI for one of our previous PR branches, when one of the conditions w/in the VTAssertPaginationEquals func fails it does not fail the entire test. Instead the test continues and the final results report additional failures. In the example linked above, VTAssertPaginationEquals was called 4 times w/in the same test (MainScreenPaginationTests::testCanScrollPagesWithPaginationArrows) and so CircleCI erroneously reported 4 test failures.
We need to refactor our VTAssertPaginationEquals function so that it fails the test as soon as one of the assertions w/in it fails.
Acceptance Criteria:
VTAssertPaginationEquals fails the entire test function that calls it, when it encounters its first failed assertion
The text was updated successfully, but these errors were encountered:
Description:
Based on a reported test failure in CircleCI for one of our previous PR branches, when one of the conditions w/in the
VTAssertPaginationEquals
func fails it does not fail the entire test. Instead the test continues and the final results report additional failures. In the example linked above,VTAssertPaginationEquals
was called 4 times w/in the same test (MainScreenPaginationTests::testCanScrollPagesWithPaginationArrows) and so CircleCI erroneously reported 4 test failures.We need to refactor our
VTAssertPaginationEquals
function so that it fails the test as soon as one of the assertions w/in it fails.Acceptance Criteria:
VTAssertPaginationEquals
fails the entire test function that calls it, when it encounters its first failed assertionThe text was updated successfully, but these errors were encountered: