Connectivity test method of intelligent equipment, storage medium and electronic device

Abstract

The invention discloses a connectivity test method of intelligent equipment, a storage medium and an electronic device, and relates to the technical field of intelligent home / smart home. The method comprises the following steps: acquiring a target test scene of the intelligent equipment, and determining corresponding connectivity test items and test conditions of the connectivity test items according to the target test scene; triggering an automatic test of each connectivity test item according to a test condition; according to the test process node corresponding to each connectivity test item, obtaining a buried point log of each test process node in the automatic test process, and determining a test result corresponding to the connectivity test item according to the buried point log; according to the method, the full-process automation of the connectivity test of the intelligent equipment is realized, and the accuracy of the test result and the test efficiency are improved by accurately matching the test scene and the test condition and automatically executing the test and collecting the buried point data.

Description

Technical Field

[0001] This application relates to the technical field of smart home / smart family. Specifically, it relates to a connectivity testing method, a storage medium, and an electronic device for smart devices. Background Art

[0002] The connectivity testing of a device is to verify whether a stable communication can be established and maintained between the device and the communication system, server, or other devices it is connected to by simulating the actual operating environment, and to check key performance indicators such as the integrity, speed, and error rate of data transmission, so as to ensure the normal operation and interconnection ability of the device in the network.

[0003] In the prior art, in terms of measuring the connectivity performance between smart devices and platforms / networks, it still largely relies on manually executed connectivity tests. This testing method requires professionals to manually set up test scenarios, simulate the communication situation of the device in actual use, and evaluate the connectivity by observing factors such as whether the device can successfully establish a connection, whether the data transmission is smooth, and the connection stability.

[0004] However, manual testing not only takes a long time, but also is limited by the experience and skill level of the testers, resulting in problems such as insufficient accuracy of the manual connectivity test results and low test efficiency. Summary of the Invention

[0005] This application provides a connectivity testing method, a storage medium, and an electronic device for smart devices to solve the problems of insufficient accuracy of manual connectivity test results and low test efficiency.

[0006] In a first aspect, this application provides a connectivity testing method for smart devices, including:

[0007] Obtain the target test scenario of the smart device, determine the corresponding connectivity test items and the test conditions for each connectivity test item according to the target test scenario. The test conditions include one or more of network environment, number of tests, test time interval, or test duration. The connectivity test items include one or more of the network connection duration of the smart device, the duration for the smart device to respond to a control instruction, or the connectivity availability value between the smart device and the server;

[0008] Trigger the automated test for each connectivity test item according to the test conditions;

[0009] According to the test process nodes corresponding to each connectivity test item, obtain the buried point logs of each test process node during the automated test, and determine the test results corresponding to the connectivity test items according to the buried point logs.

[0010] Optionally, determining corresponding connectivity test items and test conditions for each connectivity test item according to the target test scenario includes:

[0011] Performing text parsing on the target test scenario, matching the obtained parsing result with preset keywords, and determining the test keywords corresponding to the target test scenario;

[0012] Determining corresponding connectivity test items and test conditions for each connectivity test item according to the test keywords.

[0013] Optionally, the connectivity test items include the durations of each process for the intelligent device to establish a connection with the router. Determining the test result corresponding to the connectivity test item according to the buried point log includes:

[0014] Extracting from the buried point log the first timestamp when the intelligent device starts to connect to the router, the second timestamp when the Wi-Fi connection handshake between the intelligent device and the router is successful, and the third timestamp when the intelligent device successfully obtains an IP address;

[0015] Determining the test result of the Wi-Fi connection duration of the intelligent device as the difference between the second timestamp and the first timestamp, determining the test result of the IP address acquisition duration of the intelligent device as the difference between the third timestamp and the second timestamp, and determining the test result of the duration for the intelligent device to establish a connection with the router as the difference between the third timestamp and the first timestamp.

[0016] Optionally, the connectivity test items include the durations of each process for the intelligent device to establish a connection with the server. Determining the test result corresponding to the connectivity test item according to the buried point log includes:

[0017] Extracting from the buried point log the fourth timestamp when the intelligent device starts to connect to the server, the fifth timestamp when the intelligent device resolves the domain name of the server to an IP address, and the sixth timestamp when the intelligent device successfully connects to the server;

[0018] Determining the test result of the domain name resolution duration of the intelligent device as the difference between the fifth timestamp and the fourth timestamp, determining the test result of the transmission connection establishment duration of the intelligent device as the difference between the sixth timestamp and the fifth timestamp, and determining the test result of the duration for the intelligent device to establish a connection with the server as the difference between the sixth timestamp and the fourth timestamp.

[0019] Optionally, the connectivity test item includes the processing duration of the intelligent device in response to a control instruction. Determining the test result corresponding to the connectivity test item according to the buried point log includes:

[0020] Extracting from the buried point log the seventh timestamp when the open software development kit (OSDK) of the intelligent device receives the control instruction, the eighth timestamp when the OSDK sends the control command to the API interface of the OSDK, the ninth timestamp when the OSDK receives a control command response from the API interface, and the tenth timestamp when the OSDK issues the control command response;

[0021] Determining the sum of the difference between the eighth timestamp and the seventh timestamp and the difference between the tenth timestamp and the ninth timestamp as the test result of the device - side processing duration of the intelligent device, and determining the difference between the ninth timestamp and the eighth timestamp as the test result of the application processing duration of the intelligent device.

[0022] Optionally, the connectivity test item includes the processing duration of the intelligent device in response to a control instruction. Determining the test result corresponding to the connectivity test item according to the buried point log includes:

[0023] Extracting from the buried point log the eleventh timestamp when the open software development kit (OSDK) of the intelligent device receives the control instruction, the twelfth timestamp when the OSDK sends the control command to the motherboard of the intelligent device, the thirteenth timestamp when the OSDK receives a control command response from the motherboard, and the fourteenth timestamp when the OSDK issues the control command response;

[0024] Determining the sum of the difference between the twelfth timestamp and the eleventh timestamp and the difference between the fourteenth timestamp and the thirteenth timestamp as the test result of the device - side processing duration of the intelligent device, and determining the difference between the thirteenth timestamp and the twelfth timestamp as the test result of the motherboard processing duration of the intelligent device.

[0025] Optionally, the connectivity test item is the connectivity availability value between the device and the server. Determining the test result corresponding to the connectivity test item according to the buried point log includes:

