Service - Integration Testing: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
This service is intended to be run in a deployed AWS environment, all services and resources required for the integration tests need to be operational. | This service is intended to be run in a deployed AWS environment, all services and resources required for the integration tests need to be operational. | ||
== Initiating | == Initiating tests == | ||
When the initial request is sent to begin an integration test the middleware LOG_LEVEL is set to DEBUG, this causes all Lambda functions and requests to external services to add a message to the services MsgOut queue. The Integration Testing service subscribes to these queues and uses these messages to monitor each stage of the workflow to ensure input and output is as expected, and that the request completes. | When the initial request is sent to begin an integration test the middleware LOG_LEVEL is set to DEBUG, this causes all Lambda functions and requests to external services to add a message to the services MsgOut queue. The Integration Testing service subscribes to these queues and uses these messages to monitor each stage of the workflow to ensure input and output is as expected, and that the request completes. | ||
(possible feature) We could mark requests initiated by Integration Testing service with a Correlation Id which gets added to Message Attributes and can be used as a filter, so only debug messages that were initiated by Integration Testing are received by it. This will exclude requests that middleware randomly sets to debug. | (possible feature) We could mark requests initiated by Integration Testing service with a Correlation Id which gets added to Message Attributes and can be used as a filter, so only debug messages that were initiated by Integration Testing are received by it. This will exclude requests that middleware randomly sets to debug. | ||
[[Category:Backend services| Integration Testing]] | |||
Revision as of 07:50, 9 August 2020
Overview
Service that pulls integration tests from the Integration Test Config service, invokes each test and monitors the steps execute as expected.
This service is intended to be run in a deployed AWS environment, all services and resources required for the integration tests need to be operational.
Initiating tests
When the initial request is sent to begin an integration test the middleware LOG_LEVEL is set to DEBUG, this causes all Lambda functions and requests to external services to add a message to the services MsgOut queue. The Integration Testing service subscribes to these queues and uses these messages to monitor each stage of the workflow to ensure input and output is as expected, and that the request completes.
(possible feature) We could mark requests initiated by Integration Testing service with a Correlation Id which gets added to Message Attributes and can be used as a filter, so only debug messages that were initiated by Integration Testing are received by it. This will exclude requests that middleware randomly sets to debug.