Endpoint Data Validation for Device Management Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Device management platforms face challenges in accurately testing endpoint control due to the occurrence of false positives, which can arise from relying solely on API-based testing without direct validation of endpoint data.
Innovation Solution
A method and system that involve sending requests to a cloud controller to create entities, receiving response data, generating control data, and comparing it with entity data retrieved directly from the endpoint using various interfaces like REST APIs or CLI, to validate the test status and eliminate false positives.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If API-based testing is used without direct endpoint validation, then testing simplicity is maintained, but false positives occur reducing testing accuracy
Solution Approach 1:
The testing process is segmented into two independent validation paths: one through the cloud controller API and another directly to the endpoint. Each path operates separately and their results are compared, allowing the system to maintain simplicity in each individual path while achieving higher overall accuracy through the comparison mechanism.
Solution Approach 2:
The computing device acts as an intermediary that receives data from both the cloud controller and the endpoint directly, compares the two data sources, and determines test status. This intermediary role enables cross-validation without requiring complex integration between the API testing framework and endpoint direct access.
2Reliability
If direct endpoint validation is added to API-based testing, then false positives are eliminated, but testing process complexity increases
Solution Approach 1:
The system implements feedback by comparing the response data from the cloud controller with the entity data retrieved directly from the endpoint. When the data matches, the test is confirmed reliable; when they differ, the system identifies false positives. This feedback loop enhances reliability without requiring fundamental changes to the testing architecture.
Solution Approach 2:
The patent applies partial action by performing direct endpoint validation only for specific critical tests where false positives are most problematic, rather than requiring direct validation for all possible test scenarios. This selective approach improves reliability for critical operations while limiting the increase in overall system complexity.
Data Source
AI summary
A method of eliminating false positives when testing a device management platform for controlling endpoints. The method includes sending, by a computing device, a request to a cloud controller to create an entity. The request causes operations including i) creating, by an endpoint responsive to a receipt of an interface request from the cloud controller, the entity, ii) receiving, by the cloud controller from the endpoint, response data generated by the entity, the response data indicating the creation of the entity, and iii) generating, by the cloud controller, control data based on the response data. The method includes receiving the control data from the cloud controller; sending, responsive to the receipt of the control data, a call to the endpoint for entity data; receiving entity data from the endpoint; comparing, the response data to the entity data to validate the response data; and generating a test status.