Timeline for Automation: how to isolate test cases when they really depend on another one?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2018 at 16:25 | comment | added | sphennings | @Floella You should separate your actions from your validation. If you have a method that creates an account. That should be used in the test validating account creation but it can also be used in setting up other tests if you need to create a new account for that test. | |
| Feb 21, 2018 at 13:55 | comment | added | Floella | Thanks :) In this case I have no control over application data. But since there's no API I can use, the only way to create a user account would be by running a test that creates it (or, if we don't want to call it a "test", it would still execute the same behavior the account creation test steps perform). Would it still be a good practise to "execute a test" in a suite setup? | |
| Feb 21, 2018 at 13:07 | history | answered | Kate Paulk | CC BY-SA 3.0 |