[0026] Extracting the first quantity of data packets sent by the intelligent device to the server from the buried point log, and obtaining the second quantity of data packets received by the server. Determining the ratio of the second quantity to the first quantity as the test result of the connectivity availability value between the intelligent device and the server.

[0027] In a second aspect, the present application provides a connectivity testing device for an intelligent device, including:

[0028] An acquisition module, configured to acquire a target test scenario of the intelligent device;

[0029] A determination module, configured to determine corresponding connectivity test items and test conditions for each connectivity test item according to the target test scenario, where the test conditions include one or more of a network environment, a number of test times, a test time interval, or a test duration, and the connectivity test items include one or more of a network connection duration of the intelligent device, a duration for the intelligent device to respond to a control instruction, or a connectivity availability value between the intelligent device and a server;

[0030] A control module, configured to trigger an automated test for each of the connectivity test items according to the test conditions;

[0031] The acquisition module is further configured to acquire buried point logs for each test process node during the automated test according to the test process nodes corresponding to each connectivity test item;

[0032] The determination module is further configured to determine a test result corresponding to the connectivity test item according to the buried point logs.

[0033] Optionally, the determination module is further configured to perform text parsing on the target test scenario, match the obtained parsing result with a preset keyword, and determine a test keyword corresponding to the target test scenario;

[0034] The determination module is further configured to determine corresponding connectivity test items and test conditions for each connectivity test item according to the test keyword and the target test scenario.

[0035] Optionally, the acquisition module is further configured to extract a first timestamp when the intelligent device starts to connect to the router, a second timestamp when the Wi-Fi connection handshake between the intelligent device and the router is successful, and a third timestamp when the intelligent device successfully obtains an IP address from the buried point logs;

[0036] The determination module is further configured to determine a test result of the Wi-Fi connection duration of the intelligent device as the difference between the second timestamp and the first timestamp, determine a test result of the IP address acquisition duration of the intelligent device as the difference between the third timestamp and the second timestamp, and determine a test result of the duration for the intelligent device to establish a connection with the router as the difference between the third timestamp and the first timestamp.

[0037] Optionally, the obtaining module is further configured to extract from the buried point log a fourth timestamp when the intelligent device starts to connect to the server, a fifth timestamp when the intelligent device resolves the domain name of the server to an IP address, and a sixth timestamp when the intelligent device successfully connects to the server;

[0038] The determining module is further configured to determine the test result of the domain name resolution duration of the intelligent device as the difference between the fifth timestamp and the fourth timestamp, determine the test result of the transmission connection establishment duration of the intelligent device as the difference between the sixth timestamp and the fifth timestamp, and determine the test result of the connection establishment duration between the intelligent device and the server as the difference between the sixth timestamp and the fourth timestamp.

[0039] Optionally, the obtaining module is further configured to extract from the buried point log a seventh timestamp when the open software development kit (OSDK) of the intelligent device receives the control instruction, an eighth timestamp when the OSDK sends the control command to the API interface of the OSDK, a ninth timestamp when the OSDK receives a control command response from the API interface, and a tenth timestamp when the OSDK issues the control command response;

[0040] The determining module is further configured to determine the test result of the device-side processing duration of the intelligent device as the sum of the difference between the eighth timestamp and the seventh timestamp and the difference between the tenth timestamp and the ninth timestamp, and determine the test result of the application processing duration of the intelligent device as the difference between the ninth timestamp and the eighth timestamp.

[0041] Optionally, the obtaining module is further configured to extract from the buried point log an eleventh timestamp when the open software development kit (OSDK) of the intelligent device receives the control instruction, a twelfth timestamp when the OSDK sends the control command to the bottom board of the intelligent device, a thirteenth timestamp when the OSDK receives a control command response from the bottom board, and a fourteenth timestamp when the OSDK issues the control command response;

[0042] The determining module is further configured to determine the test result of the device-side processing duration of the intelligent device as the sum of the difference between the twelfth timestamp and the eleventh timestamp and the difference between the fourteenth timestamp and the thirteenth timestamp, and determine the test result of the bottom board processing duration of the intelligent device as the difference between the thirteenth timestamp and the twelfth timestamp.

[0043] Optionally, the obtaining module is further configured to extract a first quantity of data packets sent by the intelligent device to the server from the buried point log, and obtain a second quantity of data packets received by the server;

[0044] The determining module is further configured to determine the ratio of the second quantity to the first quantity as the test result of the connectivity availability value between the intelligent device and the server.

[0045] In a third aspect, the present application provides a connectivity testing device for an intelligent device, including:

[0046] A memory;

[0047] A processor;

[0048] Wherein, the memory stores computer-executable instructions;

[0049] The processor executes the computer-executable instructions stored in the memory to implement the connectivity testing method for the intelligent device as described in the first aspect and various possible implementations of the first aspect.

[0050] In a fourth aspect, the present application provides a computer storage medium, characterized in that the computer storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the connectivity testing method for the intelligent device as described in the first aspect and various possible implementations of the first aspect.

[0051] The connectivity testing method for the intelligent device provided by the present application obtains the target test scenario of the intelligent device, determines the corresponding connectivity test items and the test conditions for each connectivity test item according to the target test scenario, where the test conditions include one or more of a network environment, the number of tests, a test time interval, or a test duration, and the connectivity test items include: one or more of the network connection duration of the intelligent device, the duration for the intelligent device to respond to a control instruction, or the connectivity availability value between the intelligent device and the server; triggers the automated testing of each connectivity test item according to the test conditions; obtains the buried point log of each test process node during the automated testing according to the test process nodes corresponding to each connectivity test item, and determines the test result corresponding to the connectivity test item according to the buried point log; this method realizes the full-process automation of the connectivity testing of the intelligent device, and improves the accuracy of the test result and the test efficiency by accurately matching the test scenario and the test conditions, automatically executing the test and collecting the buried point data. Description of the Drawings

[0052] The drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0053] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0054] Figure 1 It is a schematic diagram of the hardware environment of the interaction method of the intelligent device provided by the present application;

[0055] Figure 2 It is the flow of the connectivity test method of the intelligent device provided by the present application Figure 1 ;

[0056] Figure 3 It is the flow of the connectivity test method of the intelligent device provided by the present application Figure 2 ;

[0057] Figure 4 It is the flow of the connectivity test method of the intelligent device provided by the present application Figure 3 ;

