Service - Integration Test Config: Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 18: Line 18:


[[Category:Backend Services| Integration Test Config]]
[[Category:Backend Services| Integration Test Config]]
For each step in an test that spans multiple resources there will be expected input and outputs, these are configured separate to tests so unit test config for each service can point to just the data in needs, also allowing tests to branch out into multiple paths, each being tested.
The test config specifies which points to monitor and what to test for.

Revision as of 04:49, 2 August 2020

Overview

This service is intended to be used both for offline local unit testing individual services, and for multi-step/multi-service deployed integration tests.

Using this service we can configure integration, and use those same tests in a local environment, pulling out only the steps that apply to a single service and turning them into de-coupled unit tests.

The main purpose of this service is to configure integration tests for the current project that will then be used by either the local test environment or deployed by the Integration Testing service

Repository Structure

... (to be added)


Constructing Tests

For each step in an test that spans multiple resources there will be expected input and outputs, these are configured separate to tests so unit test config for each service can point to just the data in needs, also allowing tests to branch out into multiple paths, each being tested.

The test config specifies which points to monitor and what to test for.