No, Create a single without seed accounts and individual features in integration using seed accounts.

In this scenario, I would create a single E2E test covering primary user flow( how end user typically will use the application 80-90% of the time in production).In this, I will not use any mocking/ DB insertions for test creation(seed accounts).End to end flow in a single shot just like the real user.

For other feature level integration tests, I will use the seed accounts and each test will focus on feature/ sub feature it is primarily , not on the entire flow.

In general, I will make sure there is no redundant test cases/ test verification steps throughout the suite which is being executed as part of a single run.

In a recent code review of a test team, I found 20-30% test assertions were redundant throughout the suite and removing them significantly reduced the execution time at the same test coverage.



Source link https://sqa.stackexchange.com/questions/32427/is--test-data-in-e2e-tests-a--

LEAVE A REPLY

Please enter your comment!
Please enter your name here