[0058] Figure 5 It is the flow of the connectivity test method of the intelligent device provided by the present application Figure 4 ;

[0059] Figure 6 It is the flow of the connectivity test method of the intelligent device provided by the present application Figure 5 ;

[0060] Figure 7 It is the flow of the connectivity test method of the intelligent device provided by the present application Figure 6 ;

[0061] Figure 8 It is the flow of the connectivity test method of the intelligent device provided by the present application Figure 7 ;

[0062] Figure 9 It is a schematic diagram of the structure of the connectivity test device of the intelligent device provided by the present application;

[0063] Figure 10 It is a schematic diagram of the structure of the connectivity test device of the intelligent device provided by the present application. Detailed implementation manners

[0064] To enable those skilled in the art to better understand the solution of this application, the following will clearly and completely describe the technical solutions in the embodiments of this application in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

[0065] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "include" and "have" and any of their variants are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products or devices.

[0066] Figure 1 It is a schematic diagram of the hardware environment of the interaction method of the intelligent device provided by this application. The interaction method of this smart home device is widely applied to the whole-house intelligent digital control application scenarios such as Smart Home, smart home, smart home appliance ecosystem, Intelligence House ecosystem, etc. Optionally, in this embodiment, the above-mentioned interaction method of the smart home device can be applied to, for example, Figure 1 the hardware environment composed of the terminal device 102 and the server 104 as shown. As Figure 1 shown, the server 104 is connected to the terminal device 102 through the network, and can be used to provide services (such as application services, etc.) for the terminal or the client installed on the terminal. A database can be set on the server or independently of the server to provide data storage services for the server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data operation services for the server 104.

[0067] The above network may include, but is not limited to, at least one of the following: wired network, wireless network. The above wired network may include, but is not limited to, at least one of the following: wide area network, metropolitan area network, local area network. The above wireless network may include, but is not limited to, at least one of the following: WIFI (Wireless Fidelity), Bluetooth. The terminal device 102 may not be limited to PC, mobile phone, tablet computer, smart air conditioner, smart range hood, smart refrigerator, smart oven, smart stove, smart washing machine, smart water heater, smart washing equipment, smart dishwasher, smart projection device, smart TV, smart clothes hanger, smart curtain, smart audio and video, smart socket, smart speaker, smart sound box, smart fresh air device, smart kitchen and bathroom equipment, smart bathroom equipment, smart floor sweeping robot, smart window cleaning robot, smart mopping robot, smart air purification device, smart steam box, smart microwave oven, smart kitchen water heater, smart purifier, smart water dispenser, smart door lock, etc.

[0068] The connectivity test of the device is to verify whether stable communication can be established and maintained between the device and the communication system, server or other devices it is connected to by simulating the actual operating environment, and to check key performance indicators such as the integrity, speed and error rate of data transmission, so as to ensure the normal operation and interconnection ability of the device in the network.

[0069] In the prior art, the evaluation of the connectivity performance between intelligent devices, platforms and networks mainly relies on manual connectivity tests. This requires professional personnel to manually construct test scenarios to simulate the actual communication environment of the devices, and to measure the connectivity performance of the devices in a manual evaluation manner by observing key factors such as the success rate of connection establishment, the smoothness of data transmission and the connection stability.

[0070] However, manual testing not only takes a long time, but also is limited by the experience and skill level of the testers, resulting in problems such as insufficient accuracy of the manual connectivity test results and low test efficiency.

[0071] In view of the above problems, the connectivity test method for intelligent devices provided by this application builds an intelligent mapping system of "scenario - test item - test condition". First, it analyzes the target test scenario and matches the key test elements, then automatically generates test conditions including parameters such as network environment and test frequency, triggers the automated execution of connectivity test items such as network connection duration and command response duration through a standardized process, and finally realizes the accurate quantitative analysis of the test results based on the buried point log data of the test nodes; this method improves the accuracy and test efficiency of the test results.

[0072] The following uses specific embodiments to elaborate in detail on the technical solution of this application and how the technical solution of this application solves the above technical problems. These several specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will be described below in conjunction with the accompanying drawings.

[0073] Figure 2 is the flow of the connectivity test method for the intelligent device provided by this application Figure 1 . The execution subject of this embodiment is, for example, a connectivity test system. As Figure 2 shown, the connectivity test method for the intelligent device provided in this embodiment includes:

[0074] S201: Obtain the target test scenario of the intelligent device, determine the corresponding connectivity test items and the test conditions for each connectivity test item according to the target test scenario. The test conditions include one or more of network environment, number of tests, test time interval, or test duration. The connectivity test items include: one or more of the network connection duration of the intelligent device, the duration for the intelligent device to respond to a control instruction, or the connectivity availability value between the intelligent device and the server.

[0075] Among them, the network environment is used to indicate the strength of the network signal of the intelligent device. The strength of the network signal directly affects the network connection performance of the intelligent device, including connection speed, stability, and reliability, etc.

[0076] The number of tests is used to measure the frequency of the connectivity test between the intelligent device and the server.

[0077] The test time interval refers to the time length between two connectivity tests between the intelligent device and the server.

[0078] The test duration is used to indicate the time length required for each connectivity test, including the entire process from test preparation, test execution to test result analysis.

[0079] It can be understood that, first, determine the target test scenario of the intelligent device according to its actual application requirements. For example, for smart home devices, the test scenarios may include device initial network configuration, daily remote control, multi-device linkage, or high-load network environment, etc. The selection of the target test scenario needs to combine the user usage pattern and potential abnormal situations (such as network switching, signal interference, etc.) to ensure that the test covers the key links in real applications.

[0080] The time required for the test device to start up and successfully connect to the specified network (such as Wi-Fi / Bluetooth), which is applicable to the network configuration scenario. The test conditions need to clarify the network environment (such as 2.4GHz / 5GHz frequency band), the number of tests (such as repeat 5 times), and the time interval (such as 30 seconds interval each time).

[0081] The user sends instructions (such as on / off instructions) through the APP or voice, and measures the latency from the instruction issuance to the device's completion of execution. The test conditions need to specify the instruction type, network environment (such as weak signal strength of -70dBm), and test duration (such as 1 hour continuously).

[0082] Statistically calculate the success rate of communication between the device and the server (such as the heartbeat packet loss rate). The test conditions need to set network fluctuation simulation (such as bandwidth limited to 1Mbps), number of test times (such as 100 consecutive requests), and time interval (such as once per second).

