That's E2E test. What's interesting with unit tests is that you can run them locally, offline. They are fast enough so that you can run them and see if you broke anything. If your tests take too much time to start or relies on a live env (which may be down or broken), you'll spend more time for maybe nothing.
With Docker I can run my E2E "offline".
Re:Software Testing Anti-patterns
by joshuamorton on Monday April 23, 2018 @12:15AM
(#16900473)
If you're touching real data, your test isn't offline.
Re:Software Testing Anti-patterns
by AstralStorm on Monday April 23, 2018 @03:18AM
(#16901165)
Not true. You might be touching local sample of real or realistic data. It does not need to be static either.
The performance of such a test is still a problem.
it('sends an email to the user', ...)An automated test causes the tested product to send an email to the user? So ... my docker local deployment has a DNS server with the proper MX records, an SMTP server to receive the emails, an IMAP server to expose and serve up the received emails, and the test running on my macOS can check the entire flow. No need to even have my laptop connected to any network for this test to run in its fullest.
With this you still have fast and slow perhaps, but everybody can run all but the most extreme scaling tests.