Production environment deployed on AWS: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Overview = Tests that run within the production environment do not change state such as records in databases. = Integration tests = Integration tests use the same system...") |
|||
| Line 11: | Line 11: | ||
= Beginning tests automatically from live requests = | = Beginning tests automatically from live requests = | ||
(not yet implemented) Middleware randomly sets some production requests to DEBUG log level, these are not initiated by the [[Service - Integration Testing]] service so | (not yet implemented) Middleware randomly sets some production requests to DEBUG log level, these are not initiated by the [[Service - Integration Testing]] service so will not trigger a message sent to Integration Test service. | ||
We could try to design tests that trigger from these requests, tests that we know certain requests will result in certain outputs. | We could try to design tests that trigger from these requests, tests that we know certain requests will result in certain outputs. | ||
Latest revision as of 14:02, 3 May 2021
Overview
Tests that run within the production environment do not change state such as records in databases.
Integration tests
Integration tests use the same system as Test Environment Deployed on AWS however are limited to tests that do not change state such as records in databases.
We configure the tests with the Integration Test Config service, invoke and monitor them in the Service - Integration Testing service.
Beginning tests automatically from live requests
(not yet implemented) Middleware randomly sets some production requests to DEBUG log level, these are not initiated by the Service - Integration Testing service so will not trigger a message sent to Integration Test service.
We could try to design tests that trigger from these requests, tests that we know certain requests will result in certain outputs.