[0083] For example, when testing the "multi-device linkage" scenario, it is necessary to simultaneously detect the network connection duration (device networking efficiency) and connectivity availability (master-slave device cooperation stability), and set a stepped network environment (from full load to network disconnection and recovery) to verify robustness. The test time interval may also change dynamically (such as the first fast reconnection test interval is 10 seconds, and it is extended to 1 minute later).

[0084] S202: Trigger the automated tests for each connectivity test item according to the test conditions.

[0085] According to the preset test conditions, the connectivity test system will trigger the execution of each connectivity test item. For example, for the network connection duration test, the connectivity test system automatically simulates the device startup, connects to the specified Wi-Fi and records the time consumption, and at the same time adjusts the network frequency band or signal strength according to the test conditions; for the response control instruction duration test, the connectivity test system will periodically issue on / off instructions and statistically calculate the latency data to ensure that the number of test times and time interval meet the requirements.

[0086] After the test is completed, the connectivity test system automatically summarizes the results and generates a report. For example, in the connectivity availability numerical test, the connectivity test system will continuously initiate communication requests with the server, calculate the success rate according to the set test duration or number of times, and mark abnormal situations (such as packet loss or timeout). Automated testing not only improves efficiency but also ensures the strict consistency of test conditions (such as weak network environment, high-concurrency scenario), providing reliable data support for optimizing device connectivity.

[0087] S203: According to the test process nodes corresponding to each connectivity test item, obtain the buried point logs of each test process node during the automated test, and determine the test results corresponding to the connectivity test item according to the buried point logs.

[0088] Among them, the test process nodes are used to indicate the key steps or state points divided during the automated test, and are used to identify different stages of the connectivity test, such as device startup, network connection request, instruction issuance, server response and other links. Each node corresponds to specific test actions or state transitions, and records data such as timestamp, event status, and network parameters through buried points.

[0089] During the execution of automated tests, the connectivity test system will collect the buried point logs of each test process node corresponding to the connectivity test items in real time. For example, when testing the network connection duration, the key nodes include device startup, initiating a connection request, completing authentication, and successfully connecting to the network. Each node will record data such as timestamps, event status, and network parameters. When testing the response control instruction duration, the buried point logs will capture the exact times and result codes at stages such as instruction issuance, device reception, and execution feedback. These logs are embedded in the test process through preset probes or SDKs to ensure the integrity and real-time nature of data collection.

[0090] Based on the buried point logs, the connectivity test system determines the test results by analyzing key metrics. For example, the network connection duration is obtained by calculating the time difference from device startup to successful network connection, or the average delay from instruction issuance to reception is statistically used as the test result of the response control instruction duration. For the connectivity availability value, the connectivity test system aggregates the number of successful / failed requests in the logs and calculates the availability percentage. At the same time, abnormal logs (such as connection timeouts, instruction packet losses) will be automatically marked to assist in locating the root cause of problems, and finally a structured test report is generated.

[0091] The connectivity test method for intelligent devices provided in this embodiment obtains the target test scenario of the intelligent device, determines the corresponding connectivity test items and the test conditions for each connectivity test item according to the target test scenario. The test conditions include one or more of network environment, number of tests, test time interval, or test duration. The connectivity test items include one or more of the network connection duration of the intelligent device, the duration of the intelligent device's response to control instructions, or the connectivity availability value between the intelligent device and the server. Trigger the automated tests for each connectivity test item according to the test conditions. Obtain the buried point logs of each test process node during the automated test according to the test process nodes corresponding to each connectivity test item, and determine the test results corresponding to the connectivity test items according to the buried point logs. This method realizes the full-process automation of intelligent device connectivity testing, and improves the accuracy of test results and test efficiency by accurately matching test scenarios with test conditions, automatically executing tests, and collecting buried point data.

[0092] Figure 3 is the flow of the connectivity test method for intelligent devices provided in this application Figure 2 . As Figure 3 shown, on the basis of the Figure 2 embodiment, a detailed description is given of determining the connectivity test items of the intelligent device and the test conditions for each connectivity test item according to the target test scenario, including:

[0093] S301: Parse the text of the target test scenario, match the obtained parsing result with the preset keywords, and determine the test keywords corresponding to the target test scenario.

[0094] In the test scenario analysis stage, the connectivity test system first performs a structured parsing on the text description of the target test scenario, including techniques such as word segmentation, semantic analysis, and entity recognition in natural language processing (NLP). For example, for the scenario description "The network configuration stability of smart home devices under weak Wi-Fi signals", the parsing module will extract key entities (such as "weak Wi-Fi signal", "network configuration") and actions (such as "stability test"), and filter out irrelevant words to form standardized semantic units.

[0095] Next, the parsing result is matched with the preset keyword library. For example, "weak Wi-Fi signal" is matched to the network environment keyword "low signal strength", and "network configuration" is matched to the test type keyword "connection initialization". The matching degree is calculated through a weighting algorithm (such as TF-IDF or cosine similarity), and finally the core test keywords corresponding to the scenario are determined, such as "signal strength = -70dBm", "test item = network connection duration". This process realizes an accurate mapping from fuzzy scenario descriptions to quantifiable test conditions, providing clear input for subsequent automated tests.

[0096] S302: Determine the connectivity test items corresponding to the target test scenario according to the test keywords and the test conditions of each connectivity test item.

[0097] After completing the extraction of test keywords, the connectivity test system will associate the keywords with specific connectivity test items according to the preset rule library and test item mapping relationship. For example, if the test keywords include "low signal strength" and "network configuration", it will be automatically matched to the test item "network connection duration"; if the keywords include "remote control" and "response delay", it will correspond to the test item "response control instruction duration". For complex scenarios, the connectivity test system will intelligently split and match multiple test items. For example, a scenario that includes both "network switching" and "server communication" will be associated with two test items, "network connection duration" and "connectivity availability value".

