Software Test Coordinator for Cross-Service Integration Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for in-field testing of software services in modular systems require permanent integration of test probes, limiting the ability to perform tests across different services and necessitate complex management of test probes, test cases, and execution schedules within the development cycle, which is inefficient and lacks transparency.
Innovation Solution
A centralized test coordinator module is introduced to manage and coordinate testing across multiple software components, decoupling test suites and probes, allowing dynamic definition and execution of tests without embedding test logic within the service code, and utilizing a service meta model for centralized information storage and management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If test probes are permanently integrated into software services, then testing can be performed within individual services, but testing across different services becomes difficult and complex management is required
Solution Approach 1:
The system segments test probes, test cases, and execution schedules as independent manageable units that can be individually assigned to services. Test probes are no longer permanently bound to specific services but can be dynamically allocated, allowing separate management of testing components across multiple services without complex interdependencies.
Solution Approach 2:
The patent introduces an intermediary management layer that coordinates test probes across different services. This intermediary enables test cases to access and coordinate multiple test probes from different services without requiring direct integration, simplifying the management architecture while maintaining comprehensive testing capability.
2Ease of manufacture
If test probes are added at build time, then testing is integrated into the service, but flexibility to perform tests across different services is lost
Solution Approach 1:
The system transitions from static, build-time integration of test probes to dynamic, runtime allocation. Test probes can be dynamically assigned to different services and test cases based on testing requirements, enabling flexible cross-service testing while maintaining ease of service deployment and management.
3Extent of automation
If test cases are executed on an external test system, then centralized control is achieved, but developers must know all test probes across services increasing complexity
Solution Approach 1:
The system implements self-service mechanisms where test cases automatically discover and manage their required test probes without developer intervention. The management system handles probe allocation, coordination, and lifecycle management automatically, reducing the knowledge burden on developers while maintaining centralized execution control.
4Loss of information
If per-service test probe lists are merged, then an overview is created, but alignment with deployed service versions must be ensured adding complexity
Solution Approach 1:
The system implements feedback mechanisms that automatically verify and align test probe versions with deployed service versions. The management system continuously monitors version consistency and provides feedback to ensure test probes remain synchronized with their corresponding services, eliminating manual alignment complexity while maintaining complete information accuracy.
Data Source
Figure 1
Figure 2
AI summary
The inventions relates to a method for testing at least one software component (14, 16) of a system (18) by an electronic computing device (10), comprising the steps of providing a test coordinator module (12) of the electronic computing device (10) for the system (18), wherein the test coordinator module (12) provides a test protocol for testing the software component (14, 16), and wherein the test coordinator module (12) is provided separately to the software component (14, 16); and testing the software component (14, 16) by coordinating the testing of the software component (14, 16) depending on the test protocol by the test coordinator module (12). Furthermore, the present invention relates to a computer program product, a computer-readable storage medium, as well as to an electronic computing device (10).