{"id":99023,"date":"2019-10-10T07:00:00","date_gmt":"2019-10-10T04:00:00","guid":{"rendered":"https:\/\/www.javacodegeeks.com\/?p=99023"},"modified":"2019-10-07T17:33:45","modified_gmt":"2019-10-07T14:33:45","slug":"efficient-enterprise-testing-conclusion","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2019\/10\/efficient-enterprise-testing-conclusion.html","title":{"rendered":"Efficient enterprise testing \u2014 conclusion (6\/6)"},"content":{"rendered":"

This last part of the series will cover additional end-to-end tests, testing in production, and a conclusion of the parts.<\/p>\n

Further end-to-end tests & testing in production<\/strong><\/p>\n

Besides system tests that only verify a single application-under-test and mock external concerns, our pipeline must also include full end-to-end test that verify the system as a whole. The good news is that if we\u2019re crafting our tests in a maintainable way, with reusable components, we can recycle the test scenarios to be fired against other test or staging environments.<\/p>\n

It depends on the nature of the business logic, to which regard that is feasible, if for example the system then actually orders a coffee or performs a financial transaction. In these cases it might be possible to add additional business steps, for example add an immediate \u201cundo\u201d transactions or something similar.<\/p>\n

As an outlook, this touches the topic of testing in production, verifying the same logical paths that the users also go through and making sure that the tests have no negative impact in the business process, such as ordering actual coffee. Testing in production is, after all the efforts on a test scope, the ultimate verification, whether our system works as expected. Defining our test scenarios in a reasonable way, being driven by the actual business use cases with test code quality in mind, make this endeavor easier to pursue.

<\/div> <\/div><\/p>\n

Conclusion<\/strong><\/p>\n