[0098] After determining the test items, the connectivity test system further automatically generates test conditions for each test item according to the quantization parameters and scenario features in the keywords. For example, when the keyword contains "signal strength = -70dBm", the network environment is automatically set to the 2.4GHz frequency band with a signal attenuation of -70dBm; if the keyword "high concurrency" appears, the stress test conditions are configured with 100 test times and a time interval of 100ms; for keywords such as "long-term stability", a 24-hour continuous test is set, and data is recorded once per hour. The connectivity test system ensures that the test conditions can accurately reflect the scenario requirements and are executable by dynamically parsing the numerical attributes (such as "≥30 retries") and logical relationships (such as "Wi-Fi / 4G dual-network switching") of the keywords. The finally generated test plan will directly drive the execution of automated tests.

[0099] Figure 4 is the flow of the connectivity test method for intelligent devices provided by this application Figure 3 As Figure 4 shown, based on the Figure 2 embodiment, when the connectivity test item includes the duration of each process for the intelligent device to establish a connection with the router, the test results corresponding to the connectivity test item determined according to the buried point log are described in detail, including:

[0100] S401: Extract the first timestamp when the intelligent device starts to connect to the router, the second timestamp when the Wi-Fi connection handshake between the intelligent device and the router is successful, and the third timestamp when the intelligent device successfully obtains an IP address from the buried point log.

[0101] Among them, three key timestamps during the process of the intelligent device starting up and attempting to connect to the router are obtained: the first timestamp records the time point when the intelligent device starts to connect to the router, the second timestamp marks the time point when the Wi-Fi connection handshake between the intelligent device and the router is successful, and the third timestamp represents the time point when the intelligent device successfully obtains an IP address from the router. These timestamp data are important indicators for evaluating the network connection performance of the intelligent device.

[0102] The first timestamp can reveal the network initialization speed after the intelligent device starts up, helping to evaluate the response efficiency of the intelligent device during the startup phase. The second timestamp directly reflects the establishment speed of the Wi-Fi connection, which is crucial for the user experience because a fast connection can improve user satisfaction. The third timestamp indicates the ability of the intelligent device to obtain an IP address from the router, which is a key step for the intelligent device to smoothly conduct network communication.

[0103] S402: Determine the difference between the second timestamp and the first timestamp as the test result of the Wi-Fi connection duration of the smart device, determine the difference between the third timestamp and the second timestamp as the test result of the IP address acquisition duration of the smart device, and determine the difference between the third timestamp and the first timestamp as the test result of the duration for the smart device to establish a connection with the router.

[0104] Subtract the first timestamp when the smart device starts attempting to connect to the router from the second timestamp when the Wi-Fi connection handshake between the smart device and the router is successful. The resulting difference is the Wi-Fi connection duration of the smart device. Similarly, subtract the second timestamp when the Wi-Fi connection handshake is successful from the third timestamp when the smart device successfully obtains an IP address. The resulting difference represents the IP address acquisition duration of the smart device. Subtracting the first timestamp when starting to attempt the connection from the third timestamp when the IP address is successfully obtained can yield the total duration for the smart device to establish a connection with the router.

[0105] The Wi-Fi connection duration reflects the speed at which the smart device starts up and successfully establishes a Wi-Fi connection, which has a direct impact on the user experience. The IP address acquisition duration reveals the efficiency of the smart device in obtaining the IP address required for network communication from the router after the connection is successful. The total duration for the smart device to establish a connection with the router comprehensively reflects the overall performance of the smart device from startup to being fully ready for network communication. By measuring these durations, potential problems in the network connection process can be identified and resolved, thereby optimizing the connection speed and stability of the smart device.

[0106] Figure 5 is the process of the connectivity test method for the smart device provided in this application Figure 4 . As Figure 5 shown, on the basis of the Figure 2 embodiment, when the connectivity test items include the durations of each process for the smart device to establish a connection with the server, a detailed description is given of determining the test results corresponding to the connectivity test items according to the buried point logs, including:

[0107] S501: Extract from the buried point logs the fourth timestamp when the smart device starts connecting to the server, the fifth timestamp when the smart device resolves the domain name of the server to an IP address, and the sixth timestamp when the smart device successfully connects to the server.

[0108] During the process of the smart device starting to connect to the server, three key timestamps can be collected through the buried point logs: The fourth timestamp records the time point when the smart device starts connecting to the server; the fifth timestamp is the time point when the smart device successfully resolves the domain name of the server to an IP address; the sixth timestamp marks the time point when the smart device successfully establishes a connection with the server. These three timestamps together constitute the timeline of the process of the smart device connecting to the server.

[0109] First, the difference between the fourth timestamp and the fifth timestamp reflects the speed at which the intelligent device resolves domain names, which is an important part of the network connection process because the latency of domain name resolution directly affects the connection response time felt by the user. Second, the difference between the fifth timestamp and the sixth timestamp reveals the time required for the intelligent device to establish a connection successfully after the domain name resolution is completed, which helps to identify bottlenecks in the connection process. Finally, by comparing the fourth timestamp and the sixth timestamp, the total duration from when the intelligent device starts the connection to when the connection is successfully established can be obtained, which is a comprehensive indicator for measuring the connection performance of the intelligent device.

[0110] S502: Determine the test result of the domain name resolution duration of the intelligent device as the difference between the fifth timestamp and the fourth timestamp, determine the test result of the transmission connection establishment duration of the intelligent device as the difference between the sixth timestamp and the fifth timestamp, and determine the test result of the duration for the intelligent device to establish a connection with the server as the difference between the sixth timestamp and the fourth timestamp.

[0111] Subtract the fourth timestamp when the intelligent device starts connecting to the server from the fifth timestamp when the intelligent device successfully resolves the domain name of the server to obtain the difference, which is the domain name resolution duration of the intelligent device. Similarly, subtract the fifth timestamp when the domain name resolution is completed from the sixth timestamp when the intelligent device successfully establishes a connection with the server to obtain the difference, which represents the transmission connection establishment duration of the intelligent device. Subtracting the fourth timestamp when starting the connection from the sixth timestamp when the connection is successfully established can obtain the total duration for the intelligent device to establish a connection with the server.

[0112] The domain name resolution duration reflects the speed at which the intelligent device converts a human-readable domain name into a machine-readable IP address, which is the first step in the network connection and one of the key factors affecting the user experience. The transmission connection establishment duration reveals the time required for the device to establish a stable transmission connection with the server after the domain name resolution is completed, which is crucial for the efficiency and stability of data transmission. The total duration for the intelligent device to establish a connection with the server comprehensively reflects the overall performance of the intelligent device from starting the connection to successfully transmitting data. By measuring these durations, potential problems in the network connection process can be identified and solved, thereby optimizing the communication performance of the device.

