Test environment deployed on AWS: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Marked this version for translation) |
||
| Line 1: | Line 1: | ||
<translate> | <translate> | ||
= Overview = | = Overview = <!--T:1--> | ||
<!--T:2--> | |||
All services that are part of the multi-service workflow being tested are deployed to AWS, normally with seeded data ready for tests. | All services that are part of the multi-service workflow being tested are deployed to AWS, normally with seeded data ready for tests. | ||
= Integration tests = | = Integration tests = <!--T:3--> | ||
<!--T:4--> | |||
We configure the tests with the [[Service - Integration Test Config|Integration Test Config]] service, invoke and monitor them in the [[Service - Integration Testing|Integration Testing]] service. | We configure the tests with the [[Service - Integration Test Config|Integration Test Config]] service, invoke and monitor them in the [[Service - Integration Testing|Integration Testing]] service. | ||
<!--T:5--> | |||
Requests initiated by testing service set the [[NPM module - izara-middleware|izara-middleware] module's LOG_LEVEL to DEBUG by setting the DEBUG_LOG_ENABLED correlation id, this will trigger a message sent to [[Service - Integration Test Config|Integration Test Config]] whenever an external service is invoked/returns, that message is checked to see if matches expected inputs/outputs. | Requests initiated by testing service set the [[NPM module - izara-middleware|izara-middleware] module's LOG_LEVEL to DEBUG by setting the DEBUG_LOG_ENABLED correlation id, this will trigger a message sent to [[Service - Integration Test Config|Integration Test Config]] whenever an external service is invoked/returns, that message is checked to see if matches expected inputs/outputs. | ||
</translate> | </translate> | ||
Latest revision as of 04:01, 4 October 2022
Overview
All services that are part of the multi-service workflow being tested are deployed to AWS, normally with seeded data ready for tests.
Integration tests
We configure the tests with the Integration Test Config service, invoke and monitor them in the Integration Testing service.
Requests initiated by testing service set the [[NPM module - izara-middleware|izara-middleware] module's LOG_LEVEL to DEBUG by setting the DEBUG_LOG_ENABLED correlation id, this will trigger a message sent to Integration Test Config whenever an external service is invoked/returns, that message is checked to see if matches expected inputs/outputs.