An idea: instead of using the production database for e2e testing (which uses up our reads, writes and authentications), why not create a different, strictly test database?
From what I can see, it's possible to change the configuration using Angular environments, but I'm not too sure what this is yet. So, the second database would have the same structure as the real one, but we don't need to worry about testing too much.
An idea: instead of using the production database for e2e testing (which uses up our reads, writes and authentications), why not create a different, strictly test database?
From what I can see, it's possible to change the configuration using Angular environments, but I'm not too sure what this is yet. So, the second database would have the same structure as the real one, but we don't need to worry about testing too much.