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
We have a testscenario, where we want to mock a section that performs a goback, but the functionality of the goback needs to be preserved, to avoid bad tests.
Example: EXAMPLE SECTION. PERFORM DO-SOMETHING IF DO-SOMETHING-WENT-BAD PERFORM SECTION-WITH-GOBACK END-IF PERFORM DO-SOMETHING-MORE .
If I create a test of example section, and make sure that we enter the SECTION-WITH-GOBACK, we want to mock that section, so we do not goback, but we want to exit the testcase, because we do not want to perform the section do-something-more, as that would not normally be executed.
This could of course be fixed with a little bit of refactoring, but I also know of many who use this syntax.
The text was updated successfully, but these errors were encountered:
We have a testscenario, where we want to mock a section that performs a goback, but the functionality of the goback needs to be preserved, to avoid bad tests.
Example:
EXAMPLE SECTION. PERFORM DO-SOMETHING IF DO-SOMETHING-WENT-BAD PERFORM SECTION-WITH-GOBACK END-IF PERFORM DO-SOMETHING-MORE .
If I create a test of example section, and make sure that we enter the SECTION-WITH-GOBACK, we want to mock that section, so we do not goback, but we want to exit the testcase, because we do not want to perform the section do-something-more, as that would not normally be executed.
This could of course be fixed with a little bit of refactoring, but I also know of many who use this syntax.
The text was updated successfully, but these errors were encountered: