System tests
Sitting at the top of the pyramid are the system tests or E2E tests. They have a very broad scope, or we can say they have a 50,000-foot scope, and they try to cover a lot of things in very few tests. They don't go down the macroscopic level. Whenever a system test fails, it is difficult to identify where the problem is because of its large scope. The test covers the entire distributed system, so the problem can be anywhere, in any component.
An example of a system test in our shopping cart microservices would be the complete checkout process. It uses the web UI of the add to cart system, where we add a number of items, generate an invoice, apply a discount code, and pay using a test credit card. If the test passes, we can assert ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access