[0113] Figure 6 is the flow of the connectivity test method for the intelligent device provided in this application Figure 5 . As Figure 6 shown, based on the Figure 2 embodiment, when the connectivity test item includes the processing duration of the intelligent device's response to the control instruction, the test results corresponding to the connectivity test item determined according to the buried point log are described in detail, including:

[0114] S601: Extract the seventh timestamp when the Open Software Development Kit (OSDK) of the intelligent device receives a control instruction, the eighth timestamp when the OSDK sends the control command to the API interface of the OSDK, the ninth timestamp when the OSDK receives the control command response from the API interface, and the tenth timestamp when the OSDK issues the control command response from the buried point log.

[0115] First, integrate the timestamp recording function in the OSDK (Onboard Software Development Kit). Ensure that timestamps can be accurately recorded when receiving a control instruction, sending a control command to the API (Application Programming Interface) interface, receiving a response from the API interface, and issuing a response. Second, configure the buried point log collection system to ensure that these timestamp data can be collected and stored in real time. This requires setting appropriate parameters such as log levels, collection frequencies, and storage paths. Finally, in the testing and verification phase, analyze the performance and response speed of the intelligent device by sending control instructions and observing the timestamp records. If performance issues or abnormal behaviors are found, detailed troubleshooting and optimization work can be carried out based on the timestamp records.

[0116] First, the whole process of the OSDK receiving, processing, and responding to control instructions can be understood, thus evaluating the response speed and efficiency of the system. Second, by comparing the differences between different timestamps, the time consumption of each stage can be analyzed, which helps to identify performance bottlenecks and optimize them. In addition, these timestamps can also be used as an important basis for troubleshooting. When abnormal behaviors occur in the device, the time point and link where the problem occurs can be located by checking the timestamp records. Finally, these timestamp data can also be used for performance testing and benchmark testing, providing data support for the performance optimization of intelligent devices.

[0117] S602: Determine the test result of the device-side processing duration of the intelligent device by adding the difference between the eighth timestamp and the seventh timestamp to the difference between the tenth timestamp and the ninth timestamp, and determine the test result of the application processing duration of the intelligent device by the difference between the ninth timestamp and the eighth timestamp.

[0118] Adding the difference between the eighth timestamp and the seventh timestamp to the difference between the tenth timestamp and the ninth timestamp to determine the device-side processing duration of the intelligent device; while separately determining the difference between the ninth timestamp and the eighth timestamp as the application processing duration of the intelligent device is a method for measuring and analyzing the operating efficiency of intelligent devices. By calculating the differences of these timestamps, the time spent by the intelligent device as a whole and at the application level respectively when processing tasks can be quantified.

[0119] The device - side processing duration reflects the time taken by the intelligent device from receiving a task instruction to completing the entire processing process, including the processing time of the underlying hardware and the operating system. The application processing duration, on the other hand, focuses on the response time at the application level, that is, the time from when the application receives data to when it finishes processing and is ready to send the result. By calculating these two durations separately, performance bottlenecks can be more accurately identified, and targeted optimizations can be carried out.

[0120] Figure 7 is the process of the connectivity test method for the intelligent device provided in this application Figure 6 . Such as Figure 7 shown, based on the Figure 2 embodiment, when the connectivity test item includes the processing duration of the intelligent device's response to the control instruction, a detailed description of the test results corresponding to the connectivity test item determined according to the buried - point log is given, including:

[0121] S701: Extract from the buried - point log the eleventh timestamp when the open - source software development kit (OSDK) of the intelligent device receives the control instruction, the twelfth timestamp when the OSDK sends the control command to the bottom board of the intelligent device, the thirteenth timestamp when the OSDK receives the control - command response from the bottom board, and the fourteenth timestamp when the OSDK issues the control - command response.

[0122] Log - recording codes can be added respectively when the OSDK receives the control instruction, sends the control command to the bottom board, receives the control - command response from the bottom board, and issues the control - command response. These log - recording codes should be able to accurately record the current timestamp and save it to a specified log file or database. Then, by analyzing the data in these log files or databases, the required timestamp information can be obtained, and corresponding performance evaluation and optimization work can be carried out.

[0123] Collecting these timestamps is crucial for the development and optimization of intelligent devices. First, it can help understand the latency of the OSDK in processing control instructions, thus determining whether the code or algorithm of the OSDK needs to be optimized. Second, by comparing the time difference between the OSDK sending a command to the bottom board and receiving a response from the bottom board, the response speed and performance of the intelligent device's bottom board can be evaluated. Finally, these timestamp data can also be used for fault troubleshooting. When problems occur in the control system, the problem can be quickly located by analyzing the timestamp data, improving the efficiency of problem - solving.

[0124] S702: Determine the test result of the device - side processing duration of the intelligent device by adding the difference between the twelfth timestamp and the eleventh timestamp to the difference between the fourteenth timestamp and the thirteenth timestamp, and determine the test result of the bottom - board processing duration of the intelligent device by the difference between the thirteenth timestamp and the twelfth timestamp.

[0125] The device - side processing duration is the sum of the difference between the twelfth timestamp (the time point when the OSDK sends the control command to the backplane of the intelligent device) and the eleventh timestamp (the time point when the OSDK receives the control instruction), and the difference between the fourteenth timestamp (the time point when the OSDK sends the control command response) and the thirteenth timestamp (the time point when the OSDK receives the control command response from the backplane). The backplane processing duration is the difference between the thirteenth timestamp and the twelfth timestamp. These two duration metrics are key parameters for measuring the response speed and performance of intelligent devices.

[0126] Determining the device - side processing duration and the backplane processing duration of an intelligent device is crucial for evaluating and optimizing the device's performance. The device - side processing duration reflects the overall efficiency of the OSDK in processing control instructions and generating responses, including processes such as instruction parsing, processing logic execution, and response generation. The backplane processing duration directly reflects the response speed and processing ability of the intelligent device's backplane to control commands. By comparing and analyzing these two durations, performance bottlenecks can be identified, and then targeted optimization measures can be taken to improve the overall performance and user experience of the device.

[0127] Figure 8 is the flow of the connectivity test method for the intelligent device provided by this application Figure 7 . As Figure 7 shown, based on the Figure 2 embodiment, when the connectivity test item is the connectivity availability value between the device and the server, a detailed description of the test result corresponding to the connectivity test item determined according to the buried - point log is provided, including:

