Multi-dimensional collaborative testing method and device for background management system of vending machine
By using a multi-dimensional collaborative testing method and device for the vending machine back-end management system, the systemic problems of data synchronization and testing methods were solved, thereby improving the system's reliability and stability.
Patent Information
- Application Number
- CN202511193049.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-25
- Publication Date
- 2025-11-28
AI Technical Summary
In existing technologies, data testing methods for vending machines suffer from data synchronization issues, which affect the consistency and accuracy of business analysis. Furthermore, existing testing methods lack a systematic approach and cannot fully cover functional, performance, and data consistency requirements.
This paper provides a multi-dimensional collaborative testing method and device for a vending machine back-end management system. Through functional testing, stress testing, and data consistency methods, it simulates the entire business process to generate basic test data, applies loads, performs multi-dimensional comparisons, and generates a test report.
The system's functional testing was implemented, which solved problems in existing technologies, improved the system's functionality, and enhanced its reliability and stability.
Smart Images

Figure CN121029609A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of intelligent vending machine technology, specifically relating to a multi-dimensional collaborative testing method and device for a vending machine back-end management system. Background Technology
[0002] In practical applications of intelligent vending machine back-end management systems, business modules such as task management (covering replenishment tasks, inspection tasks, and maintenance tasks) and machine location latitude and longitude updates typically employ independent data reporting and storage processes. This independent operation leads to a lack of effective correlation and collaboration between data from different modules, resulting in data fragmentation and severely impacting the consistency and accuracy of business data analysis. For example, when settling wages for replenishment staff and maintenance personnel, the chaotic association of task data often leads to errors in wage calculations; and when analyzing the relationship between machine locations and operational data, the inaccurate matching of latitude and longitude information with task data interferes with operational decision-making.
[0003] Meanwhile, existing testing methods lack a systematic approach and fail to comprehensively cover the system's functional, performance, and data consistency requirements. Functional testing focuses only on single business processes, making it difficult to identify data flow issues between different modules; stress testing lacks targeted verification of key interfaces and message queues; and data consistency testing methods are simplistic and struggle to guarantee data accuracy in complex business scenarios. These problems challenge the quality and reliability of intelligent vending machine back-end management systems, thus necessitating a comprehensive and efficient testing methodology to address these issues. Summary of the Invention
[0004] To address this, the present invention provides a multi-dimensional collaborative testing method and apparatus for a vending machine back-end management system, which solves the problems in existing intelligent vending machine back-end management systems where data fragmentation caused by independent data reporting and storage affects the consistency and accuracy of business analysis, and where existing testing methods lack systematicity and cannot fully cover functional, performance, and data consistency requirements.
[0005] To achieve the above objectives, the present invention provides the following technical solution: a multi-dimensional collaborative testing method for a vending machine back-end management system, including functional testing, stress testing, and data consistency testing, wherein the functional testing, stress testing, and data consistency testing dimensions form a collaborative relationship through a data flow link.
[0006] The functional testing dimension simulates the entire business process to generate basic test data. The test objects of the functional testing dimension include logical tests of task status transition, task generation, task failure and timeout, replenishment task association, and location latitude and longitude information processing.
[0007] The stress test dimension applies load to the interfaces and data links covered by the functional test dimension and records the data flow under the set load. The test objects of the stress test dimension include single interface stress test of obtaining associated task interface and Kafka message consumption capability test of task creation push.
[0008] The data consistency test dimension compares the basic test data with the data stream under the set load in multiple dimensions. The multi-dimensional comparison includes comparing the replenishment email with the background task data and comparing the consistency of task and record data.
[0009] Collect the results data from the functional testing dimension, the stress testing dimension, and the data consistency testing dimension, perform comprehensive analysis and evaluation on the results data, and generate a test report that includes the testing process, results, problem identification, and improvement suggestions.
[0010] As a preferred multi-dimensional collaborative testing method for vending machine back-end management systems, the task generation logic test in the functional testing dimension constructs a task generation model based on in-machine inventory, sales status, feedback records, and equipment failure triggering conditions. Specifically:
[0011] Let the replenishment task be triggered by I < T i In the formula, I represents the in-machine inventory, and T represents the inventory of goods in operation. i The inventory threshold is used; the inspection task is triggered when F ≥ T. f In the formula, F represents the frequency of competitor appearances in the feedback records, and T represents the frequency of competitor appearances. f The frequency threshold is used; the triggering condition for maintenance tasks is E≠0, where E is the equipment fault code; based on the input historical business data of the task generation model, an expected task list is generated, and compared with the actual task list generated by the system to calculate the matching rate:
[0012]
[0013] In the formula, N c For the number of consistent tasks, N t The total number of tasks; when M ≥ T m At that time, it is determined that the task generation is accurate and timely. m This is the preset matching threshold.
[0014] As a preferred solution for multi-dimensional collaborative testing of the vending machine back-end management system, the task failure and timeout logic test in the functional testing dimension is configured with a timeout judgment model: if t c -t g If the timeout period is greater than 48 hours and the task status is not equal to "completed", then O = 1; otherwise, O = 0. In this formula, O is the timeout flag, and t... c t represents the current time. gSet the task generation time; when O=1, the verification system updates the task status to "timeout" and performs a removal operation in the payroll data source.
[0015] As a preferred multi-dimensional collaborative testing method for the vending machine back-end management system, the single-interface stress test of the interface for obtaining associated tasks in the stress testing dimension adopts a concurrent request gradient model:
[0016] The initial concurrency is C0, and the concurrency increment is increased by ΔC at fixed time intervals until the system response time t is reached. r >T r Or error rate E r >T e In the formula, C0 is the initial concurrency, ΔC is the concurrency increment, and t r T represents the system response time. r E is the response time threshold. r For error rate, T e The error rate threshold is used; the number of concurrent connections at this point is recorded as the maximum capacity C. max .
[0017] As a preferred multi-dimensional collaborative testing method for vending machine back-end management systems, in the stress testing dimension, during the prediction of the consumption capacity of Kafka messages pushed by task creation, a message production rate gradient is set:
[0018] The initial speed is V p 0, increasing the production rate increment ΔV at fixed time intervals. p Simultaneously monitor consumption rate V c When the message backlog Q = Q p -Q c >Q t And the duration exceeds t s At that time, it was determined that a consumption bottleneck had been reached, among which V p 0 represents the initial production rate, ΔV p V represents the production rate increment. c Q represents the consumption rate, and Q represents the message backlog. p Q represents total production. c Q represents total consumption. t t is the accumulation threshold. s This is the duration threshold;
[0019] A consumption capacity model was fitted based on test data:
[0020] V cmax =k×V p +b
[0021] In the formula, V cmax For the maximum consumption rate, Vp Let k be the production rate, and b be the model parameters.
[0022] As a preferred multi-dimensional collaborative testing method for vending machine back-end management systems, the data consistency testing dimension compares the consistency of task and record data. Specifically, it compares the replenishment quantity and withdrawal quantity in the replenishment task with the actual operation quantity in the replenishment record, and calculates the actual replenishment data.
[0023] R = I e -I s +S
[0024] In the formula, R is the actual replenishment quantity, and I... e This refers to the inventory after the last replenishment, I s Let S be the inventory before the first replenishment and S be the sales quantity during the replenishment period; verify the real-time updates and correlations of the data during task execution, when |RR p |≤0.05R p In the formula, R p When determining the replenishment quantity for the task plan, the data is judged to be consistent.
[0025] As a preferred multi-dimensional collaborative testing method for vending machine back-end management systems, the data consistency testing dimension compares replenishment emails with back-end task data, extracts the replenishment quantity E from the replenishment emails and the replenishment quantity S from the back-end tasks, and calculates the deviation rate.
[0026]
[0027] In the formula, D is the deviation rate, E is the quantity to be supplemented in the email, and S is the quantity to be supplemented in the background task; when D=0, it is determined to be consistent; otherwise, the data generation and transmission process is traced to locate the root cause of the problem.
[0028] This invention also provides a multi-dimensional collaborative testing device for a vending machine back-end management system, including a functional testing module, a stress testing module, a data consistency testing module, and a test report generation module. The functional testing module, the stress testing module, and the data consistency testing module form a collaborative relationship through a data flow link.
[0029] The functional testing module is used to simulate the entire business process to generate basic test data. The test objects of the functional testing module include logical tests of task status transition, task generation, task failure and timeout, replenishment task association, and location latitude and longitude information processing.
[0030] The stress testing module applies load to the interfaces and data links covered by the functional testing module and records the data flow under the set load. The test objects of the stress testing module include single-interface stress testing of obtaining associated task interfaces and Kafka message consumption capability testing of task creation and push.
[0031] The data consistency testing module performs multi-dimensional comparisons between the basic test data and the data stream under the set load. The multi-dimensional comparisons include comparisons between replenishment emails and background task data, and comparisons between task and record data consistency.
[0032] The test report generation module collects the result data from the functional test module, the stress test module, and the data consistency test module, performs comprehensive analysis and evaluation on the result data, and generates a test report that includes the test process, results, problem identification, and improvement suggestions.
[0033] As a preferred solution for multi-dimensional collaborative testing devices in a vending machine back-end management system, the task generation logic test in the functional testing module constructs a task generation model based on in-machine inventory, sales status, feedback records, and equipment fault triggering conditions. Specifically:
[0034] Let the replenishment task be triggered by I < T i In the formula, I represents the in-machine inventory, and T represents the inventory of goods in operation. i The inventory threshold is used; the inspection task is triggered when F ≥ T. f In the formula, F represents the frequency of competitor appearances in the feedback records, and T represents the frequency of competitor appearances. f The frequency threshold is used; the triggering condition for maintenance tasks is E≠0, where E is the equipment fault code; based on the input historical business data of the task generation model, an expected task list is generated, and compared with the actual task list generated by the system to calculate the matching rate:
[0035]
[0036] In the formula, N c For the number of consistent tasks, N t The total number of tasks; when M ≥ T m At that time, it is determined that the task generation is accurate and timely. m This is the preset matching threshold.
[0037] As a preferred solution for multi-dimensional collaborative testing devices in the vending machine back-end management system, the task failure and timeout logic test in the functional testing module sets up a timeout judgment model: if t c -t g If the timeout period is greater than 48 hours and the task status is not equal to "completed", then O = 1; otherwise, O = 0. In this formula, O is the timeout flag, and t... c t represents the current time. gSet the task generation time; when O=1, the verification system updates the task status to "timeout" and performs a removal operation in the payroll data source.
[0038] As a preferred solution for a multi-dimensional collaborative testing device for a vending machine back-end management system, the single-interface stress test process for obtaining associated task interfaces in the stress testing module adopts a concurrent request gradient model:
[0039] The initial concurrency is C0, and the concurrency increment is increased by ΔC at fixed time intervals until the system response time t is reached. r >T r Or error rate E r >T e In the formula, C0 is the initial concurrency, ΔC is the concurrency increment, and t r T represents the system response time. r E is the response time threshold. r For error rate, T e This is the error rate threshold; the number of concurrent connections at this point is recorded as the maximum capacity.
[0040] As a preferred solution for a multi-dimensional collaborative testing device for a vending machine back-end management system, the stress testing module sets a message production rate gradient during the prediction of the consumption capacity of Kafka messages pushed by task creation.
[0041] The initial speed is V p 0, increasing the production rate increment ΔV at fixed time intervals. p Simultaneously monitor consumption rate V c When the message backlog Q = Q p -Q c >Q t And the duration exceeds t s At that time, it was determined that a consumption bottleneck had been reached, among which V p 0 represents the initial production rate, ΔV p V represents the production rate increment. c Q represents the consumption rate, and Q represents the message backlog. p Q represents total production. c Q represents total consumption. t t is the accumulation threshold. s This is the duration threshold;
[0042] A consumption capacity model was fitted based on test data:
[0043] V cmax =k×V p +b
[0044] In the formula, V cmax For the maximum consumption rate, V pLet k be the production rate, and b be the model parameters.
[0045] As a preferred solution for a multi-dimensional collaborative testing device for a vending machine back-end management system, the data consistency testing module compares the consistency of task and record data. This comparison examines the replenishment quantity and withdrawal quantity in the replenishment task against the actual operation quantity in the replenishment record, and calculates the actual replenishment data.
[0046] R = I e -I s +S
[0047] In the formula, R is the actual replenishment quantity, and I... e This refers to the inventory after the last replenishment, I s Let S be the inventory before the first replenishment and S be the sales quantity during the replenishment period; verify the real-time updates and correlations of the data during task execution, when |RR p |≤0.05R p In the formula, R p When determining the replenishment quantity for the task plan, the data is judged to be consistent.
[0048] As a preferred solution for a multi-dimensional collaborative testing device for a vending machine back-end management system, the data consistency testing module compares replenishment emails with back-end task data, extracts the replenishment quantity E from the replenishment emails and the replenishment quantity S from the back-end tasks, and calculates the deviation rate.
[0049]
[0050] In the formula, D is the deviation rate, E is the quantity to be supplemented in the email, and S is the quantity to be supplemented in the background task; when D=0, it is determined to be consistent; otherwise, the data generation and transmission process is traced to locate the root cause of the problem.
[0051] The beneficial effects of this invention are as follows:
[0052] First, it comprehensively covers core business processes and performance requirements. Through multi-dimensional testing of functionality, stress, and data consistency, it can accurately identify potential system problems and ensure functional integrity and performance reliability.
[0053] Second, address the issue of data fragmentation by leveraging a multi-dimensional comparison and traceability mechanism for data consistency testing to ensure accurate correlation of task data, latitude and longitude data, and other data across different modules. This will improve the consistency and accuracy of business data analysis and provide reliable data support for operational decisions and payroll settlement.
[0054] Third, stress tests were conducted on key interfaces and message queues to identify and optimize performance bottlenecks, effectively improving the system's processing capabilities under high concurrency and high load scenarios and ensuring stable system operation.
[0055] Fourth, the multi-dimensional collaborative testing system automates the execution of test tasks, reduces labor costs, and improves testing efficiency. At the same time, through systematic testing methods and detailed reports, it ensures that test results are accurate and reliable, providing a strong basis for system optimization. Attached Figure Description
[0056] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are merely exemplary, and those skilled in the art can derive other embodiments based on the provided drawings without creative effort.
[0057] Figure 1 A schematic diagram of the technical route for the multi-dimensional collaborative testing method of the vending machine back-end management system provided in this embodiment of the invention;
[0058] Figure 2 This is a diagram illustrating the architecture of a multi-dimensional collaborative testing device for a vending machine back-end management system provided in an embodiment of the present invention. Detailed Implementation
[0059] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0060] Example 1
[0061] See Figure 1 This invention provides a multi-dimensional collaborative testing method for a vending machine back-end management system, including functional testing, stress testing, and data consistency testing. These three dimensions are collaboratively linked through a data flow chain.
[0062] The functional testing dimension simulates the entire business process to generate basic test data. The test objects of this functional testing dimension include logical tests of task status transitions, task generation, task failure and timeout, replenishment task association, and location latitude and longitude information processing. The stress testing dimension applies load to the interfaces and data links covered by the functional testing dimension and records the data flow under the set load. The test objects of this stress testing dimension include single-interface stress testing of obtaining associated task interfaces and Kafka message consumption capability testing of task creation push. The data consistency testing dimension performs multi-dimensional comparisons between the basic test data and the data flow under the set load. These multi-dimensional comparisons include comparisons between replenishment emails and backend task data, and consistency comparisons between task and recorded data. The results data from the functional testing dimension, the stress testing dimension, and the data consistency testing dimension are collected, and the results data are comprehensively analyzed and evaluated to generate a test report including the testing process, results, problem identification, and improvement suggestions.
[0063] Specifically, functional testing serves as the foundation. By reproducing real-world business scenarios (such as the entire process of a task from generation to completion), basic test data conforming to business rules is generated. This data forms the benchmark for subsequent tests. Stress testing is not conducted independently. Instead, it uses the interfaces and data links defined in functional testing as the target. By applying loads of varying intensities (such as high-concurrency requests), it simulates the system's operation under peak business volume and records the data flow changes to verify the system's stability under stress. Data consistency testing is the key link between the first two. It compares the basic data generated by functional testing with the accuracy of the load data flow in stress testing, ensuring that data transmission and storage remain consistent across different modules (such as email notifications and backend systems) regardless of whether the system is under normal or high-pressure conditions. This chain of basic data generation, stress data verification, and full-domain data comparison achieves comprehensive collaborative verification from functionality to performance to data quality.
[0064] Functional testing focuses on core logic such as task status transitions because these logics directly determine the integrity of the business process; for example, incorrect task status can lead to confusion in subsequent operation permissions. Stress testing focuses on obtaining related task interfaces and Kafka message consumption because these are key nodes in system data interaction, and the interface capacity and message processing efficiency directly affect the system's response speed. Data consistency testing compares replenishment emails with backend data because these data need to be highly consistent in actual operations (such as payroll settlement and inventory management), and any deviation can cause business problems. By summarizing the results from these three dimensions, the system's functional defects (such as errors in task generation logic), performance bottlenecks (such as interface maximum concurrency limits), and data inconsistencies (such as discrepancies between email and backend data quantities) can be comprehensively presented. The proposed improvement suggestions can provide targeted guidance for system optimization, avoiding the omission of problems caused by fragmented testing.
[0065] In this embodiment, the task generation logic test in the functional testing dimension constructs a task generation model based on in-machine inventory, sales status, feedback records, and equipment failure triggering conditions. Specifically:
[0066] Let the replenishment task be triggered by I < T i In the formula, I represents the in-machine inventory, and T represents the inventory of goods in operation. i The inventory threshold is used; the inspection task is triggered when F ≥ T. f In the formula, F represents the frequency of competitor appearances in the feedback records, and T represents the frequency of competitor appearances. f The frequency threshold is used; the triggering condition for maintenance tasks is E≠0, where E is the equipment fault code; based on the input historical business data of the task generation model, an expected task list is generated, and compared with the actual task list generated by the system to calculate the matching rate:
[0067]
[0068] In the formula, N c For the number of consistent tasks, N t The total number of tasks; when M ≥ T m At that time, it is determined that the task generation is accurate and timely. m This is the preset matching threshold.
[0069] Specifically, the replenishment task is triggered when I < T. i This is directly related to the core function of the vending machine, namely, selling goods. When the inventory falls below a threshold, replenishment is automatically triggered, which can avoid stockouts caused by untimely manual monitoring; the inspection task is triggered when F ≥ T. fIn response to market competition scenarios, inspections are initiated when the frequency of competitor product appearances reaches a threshold, helping operators adjust marketing strategies promptly. The maintenance task trigger condition E≠0 directly identifies equipment anomalies through fault codes, ensuring rapid response to faults and minimizing equipment downtime. These conditions are all based on actual operational needs, making testing more aligned with business scenarios.
[0070] The process involves inputting historical business data into the model to obtain a list of expected tasks, which is then compared with the list actually generated by the system to calculate the matching rate M. This process essentially verifies whether the system accurately generates tasks according to preset rules. For example, if a machine's inventory repeatedly falls below a threshold in historical data without generating a replenishment task, M will decrease, thus exposing a logical flaw in the system. The preset matching threshold T... m This provides a quantitative standard for judgment, ensuring that the accuracy of task generation reaches a level acceptable to the business, and avoiding the impact on operational efficiency due to missed or incorrect task generation.
[0071] In this embodiment, the task failure and timeout logic test in the functional testing dimension sets a timeout determination model: if t c -t g If the timeout period is greater than 48 hours and the task status is not equal to "completed", then O = 1; otherwise, O = 0. In this formula, O is the timeout flag, and t... c t represents the current time. g Set the task generation time; when O=1, the verification system updates the task status to "timeout" and performs a removal operation in the payroll data source.
[0072] Specifically, the 48-hour timeout threshold setting takes into account the reasonable execution cycle of tasks in vending machine operations (such as restocking tasks, which can usually be completed within 1-2 days). This avoids both tasks that are executed normally being incorrectly judged as timeouts due to excessively short timeframes and unfinished tasks occupying system resources for extended periods due to excessively long timeframes. (Through t...) c -t g The system uses a combination of time difference and task status to ensure the accuracy of the timeout flag O. For example, if a task is completed within 48 hours, O = 0; otherwise, O = 1. The system automatically updates the status to "timeout," allowing managers to quickly identify and address backlogged tasks, such as reassigning them to other personnel. Timeout tasks are removed from the payroll data source because incomplete tasks should not be counted towards workload. This directly ensures the fairness of payroll calculation, avoids payroll errors caused by unprocessed timeout tasks, and reduces labor disputes.
[0073] In this embodiment, during the single-interface stress test of the associated task interface in the stress test dimension, a concurrent request gradient model is adopted:
[0074] The initial concurrency is C0, and the concurrency increment is increased by ΔC at fixed time intervals until the system response time t is reached. r >T r Or error rate E r >T e In the formula, C0 is the initial concurrency, ΔC is the concurrency increment, and t r T represents the system response time. r E is the response time threshold. r For error rate, T e The error rate threshold is used; the number of concurrent connections at this point is recorded as the maximum capacity C. max .
[0075] Specifically, starting with an initial concurrency of C0, the load on the interface is gradually increased by ΔC at fixed intervals. This method can accurately pinpoint the critical point of interface performance. For example, if the initial concurrency is 100 times / second and the response is normal, the load is increased by 50 times / second each time until the response time exceeds the user's acceptable threshold T. r Or the error rate exceeds T e The number of concurrent users at this point is C. max This process simulates the change in business volume from normal to peak, more closely reflecting the load fluctuations that interfaces may face in actual operations. max Determining the parameters provides a crucial basis for system deployment. For example, if the maximum capacity of an interface is 500 concurrent users, but the actual peak business volume may reach 600, then it is necessary to improve performance by optimizing the interface (such as adding caching or optimizing database queries) or expanding the server capacity to avoid slow interface response or errors during peak business periods and to ensure that task information can be obtained in a timely manner.
[0076] In this embodiment, during the prediction of the consumption capacity of Kafka messages pushed by the task creation in the stress test dimension, a message production rate gradient is set:
[0077] The initial speed is V p 0, increasing the production rate increment ΔV at fixed time intervals. p Simultaneously monitor consumption rate V c When the message backlog Q = Q p -Q c >Q t And the duration exceeds t s At that time, it was determined that a consumption bottleneck had been reached, among which V p 0 represents the initial production rate, ΔV p V represents the production rate increment. c Q represents the consumption rate, and Q represents the message backlog. p Q represents total production. c Q represents total consumption. t t is the accumulation threshold. sThis is the duration threshold;
[0078] A consumption capacity model was fitted based on test data:
[0079] V cmax =k×V p +b
[0080] In the formula, V cmax For the maximum consumption rate, V p Let k be the production rate, and b be the model parameters.
[0081] Specifically, the message production rate V is increased through gradient boosting. p Observe the rate of consumption V c The change occurs when the message backlog Q exceeds the threshold Q. t And the duration exceeds t s When the backlog of messages exceeds 1000 and persists for 5 minutes without improvement, it indicates that the consumption capacity is insufficient. This determination considers not only the backlog volume but also the duration to avoid misjudgments caused by instantaneous fluctuations, such as messages that are quickly consumed after a short period of backlog. For example, if the backlog exceeds 1000 messages and continues for 5 minutes without improvement, it can be determined that the consumption capacity is insufficient. The fitted V... cmax =k×V p The +b model quantifies the relationship between maximum consumption rate and production rate. This model can predict the maximum processing capacity of the consumer at different production rates, providing data support for system configuration. For example, it allows adjusting the number of threads or server resources on the consumer side based on model predictions, ensuring that the Kafka message queue operates efficiently even at high production rates and avoiding task delays caused by message backlog, such as replenishment task messages not being consumed in time, leading to replenishment delays.
[0082] In this embodiment, the data consistency test dimension compares the consistency of task and record data, specifically comparing the replenishment quantity and withdrawal quantity in the replenishment task with the actual operation quantity in the replenishment record, and calculates the actual replenishment data:
[0083] R = I e -I s +S
[0084] In the formula, R is the actual replenishment quantity, and I... e This refers to the inventory after the last replenishment, I s Let S be the inventory before the first replenishment and S be the sales quantity during the replenishment period; verify the real-time updates and correlations of the data during task execution, when |RR p |≤0.05R p In the formula, R p When determining the replenishment quantity for the task plan, the data is judged to be consistent.
[0085] Specifically, the formula R = Ie -I s +S is derived from the physical laws governing inventory changes. The inventory after the last replenishment equals the inventory before the first replenishment plus the actual replenishment quantity minus the sales volume during the replenishment period. By rearranging, the actual replenishment quantity R can be obtained. This calculation method objectively reflects inventory changes in actual operation, avoiding potential errors such as omissions or misrecordings that may occur when relying directly on manual records. Allow |RR p |≤0.05R p The deviation is considered to account for minor errors that are unavoidable in actual operation, such as slight deviations in product counting, but a 5% threshold limit ensures that the deviation is within a reasonable range. For example, if the plan is to replenish 100 units, and 95-105 units are actually replenished, it is considered consistent, which ensures that the data is basically accurate while avoiding excessive verification costs caused by stringent standards. This design makes data consistency testing more in line with actual business scenarios and improves the practicality of the test.
[0086] In this embodiment, the replenishment emails and background task data in the data consistency test dimension are compared to extract the replenishment quantity E from the replenishment emails and the replenishment quantity S from the background task, and the deviation rate is calculated:
[0087]
[0088] In the formula, D is the deviation rate, E is the quantity to be supplemented in the email, and S is the quantity to be supplemented in the background task; when D=0, it is determined to be consistent; otherwise, the data generation and transmission process is traced to locate the root cause of the problem.
[0089] Specifically, calculating deviations using relative values rather than absolute values better reflects the severity of data inconsistencies. For example, when S=10, the absolute deviation of E=11 is 1 compared to when S=100, E=101. However, the former's deviation rate of 10% is much higher than the latter's 1%, allowing for more accurate identification of key differences. When D≠0, tracing the data generation process (such as the rules for extracting data from the backend for email templates and the calculation logic for the number of backend tasks) and the transmission process (such as the format conversion and encryption / decryption steps of the data interface) can pinpoint specific problem nodes (such as incorrect email template variables or data truncation during interface transmission). This process ensures that data inconsistency problems can be eradicated, rather than merely remaining at the level of superficial comparison. It guarantees the consistency between replenishment emails and backend data from the root, avoiding replenishment errors caused by information discrepancies (such as email notifications for replenishing 20 items when the backend task actually requires 30 items).
[0090] The following are experimental data based on the multi-dimensional collaborative testing method of this invention, used to verify its effectiveness:
[0091] I. Functional Testing Dimension Experimental Data: For the task generation logic test, 1000 historical business data entries (including on-machine inventory, competitor feedback, fault codes, etc.) were input into the task generation model to generate an expected task list, which was then compared with the list actually generated by the system. The results showed a matching rate M = 98.2%, with replenishment tasks achieving a matching rate of 99.1%, inspection tasks 97.5%, and maintenance tasks 98.3%, all exceeding the preset threshold T. m =95%, indicating that the task generation logic is accurate and timely. To test the task failure and timeout logic, 500 incomplete tasks were simulated, with a timeout threshold T set. o =48h. When the time exceeds 48h, the accuracy of the system timeout flag O=1 is 100%, and all timeout tasks are correctly removed from the payroll settlement data source without omission or misoperation.
[0092] II. Stress Test Dimensions and Experimental Data: A single-interface stress test was conducted on the interface for acquiring related tasks. The initial concurrency C0 = 100, increasing by ΔC = 50 every 5 minutes. When the concurrency increased to 800, the system response time t... r = 3.2s (exceeds threshold T) r =3s), error rate E r =5.3% (exceeding threshold T) e =5%), at which point the maximum load-bearing capacity C max =750. After optimization and retesting, C max The response time and error rate were both kept within the threshold after being increased to 1200, resulting in a significant improvement in interface performance.
[0093] Testing Kafka message consumption capacity, initial production rate V p0 =100 messages / second, increasing ΔV every 10 minutes p = 50 messages / second. When the production rate reaches 500 messages / second, the message backlog Q = 1200 messages and the duration exceeds t. s =After 5 minutes, the consumption bottleneck was determined. Based on the test data, a consumption capacity model was fitted. After optimizing the configuration according to the model, the consumption bottleneck was reduced to 800 messages / second, and the message backlog was controlled within Q. t =Within 1000 items.
[0094] III. Data Consistency Test Dimensions: Experimental Data: Comparison of task and record data consistency was conducted using 200 replenishment tasks, calculated according to the formula R = I... e -I s +S calculates the actual replenishment quantity and compares it with the planned quantity R. p Comparison. The results show that |RR p |≤0.05R pThe accuracy rate was 99.5%, with only one instance where the count slightly exceeded the threshold, indicating good data consistency. For replenishment emails and backend task data, 300 sets of emails were compared to the required replenishment quantity E and the backend quantity S, and the deviation rate D was calculated. Of these, 298 sets had D = 0, and 2 sets had D = 2.1%. Further investigation revealed errors in email template variable extraction; after correction, the deviation rate was 0 for all sets, ensuring data consistency.
[0095] The above data shows that, through multi-dimensional collaborative testing, this invention can effectively verify the system's functional integrity (accurate task generation and timeout logic), improve performance limits (optimized interface carrying capacity and message consumption capacity), ensure data consistency (low deviation rate in multi-scenario data comparison), and significantly improve the reliability and stability of the vending machine back-end management system.
[0096] The application scenarios of this invention are as follows:
[0097] Pre-launch testing after system development: Before the vending machine backend management system is officially put into use, functional testing is conducted to comprehensively verify the logic of task status transition, task generation, task failure and timeout, etc., to ensure that the basic functions of the system meet the requirements of the business process; stress testing is used to detect the response of related task interfaces under high concurrency requests and the consumption capacity of Kafka messages, to ensure that the system can handle daily and peak business loads after launch; data consistency testing is conducted to compare replenishment emails with backend task data, task and record data, etc., to ensure the consistency of data between different modules, laying the foundation for the smooth launch of the system.
[0098] Regular maintenance testing during system operation: During continuous system operation, tests are periodically conducted using the methods described in this invention. Functional testing can promptly identify whether task generation logic deviates due to adjustments in business rules, and whether task failure and timeout logic still executes accurately. Stress testing can monitor whether interface and message consumption capabilities experience performance degradation as business grows. Data consistency testing can identify potential data fragmentation issues that may arise during long-term operation, ensuring the system stably supports the daily operation of the vending machine, such as accurate payroll settlement, timely restocking, and maintenance tasks.
[0099] Verification testing after system function iteration: When the vending machine back-end management system is updated or optimized (such as adjusting the task generation threshold, adding new task types, etc.), functional testing is used to verify whether the new functions or the adjusted logic work normally; stress testing is used to evaluate the performance of the system under high load after iteration, to avoid the new functions from negatively affecting the system performance; data consistency testing is used to ensure that the data link remains smooth after iteration, and that the data related to the new functions can be accurately associated with the original data, so as to ensure that the system can still run reliably after iteration.
[0100] Example 2
[0101] See Figure 2 Embodiment 2 of the present invention also provides a multi-dimensional collaborative testing device for a vending machine back-end management system, including a functional testing module 100, a stress testing module 200, a data consistency testing module 300, and a test report generation module 400. The functional testing module 100, the stress testing module 200, and the data consistency testing module 300 form a collaborative relationship through a data flow link.
[0102] The functional testing module 100 is used to simulate the entire business process to generate basic test data. The test objects of the functional testing module 100 include logical tests of task status transition, task generation, task failure and timeout, replenishment task association, and location latitude and longitude information processing.
[0103] The stress testing module 200 applies load based on the interfaces and data links covered by the functional testing module 100 and records the data flow under the set load. The test objects of the stress testing module 200 include single-interface stress testing of obtaining associated task interfaces and Kafka message consumption capability testing of task creation and push.
[0104] The data consistency testing module 300 performs multi-dimensional comparisons between the basic test data and the data stream under the set load. The multi-dimensional comparisons include comparisons between replenishment emails and background task data, and comparisons between task and record data consistency.
[0105] The test report generation module 400 collects the result data from the functional test module 100, the stress test module 200, and the data consistency test module 300, performs comprehensive analysis and evaluation on the result data, and generates a test report including the test process, results, problem location, and improvement suggestions.
[0106] As a preferred solution for a multi-dimensional collaborative testing device for a vending machine back-end management system, the task generation logic test in the functional testing module 100 constructs a task generation model based on in-machine inventory, sales status, feedback records, and equipment fault triggering conditions. Specifically:
[0107] Let the replenishment task be triggered by I < T i In the formula, I represents the in-machine inventory, and T represents the inventory of goods in operation. i The inventory threshold is used; the inspection task is triggered when F ≥ T. f In the formula, F represents the frequency of competitor appearances in the feedback records, and T represents the frequency of competitor appearances. f The frequency threshold is used; the triggering condition for maintenance tasks is E≠0, where E is the equipment fault code; based on the input historical business data of the task generation model, an expected task list is generated, and compared with the actual task list generated by the system to calculate the matching rate:
[0108]
[0109] In the formula, N c For the number of consistent tasks, N t The total number of tasks; when M ≥ T m At that time, it is determined that the task generation is accurate and timely. m This is the preset matching threshold.
[0110] As a preferred solution for the multi-dimensional collaborative testing device of the vending machine back-end management system, the task failure and timeout logic test in the functional testing module 100 sets up a timeout judgment model: if t c -t g If the timeout period is greater than 48 hours and the task status is not equal to "completed", then O = 1; otherwise, O = 0. In this formula, O is the timeout flag, and t... c t represents the current time. g Set the task generation time; when O=1, the verification system updates the task status to "timeout" and performs a removal operation in the payroll data source.
[0111] As a preferred solution for a multi-dimensional collaborative testing device for a vending machine back-end management system, the single-interface stress test process of the stress testing module 200 for obtaining associated task interfaces adopts a concurrent request gradient model:
[0112] The initial concurrency is C0, and the concurrency increment is increased by ΔC at fixed time intervals until the system response time t is reached. r >T r Or error rate E r >T e In the formula, C0 is the initial concurrency, ΔC is the concurrency increment, and t r T represents the system response time. r E is the response time threshold. r For error rate, T e This is the error rate threshold; the number of concurrent connections at this point is recorded as the maximum capacity.
[0113] As a preferred solution for multi-dimensional collaborative testing devices in the vending machine back-end management system, the stress testing module 200 sets a message production rate gradient during the process of predicting the consumption capacity of Kafka messages pushed by task creation.
[0114] The initial speed is V p 0, increasing the production rate increment ΔV at fixed time intervals. p Simultaneously monitor consumption rate V c When the message backlog Q = Q p -Q c >Q t And the duration exceeds t s At that time, it was determined that a consumption bottleneck had been reached, among which Vp 0 represents the initial production rate, ΔV p V represents the production rate increment. c Q represents the consumption rate, and Q represents the message backlog. p Q represents total production. c Q represents total consumption. t t is the accumulation threshold. s This is the duration threshold;
[0115] A consumption capacity model was fitted based on test data:
[0116] V cmax =k×V p +b
[0117] In the formula, V cmax For the maximum consumption rate, V p Let k be the production rate, and b be the model parameters.
[0118] As a preferred solution for a multi-dimensional collaborative testing device for a vending machine back-end management system, the data consistency testing module 300 compares the consistency of task and record data, specifically the replenishment quantity and withdrawal quantity in the replenishment task with the actual operation quantity in the replenishment record, and calculates the actual replenishment data.
[0119] R = I e -I s +S
[0120] In the formula, R is the actual replenishment quantity, and I... e This refers to the inventory after the last replenishment, I s Let S be the inventory before the first replenishment and S be the sales quantity during the replenishment period; verify the real-time updates and correlations of the data during task execution, when |RR p |≤0.05R p In the formula, R p When determining the replenishment quantity for the task plan, the data is judged to be consistent.
[0121] As a preferred solution for a multi-dimensional collaborative testing device for a vending machine back-end management system, the data consistency testing module 300 compares replenishment emails with back-end task data, extracts the replenishment quantity E from the replenishment emails and the replenishment quantity S from the back-end tasks, and calculates the deviation rate.
[0122]
[0123] In the formula, D is the deviation rate, E is the quantity to be supplemented in the email, and S is the quantity to be supplemented in the background task; when D=0, it is determined to be consistent; otherwise, the data generation and transmission process is traced to locate the root cause of the problem.
[0124] It should be noted that the information interaction and execution process between the modules of the above-mentioned device are based on the same concept as the method embodiment in Embodiment 1 of this application, and the resulting technical effects are the same as those in the method embodiment of this application. For details, please refer to the description in the method embodiment shown above in this application, and it will not be repeated here.
[0125] Example 3
[0126] Embodiment 3 of the present invention provides a non-transitory computer-readable storage medium, wherein the computer-readable storage medium stores program code of a multi-dimensional collaborative testing method for a vending machine back-end management system, the program code including instructions for executing the multi-dimensional collaborative testing method of the vending machine back-end management system of Embodiment 1 or any possible implementation thereof.
[0127] Computer-readable storage media can be any available medium that a computer can access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives, SSDs).
[0128] Example 4
[0129] Embodiment 4 of the present invention provides an electronic device, including: a memory and a processor;
[0130] The processor and the memory communicate with each other via a bus; the memory stores program instructions that can be executed by the processor, and the processor can execute the multi-dimensional collaborative testing method of the vending machine back-end management system of Embodiment 1 or any possible implementation thereof by calling the program instructions.
[0131] Specifically, a processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently.
[0132] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
[0133] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.
[0134] Although the present invention has been described in detail above with general descriptions and specific embodiments, modifications or improvements can be made to it, which will be obvious to those skilled in the art. Therefore, all such modifications or improvements made without departing from the spirit of the present invention fall within the scope of protection claimed by the present invention.
Claims
1. A multi-dimensional collaborative testing method for a vending machine back-end management system, characterized in that, This includes functional testing, stress testing, and data consistency testing, which are interconnected through a data flow chain. The functional testing dimension simulates the entire business process to generate basic test data. The test objects of the functional testing dimension include logical tests of task status transition, task generation, task failure and timeout, replenishment task association, and location latitude and longitude information processing. The stress test dimension applies load to the interfaces and data links covered by the functional test dimension and records the data flow under the set load. The test objects of the stress test dimension include single interface stress test of obtaining associated task interface and Kafka message consumption capability test of task creation push. The data consistency test dimension compares the basic test data with the data stream under the set load in multiple dimensions. The multi-dimensional comparison includes comparing the replenishment email with the background task data and comparing the consistency between task and record data. Collect the results data from the functional testing dimension, the stress testing dimension, and the data consistency testing dimension, perform comprehensive analysis and evaluation on the results data, and generate a test report that includes the testing process, results, problem identification, and improvement suggestions.
2. The multi-dimensional collaborative testing method for a vending machine back-end management system according to claim 1, characterized in that, The task generation logic test in the aforementioned functional testing dimension constructs a task generation model based on in-machine inventory, sales status, feedback records, and equipment failure triggering conditions. Specifically: Let the replenishment task be triggered by I < T i In the formula, I represents the in-machine inventory, and T represents the inventory of goods in operation. i This is the inventory threshold; The inspection task is triggered when F ≥ T f In the formula, F represents the frequency of competitor appearances in the feedback records, and T represents the frequency of competitor appearances. f The frequency threshold is used; the triggering condition for maintenance tasks is E≠0, where E is the equipment fault code; based on the input historical business data of the task generation model, an expected task list is generated, and compared with the actual task list generated by the system to calculate the matching rate: In the formula, N c For the number of consistent tasks, N t The total number of tasks; when M ≥ T m At that time, it is determined that the task generation is accurate and timely. m This is the preset matching threshold.
3. The multi-dimensional collaborative testing method for a vending machine back-end management system according to claim 1, characterized in that, The task failure and timeout logic test in the functional testing dimension includes a timeout determination model: if t c -t g If the timeout period is greater than 48 hours and the task status is not equal to "completed", then O = 1; otherwise, O = 0. In this formula, O is the timeout flag, and t... c t represents the current time. g For task generation time; When O=1, the verification system updates the task status to "timeout" and performs a removal operation in the payroll data source.
4. The multi-dimensional collaborative testing method for a vending machine back-end management system according to claim 1, characterized in that, In the single-interface stress test of the interface for obtaining associated tasks in the stress test dimension, a concurrent request gradient model is adopted: The initial concurrency is C0, and the concurrency increment is increased by ΔC at fixed time intervals until the system response time t is reached. r >T r Or error rate E r >T e In the formula, C0 is the initial concurrency, ΔC is the concurrency increment, and t r T represents the system response time. r E is the response time threshold. r For error rate, T e The error rate threshold is used; the number of concurrent connections at this point is recorded as the maximum capacity C. max .
5. The multi-dimensional collaborative testing method for a vending machine back-end management system according to claim 1, characterized in that, In the process of predicting the consumption capacity of Kafka messages pushed by the task creation in the stress test dimension, a message production rate gradient is set: The initial speed is V p 0, increasing the production rate increment ΔV at fixed time intervals. p Simultaneously monitor consumption rate V c When the message backlog Q = Q p -Q c >Q t And the duration exceeds t s At that time, it was determined that a consumption bottleneck had been reached, among which V p 0 represents the initial production rate, ΔV p V represents the production rate increment. c Q represents the consumption rate, and Q represents the message backlog. p Q represents total production. c Q represents total consumption. t t is the accumulation threshold. s This is the duration threshold; A consumption capacity model was fitted based on test data: V cmax =k×V p +b In the formula, V cmax For the maximum consumption rate, V p Let k be the production rate, and b be the model parameters.
6. The multi-dimensional collaborative testing method for a vending machine back-end management system according to claim 1, characterized in that, The data consistency test dimension compares the consistency of task and record data, specifically comparing the replenishment quantity and withdrawal quantity in the replenishment task with the actual operation quantity in the replenishment record, and calculates the actual replenishment data: R=I e -I s +S In the formula, R is the actual replenishment quantity, and I... e This refers to the inventory after the last replenishment, I s Let S be the inventory before the first replenishment and S be the sales quantity during the replenishment period; verify the real-time updates and correlations of the data during task execution, when |RR p |≤0.05R p In the formula, R p When determining the replenishment quantity for the task plan, the data is judged to be consistent.
7. The multi-dimensional collaborative testing method for a vending machine back-end management system according to claim 1, characterized in that, In the data consistency test dimension, the replenishment emails and background task data are compared to extract the replenishment quantity E from the replenishment emails and the replenishment quantity S from the background task, and the deviation rate is calculated. In the formula, D is the deviation rate, E is the quantity to be supplemented in the email, and S is the quantity to be supplemented in the background task; when D=0, it is determined to be consistent; otherwise, the data generation and transmission process is traced to locate the root cause of the problem.
8. A multi-dimensional collaborative testing device for a vending machine back-end management system, characterized in that, It includes a functional testing module, a stress testing module, a data consistency testing module, and a test report generation module. The functional testing module, the stress testing module, and the data consistency testing module are interconnected through a data flow link. The functional testing module is used to simulate the entire business process to generate basic test data. The test objects of the functional testing module include logical tests of task status transition, task generation, task failure and timeout, replenishment task association, and location latitude and longitude information processing. The stress testing module applies load to the interfaces and data links covered by the functional testing module and records the data flow under the set load. The test objects of the stress testing module include single-interface stress testing of obtaining associated task interfaces and Kafka message consumption capability testing of task creation and push. The data consistency testing module performs multi-dimensional comparisons between the basic test data and the data stream under the set load. The multi-dimensional comparisons include comparisons between replenishment emails and background task data, and comparisons between task and record data consistency. The test report generation module collects the result data from the functional test module, the stress test module, and the data consistency test module, performs comprehensive analysis and evaluation on the result data, and generates a test report that includes the test process, results, problem identification, and improvement suggestions.
9. A multi-dimensional collaborative testing device for a vending machine back-end management system according to claim 8, characterized in that, The task generation logic test in the functional testing module constructs a task generation model based on in-machine inventory, sales status, feedback records, and equipment failure triggering conditions. Specifically: Let the replenishment task be triggered by I < T i In the formula, I represents the in-machine inventory, and T represents the inventory of goods in operation. i This is the inventory threshold; The inspection task is triggered when F ≥ T f In the formula, F represents the frequency of competitor appearances in the feedback records, and T represents the frequency of competitor appearances. f The frequency threshold is used; the triggering condition for maintenance tasks is E≠0, where E is the equipment fault code; based on the input historical business data of the task generation model, an expected task list is generated, and compared with the actual task list generated by the system to calculate the matching rate: In the formula, N c For the number of consistent tasks, N t The total number of tasks; when M ≥ T m At that time, it is determined that the task generation is accurate and timely. m Preset matching threshold; The task failure and timeout logic test in the functional test module includes a timeout determination model: if t c -t g If the timeout period is greater than 48 hours and the task status is not equal to "completed", then O = 1; otherwise, O = 0. In this formula, O is the timeout flag, and t... c t represents the current time. g For task generation time; When O=1, the verification system updates the task status to "timeout" and performs a removal operation in the payroll data source; During the single-interface stress test of the associated task interface in the stress test module, a concurrent request gradient model is adopted: The initial concurrency is C0, and the concurrency increment is increased by ΔC at fixed time intervals until the system response time t is reached. r >T r Or error rate E r >T e In the formula, C0 is the initial concurrency, ΔC is the concurrency increment, and t r T represents the system response time. r E is the response time threshold. r For error rate, T e The error rate threshold is used; the number of concurrent connections at this point is recorded as the maximum capacity C. max ; In the stress testing module, during the process of predicting the consumption capacity of pushed Kafka messages during task creation, a message production rate gradient is set: The initial speed is V p 0, increasing the production rate increment ΔV at fixed time intervals. p Simultaneously monitor consumption rate V c When the message backlog Q = Q p -Q c >Q t And the duration exceeds t s At that time, it was determined that a consumption bottleneck had been reached, among which V p 0 represents the initial production rate, ΔV p V represents the production rate increment. c Q represents the consumption rate, and Q represents the message backlog. p Q represents total production. c Q represents total consumption. t t is the accumulation threshold. s This is the duration threshold; A consumption capacity model was fitted based on test data: V cmax =k×V p +b In the formula, V cmax For the maximum consumption rate, V p Let k be the production rate, and b be the model parameters.
10. A multi-dimensional collaborative testing device for a vending machine back-end management system according to claim 8, characterized in that, The data consistency testing module compares the task and record data for consistency, specifically the replenishment quantity and withdrawal quantity in the replenishment task with the actual operation quantity in the replenishment record, and calculates the actual replenishment data. R=I e -I s +S In the formula, R is the actual replenishment quantity, and I... e This refers to the inventory after the last replenishment, I s Let S be the inventory before the first replenishment and S be the sales quantity during the replenishment period; verify the real-time updates and correlations of the data during task execution, when |RR p |≤0.05R p In the formula, R p When determining the replenishment quantity for a task plan, data consistency is considered. The data consistency testing module compares the replenishment emails with the background task data, extracts the replenishment quantity E from the replenishment emails and the replenishment quantity S from the background task, and calculates the deviation rate: In the formula, D is the deviation rate, E is the quantity to be supplemented in the email, and S is the quantity to be supplemented in the background task; when D=0, it is determined to be consistent; otherwise, the data generation and transmission process is traced to locate the root cause of the problem.
