CICD Server Visual Test Result Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current distributed tracing systems are inefficient in identifying the source of failures in complex systems, as they provide only a list of operations and timing data, making it difficult for users to determine where a failure occurred, and lack visual indicators for pass/fail results across different test phases and production environments.
Innovation Solution
A continuous integration and continuous deployment (CICD) server system that generates change identifiers for code changes, performs unit, integration, and deployment tests, and provides visualizations of test results across multiple production environments, allowing for easy identification of failed phases and environments, and enables rollback operations to restore system functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If detailed listing of each operation step and timing data is provided, then complete information about system operations is available, but user ability to quickly identify failures and delays is poor
Solution Approach 1:
The patent extracts critical failure identification information from the complete operation data and presents it separately through visual indicators (color-coded icons, highlighted nodes) on the dependency map, allowing users to quickly locate failures without being overwhelmed by detailed operation listings
Solution Approach 2:
The patent applies color changes to visually indicate test results and failure states - green for pass, red for fail, yellow for warning - enabling users to immediately identify problematic operations and environments without reading detailed timing data
2Ease of operation
If visual indicators for test results are implemented across multiple environments, then ease of identifying failed phases is improved, but system complexity increases
Solution Approach 1:
The patent implements a universal visual indicator system that works across all test phases (unit, integration, deployment) and all environments (development, staging, production) using consistent color-coding and iconography, reducing the need for separate identification mechanisms for each phase or environment
Solution Approach 2:
The patent segments the complex multi-environment test results into individual visual indicators for each environment on the dependency map, allowing users to see at a glance which specific environments passed or failed without being presented with a monolithic complex report
3Reliability
If comprehensive testing across multiple phases and environments is performed, then system reliability is improved, but time required for testing and deployment increases
Solution Approach 1:
The patent performs preliminary visual assessment through the dependency map with color-coded indicators, allowing users to quickly identify which tests failed before conducting detailed analysis, thereby reducing the total time spent on troubleshooting while maintaining comprehensive testing coverage
Solution Approach 2:
The patent replaces manual review of detailed test logs and timing data with automated visual indicators and color-coded feedback on the dependency map, significantly reducing the time required to interpret test results while maintaining comprehensive testing across all phases and environments
Data Source
AI summary
Systems and methods are provided for receiving a code change at a continuous integration and continuous deployment (CICD) server system, generating a unique change identifier, generating a new code build which includes the code change, testing the generated new code build by performing a code trace for phase of testing or production environment based on at least one predetermined testing parameter that includes a predetermined trace time for the code change of the generated change identifier, and displaying test results for the change identifier for the phase of testing or production environment to visually highlight a pass or failure of the testing for the code change based on the predetermined testing parameter for the predetermined trace time.