[0128] S801: Extract the first quantity of data packets sent by the intelligent device to the server from the buried - point log, and obtain the second quantity of data packets received by the server. Determine the ratio of the second quantity to the first quantity as the test result of the connectivity availability value between the intelligent device and the server.

[0129] Obtaining the first quantity of data packets sent by the intelligent device to the server collected through the buried - point log and the second quantity of data packets received by the server, and determining the ratio of these two quantities as the connectivity availability value between the intelligent device and the server is a method for measuring the communication quality between the intelligent device and the server. The buried - point log refers to the preset log recording points in the code of the intelligent device, which are used to collect various data generated during the device's operation, including the number of data packets sent to the server. By comparing the number of data packets sent by the device (the first quantity) and the number of data packets actually received by the server (the second quantity), the connectivity availability value can be calculated, and this value reflects the success rate of data transmission and the stability of the communication link.

[0130] Determining the connectivity availability value between the intelligent device and the server is crucial for evaluating and optimizing the communication performance of the intelligent device. The connectivity availability value directly reflects the reliability and stability of the communication link between the device and the server. If the connectivity availability value is low, it indicates a high packet loss rate during data transmission, which may be caused by reasons such as network instability, device failure, or insufficient server processing capacity. By regularly monitoring and analyzing the connectivity availability value, communication problems can be discovered and resolved in a timely manner, thereby improving the overall performance and user experience of the device. In addition, the connectivity availability value is also one of the important indicators for measuring the communication quality of intelligent devices, which has an important impact on the market competitiveness of products and user satisfaction.

[0131] Figure 9 It is a schematic structural diagram of the connectivity test device for the intelligent device provided by this application. As Figure 9 shown, this application provides a connectivity test device for an intelligent device. The connectivity test device 900 of this intelligent device includes:

[0132] An acquisition module 901, configured to acquire the target test scenario of the intelligent device;

[0133] A determination module 902, configured to determine the corresponding connectivity test items and the test conditions for each connectivity test item according to the target test scenario. The test conditions include one or more of a network environment, the number of test times, a test time interval, or a test duration. The connectivity test items include: one or more of the network connection duration of the intelligent device, the duration for the intelligent device to respond to a control instruction, or the connectivity availability value between the intelligent device and the server;

[0134] A control module 903, configured to trigger the automated test for each of the connectivity test items according to the test conditions;

[0135] The acquisition module 901 is further configured to acquire the buried point logs of each test process node during the automated test according to the test process nodes corresponding to each connectivity test item;

[0136] The determination module 902 is further configured to determine the test results corresponding to the connectivity test items according to the buried point logs.

[0137] Optionally, the determination module 902 is further configured to perform text parsing on the target test scenario, match the obtained parsing result with a preset keyword, and determine the test keyword corresponding to the target test scenario;

[0138] The determination module 902 is further configured to determine the corresponding connectivity test items and the test conditions for each connectivity test item according to the test keyword based on the target test scenario.

[0139] Optionally, the obtaining module 901 is further configured to extract from the buried point log a first timestamp when the intelligent device starts to connect to the router, a second timestamp when the Wi-Fi connection handshake between the intelligent device and the router is successful, and a third timestamp when the intelligent device successfully obtains an IP address;

[0140] The determining module 902 is further configured to determine the difference between the second timestamp and the first timestamp as the test result of the Wi-Fi connection duration of the intelligent device, determine the difference between the third timestamp and the second timestamp as the test result of the IP address obtaining duration of the intelligent device, and determine the difference between the third timestamp and the first timestamp as the test result of the connection establishment duration between the intelligent device and the router.

[0141] Optionally, the obtaining module 901 is further configured to extract from the buried point log a fourth timestamp when the intelligent device starts to connect to the server, a fifth timestamp when the intelligent device resolves the domain name of the server to an IP address, and a sixth timestamp when the intelligent device successfully connects to the server;

[0142] The determining module 902 is further configured to determine the difference between the fifth timestamp and the fourth timestamp as the test result of the domain name resolution duration of the intelligent device, determine the difference between the sixth timestamp and the fifth timestamp as the test result of the transmission connection establishment duration of the intelligent device, and determine the difference between the sixth timestamp and the fourth timestamp as the test result of the connection establishment duration between the intelligent device and the server.

[0143] Optionally, the obtaining module 901 is further configured to extract from the buried point log a seventh timestamp when the open software development kit (OSDK) of the intelligent device receives the control instruction, an eighth timestamp when the OSDK sends the control command to the API interface of the OSDK, a ninth timestamp when the OSDK receives a control command response from the API interface, and a tenth timestamp when the OSDK issues the control command response;

[0144] The determining module 902 is further configured to determine the sum of the difference between the eighth timestamp and the seventh timestamp and the difference between the tenth timestamp and the ninth timestamp as the test result of the device-side processing duration of the intelligent device, and determine the difference between the ninth timestamp and the eighth timestamp as the test result of the application processing duration of the intelligent device.

[0145] Optionally, the obtaining module 901 is further configured to extract from the buried point log the eleventh timestamp when the open software development kit (OSDK) of the intelligent device receives the control instruction, the twelfth timestamp when the OSDK sends the control command to the motherboard of the intelligent device, the thirteenth timestamp when the OSDK receives a control command response from the motherboard, and the fourteenth timestamp when the OSDK sends out the control command response;

[0146] The determining module 902 is further configured to determine the difference between the twelfth timestamp and the eleventh timestamp, plus the difference between the fourteenth timestamp and the thirteenth timestamp, as the test result of the device-side processing duration of the intelligent device, and determine the difference between the thirteenth timestamp and the twelfth timestamp as the test result of the motherboard processing duration of the intelligent device.

[0147] Optionally, the obtaining module 901 is further configured to extract from the buried point log the first quantity of data packets sent by the intelligent device to the server, and obtain the second quantity of data packets received by the server;

[0148] The determining module 902 is further configured to determine the ratio of the second quantity to the first quantity as the test result of the connectivity availability value between the intelligent device and the server.

[0149] Figure 10 It is a schematic structural diagram of a connectivity test device for an intelligent device provided by the present application. As Figure 10 shown, the present application provides a connectivity test device for an intelligent device. The connectivity test device 1000 for the intelligent device includes: a receiver 1001, a transmitter 1002, a processor 1003, and a memory 1004.

