We have this app where creating an account takes about 10-15 min and the process is really complicated. Thus we started using
seed accounts which are basically
already created accounts that are implemented after each db clean.
Edit: I meant we started using 'seed accounts' which is some kind of setup, so whenever we clean our db, the db itself is populated with that predefined setup (already created accounts)
We have plenty of test cases, that tests features on these
However Im wondering how many e2e tests (create account + test these features) should we include? Because
seed accounts are mocked accounts which may be different than the real ones created manually by user.
Going for a testing these features with e2e testing (creating account + features testing) have a lot of cons:
- a lot of time wasted
- tests might be interrupted with problems during account creation
Another thing that struggles me is that tests made on
seed accounts will be also covered with e2e tests (if we go with testing these features on created account) so its tests coverage duplication.
So my question is:
Should we go with approach whether we tests features on seed accounts and then perform e2e test only to check if account has been correctly created (by asserting successful login)?