[0150] The receiver 1001 is configured to receive instructions and data;

[0151] The transmitter 1002 is configured to send instructions and data;

[0152] The memory 1004 is configured to store computer-executable instructions;

[0153] The processor 1003 is configured to execute the computer-executable instructions stored in the memory 1004 to implement each step performed by the connectivity test method of the intelligent device in the foregoing embodiments. For details, reference may be made to the relevant descriptions in the foregoing embodiments of the connectivity test method of the intelligent device.

[0154] Optionally, the foregoing memory 1004 may be either independent or integrated with the processor 1003.

[0155] When the memory 1004 is independently provided, the electronic device further includes a bus for connecting the memory 1004 and the processor 1003.

[0156] The present application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the connectivity test method of the intelligent device performed by the connectivity test device of the intelligent device as described above. The above are only the preferred embodiments of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A connectivity test method for an intelligent device, characterized in that, Including: Obtain the target test scenario of the intelligent device, determine the corresponding connectivity test items and the test conditions for each connectivity test item according to the target test scenario, where the test conditions include one or more of network environment, number of tests, test time interval, or test duration, and the connectivity test items include one or more of the network connection duration of the intelligent device, the duration for the intelligent device to respond to a control instruction, or the connectivity availability value between the intelligent device and the server; Trigger the automated tests for each of the connectivity test items according to the test conditions; According to the test process nodes corresponding to each of the connectivity test items, obtain the buried point logs of each of the test process nodes during the automated test, and determine the test results corresponding to the connectivity test items according to the buried point logs.

2. The method according to claim 1, wherein The determining the corresponding connectivity test items and the test conditions for each connectivity test item according to the target test scenario includes: Perform text parsing on the target test scenario, match the obtained parsing result with preset keywords, and determine the test keywords corresponding to the target test scenario; Determine the corresponding connectivity test items and the test conditions for each connectivity test item according to the test keywords.

3. The method according to claim 1, characterized in that, The connectivity test items include the durations of each process for the intelligent device to establish a connection with the router. The determining the test results corresponding to the connectivity test items according to the buried point logs includes: Extract from the buried point log the first timestamp when the intelligent device starts to connect to the router, the second timestamp when the Wi-Fi connection handshake between the intelligent device and the router is successful, and the third timestamp when the intelligent device successfully obtains an IP address; Determine the test result of the Wi-Fi connection duration of the intelligent device as the difference between the second timestamp and the first timestamp, determine the test result of the IP address acquisition duration of the intelligent device as the difference between the third timestamp and the second timestamp, and determine the test result of the duration for the intelligent device to establish a connection with the router as the difference between the third timestamp and the first timestamp.

4. The method according to claim 1, characterized in that The connectivity test items include the durations of each process for the intelligent device to establish a connection with the server. The determining the test results corresponding to the connectivity test items according to the buried point logs includes: Extract from the buried point log the fourth timestamp when the intelligent device starts to connect to the server, the fifth timestamp when the intelligent device resolves the domain name of the server to an IP address, and the sixth timestamp when the intelligent device successfully connects to the server; Determine the test result of the domain name resolution duration of the intelligent device as the difference between the fifth timestamp and the fourth timestamp, determine the test result of the transmission connection establishment duration of the intelligent device as the difference between the sixth timestamp and the fifth timestamp, and determine the test result of the duration for the intelligent device to establish a connection with the server as the difference between the sixth timestamp and the fourth timestamp.

5. The method according to claim 1, characterized in that The connectivity test items include the processing duration of the intelligent device's response to the control instruction. Determining the test result corresponding to the connectivity test item according to the buried point log includes: Extracting from the buried point log the seventh timestamp when the open software development kit (OSDK) of the intelligent device receives the control instruction, the eighth timestamp when the OSDK sends the control command to the API interface of the OSDK, the ninth timestamp when the OSDK receives the control command response from the API interface, and the tenth timestamp when the OSDK sends out the control command response; Determining the test result of the device-side processing duration of the intelligent device by adding the difference between the eighth timestamp and the seventh timestamp to the difference between the tenth timestamp and the ninth timestamp, and determining the test result of the application processing duration of the intelligent device by the difference between the ninth timestamp and the eighth timestamp.

6. The method according to claim 1, wherein The connectivity test items include the processing duration of the intelligent device's response to the control instruction. Determining the test result corresponding to the connectivity test item according to the buried point log includes: Extracting from the buried point log the eleventh timestamp when the open software development kit (OSDK) of the intelligent device receives the control instruction, the twelfth timestamp when the OSDK sends the control command to the motherboard of the intelligent device, the thirteenth timestamp when the OSDK receives the control command response from the motherboard, and the fourteenth timestamp when the OSDK sends out the control command response; Determining the test result of the device-side processing duration of the intelligent device by adding the difference between the twelfth timestamp and the eleventh timestamp to the difference between the fourteenth timestamp and the thirteenth timestamp, and determining the test result of the motherboard processing duration of the intelligent device by the difference between the thirteenth timestamp and the twelfth timestamp.

7. The method according to claim 1, characterized in that, The connectivity test item is the connectivity availability value between the device and the server. Determining the test result corresponding to the connectivity test item according to the buried point log includes: Extracting the first quantity of data packets sent by the intelligent device to the server from the buried point log, and obtaining the second quantity of data packets received by the server, and determining the test result of the connectivity availability value between the intelligent device and the server by the ratio of the second quantity to the first quantity.

8. A connectivity testing device for an intelligent device, characterized in that, Including: An acquisition module for acquiring the target test scenario of the intelligent device; A determination module for determining the corresponding connectivity test items and the test conditions of each connectivity test item according to the target test scenario. The test conditions include one or more of network environment, number of tests, test time interval, or test duration. The connectivity test items include one or more of the network connection duration of the intelligent device, the duration of the intelligent device's response to the control instruction, or the connectivity availability value between the intelligent device and the server; A control module for triggering the automated test of each connectivity test item according to the test conditions. The obtaining module is further configured to obtain the buried point logs of each of the test process nodes in the automated test process according to the test process nodes corresponding to each of the connectivity test items; The determining module determines the test result corresponding to the connectivity test item according to the buried point logs.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when running, executes the method according to any one of claims 1 to 7.

10. An electronic device, comprising a memory and a processor, characterized in that, A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 7 through the computer program.

Images