Bluetooth product testing method and device and terminal equipment

Abstract

The invention provides a Bluetooth product testing method and device and terminal equipment, and the method comprises the steps: obtaining a configuration file, the configuration file comprises to-be-tested product condition information used for defining and judging whether the to-be-tested product is a standard of a to-be-tested product, and at least one test item, the at least one test item is used for defining a to-be-tested item of the to-be-tested product, and the to-be-tested item is used for determining whether the to-be-tested item is a to-be-tested item of the to-be-tested product; each of the at least one test item comprises a plurality of test nodes; according to the condition information of the to-be-tested products, Bluetooth products meeting the condition are searched, the searched Bluetooth is connected with target Bluetooth products corresponding to the product identifiers in the to-be-tested product queue in sequence, at least one test item is executed in sequence, and for each executed test item, the Bluetooth products corresponding to the product identifiers in the to-be-tested product queue are detected. And sequentially executing the plurality of test nodes contained in the test item. The Bluetooth product testing method is beneficial to improving the testing efficiency and simplifying the testing process.

Description

Technical Field

[0001] The present invention relates to the technical field of Bluetooth testing, and in particular to a Bluetooth product testing method, device and terminal equipment. Background Art

[0002] After the Bluetooth product is manufactured in the factory, it needs to be tested for functionality to check whether the software functions of the Bluetooth product are intact. Currently, testing of Bluetooth products is generally done by making a test board, which is connected to the corresponding Bluetooth product through a specific test board to achieve functional testing of the Bluetooth product.

[0003] During the test, the products to be tested need to be connected to the test board one by one through Near Field Communication (NFC), that is, the test board needs to be close to the products to be tested one by one, or the products to be tested need to be close to the test board one by one, in order to achieve connection and testing.

[0004] There is another test method that requires reading the unique identifiers (such as MAC addresses) of the products to be tested into the test board one by one, and then establishing connections with the products to be tested one by one based on the unique identifiers. When there are a large number of products to be tested, this method is more troublesome to enter the MAC addresses; when there are many types of products to be tested, the test files in the test board need to be reconfigured, and even the test board needs to be replaced, which is inconvenient.

[0005] It can be seen that the existing Bluetooth product testing methods have problems such as complex testing equipment, cumbersome testing process, low testing efficiency, and high labor costs.

[0006] Therefore, it is urgent to provide a Bluetooth product testing method that is conducive to improving test efficiency, simplifying test procedures, and reducing labor costs. Summary of the invention

[0007] The present application provides a Bluetooth product testing method, apparatus and terminal device, which are helpful in improving the testing efficiency of Bluetooth products, simplifying the testing process and reducing the testing cost when testing Bluetooth products.

[0008] In a first aspect, the present application provides a Bluetooth product testing method, which is applied to a terminal device, and the testing method includes: obtaining a configuration file, the configuration file including condition information of a product to be tested and at least one test item, wherein the condition information of the product to be tested is used to define the standard for determining whether it is a product to be tested, and the at least one test item is used to define the test items of the product to be tested, and each of the at least one test item includes multiple test nodes; searching for qualified Bluetooth products according to the condition information of the product to be tested, and storing the product identifiers corresponding to the found Bluetooth products in a queue of products to be tested in a certain order; establishing connections with target Bluetooth products corresponding to the product identifiers in the queue of products to be tested in turn, and executing at least one test item in turn, and for each test item executed, executing the multiple test nodes contained in the test item in turn.

[0009] In the Bluetooth product testing method provided in the present application, the product to be tested is abstracted into a configurable data item. Specifically, the product condition information for defining the standard of the product to be tested is configured in the configuration file to define the condition of a product as the product to be tested. Based on a configuration file, multiple qualified products to be tested can be screened out for testing. That is to say, through the product condition information in the configuration file, multiple Bluetooth products can be range-screened to achieve batch testing. Moreover, for the products to be tested that need to be tested, the same test items between the products to be tested are obtained, and the test of the products to be tested is abstracted into test items and each test node in the test items. In this way, by configuring a configuration file, multiple test items of at least one product to be tested can be automatically tested, which reduces the number of configuration files that need to be configured when testing multiple products to be tested, simplifies the test process, and is conducive to improving the testing efficiency of Bluetooth products.

[0010] Furthermore, the Bluetooth product testing method of the present application will store the product identifications corresponding to the qualified Bluetooth products found according to the condition information of the product to be tested in a certain order into the queue of products to be tested. During the testing process, the Bluetooth products corresponding to the product identifications in the queue of products to be tested will be tested in turn. By importing the configuration file, it is possible to perform automated testing on batches of Bluetooth products that meet the conditions specified in the configuration file, thereby further improving the testing efficiency of the products. Moreover, the Bluetooth products that meet the conditions specified in the configuration file will be screened in advance, and only one screening process is required, which is conducive to reducing the occupancy of terminal device resources, further accelerating testing efficiency and simplifying the testing process.

[0011] Moreover, the Bluetooth product testing method of the present application is applied on a terminal device, which is portable. When a region or production line needs to be tested, the terminal device that is not being tested temporarily can be moved to a different region or production line for testing. This is beneficial to improving the flexibility of the use of test equipment when testing Bluetooth products, reducing the number of test equipment required for Bluetooth product testing, and reducing testing costs.

[0012] In summary, the Bluetooth product testing method provided in this application is conducive to improving testing efficiency, simplifying testing procedures, reducing terminal device resource usage, and reducing testing costs.

[0013] In a possible implementation, at least one test entry includes a test parameter, wherein the test parameter includes an operation identifier.

[0014] During the testing process, the technicians of the present application discovered that each operation identifier indicates that a Bluetooth product performs a certain action, and the operation identifiers used to indicate the execution of the same action for a type of product may be the same. Based on this discovery, the present application configures the test items according to the operation identifiers in the test items for the products to be tested. That is to say, for the products to be tested, the test items have the same operation identifiers. When configuring the configuration file, each test item is abstracted according to the test parameters, so that one type of multiple Bluetooth products can be tested in one batch. Moreover, based on the above discovery, even when the operation identifiers of different types of products for executing a certain action are configured to be the same during the development stage, multiple types of Bluetooth products can be tested in one batch, which is conducive to improving the testing efficiency of Bluetooth products.

[0015] In a possible implementation, the operation identifier includes a service identifier and a channel identifier, wherein the channel identifier includes a read-write feature identifier or a notification feature identifier.

[0016] During the testing process, the technical personnel of the present application discovered that Bluetooth products need corresponding service identifiers and channel identifiers to provide corresponding services so that the Bluetooth products can identify the actions to be performed. For multiple Bluetooth products that need to be tested, if the test items have the same service identifier and channel identifier, when configuring the configuration file, each test item is abstracted according to the test parameters, so that multiple Bluetooth products of one type can be tested in one batch. Moreover, based on the above findings, even when the service identifiers and channel identifiers of different types of products for performing a certain action are configured to be the same during the development stage, it is even possible to test multiple types of Bluetooth products in one batch, which is conducive to improving the testing efficiency of Bluetooth products.

[0017] In one possible implementation, the condition information of the product to be tested includes the Bluetooth name template of the product to be tested and the critical value of the received signal strength, wherein the Bluetooth name template of the product to be tested is the same part of the Bluetooth name of the product to be tested, and the critical value of the received signal strength is used to define the minimum signal strength value received from the product to be tested on the terminal device.

[0018] In a possible implementation, the condition information of the product to be tested includes a broadcast identification template and a received signal strength threshold of the product to be tested, wherein the broadcast identification template of the product to be tested is the same part of the broadcast identification of the product to be tested.

[0019] The technical personnel of this application have found that the conditions that can be used to distinguish the products to be tested have some of the same features in the same category of products. Based on this discovery, these partially identical features are extracted as conditions for distinguishing the products to be tested, and range distinction can be achieved in multiple Bluetooth products. Specifically, when there are many products to be tested, the same part of the Bluetooth name of the product to be tested and the critical value of the received signal strength of the product to be tested are used to define the standard for judging whether it is the product to be tested, or the same part of the broadcast identifier of the product to be tested and the critical value of the received signal strength of the product to be tested are used to define the standard for judging whether it is the product to be tested. By using the same part of the Bluetooth name or broadcast identifier of the product to be tested and combining it with the signal strength range, there is no need to enter all the Bluetooth names or broadcast identifiers of each product to be tested in the configuration file. The identifier that can distinguish the signals of the products to be tested within a certain range is used to configure the condition information of the products to be tested, which is conducive to simplifying the configuration process of the configuration file and reducing the time for configuring the configuration file, thereby further simplifying the test process and improving the test efficiency.

[0020] In a possible implementation, the condition information of the product to be tested and the at least one test item are associated with each other.

[0021] In a possible implementation, the configuration file further includes additional product condition information to be tested and at least one additional test item corresponding to the additional product condition information to be tested, and the product corresponding to the product condition information to be tested and the product corresponding to the additional product condition information to be tested are tested in sequence.

[0022] As can be seen from the above, the configuration file in the present application may further include additional product condition information to be tested and at least one additional test item corresponding to the additional product condition information to be tested. For products to be tested that need to test different test items, the same test items between the products to be tested are obtained, and the characteristics of the products to be tested on the test items are used to correspond the products to be tested to at least one test item. The correspondence between multiple different products to be tested and at least one test item is configured in one configuration file. In this way, batch testing of multiple products to be tested that need to test different test items can be achieved by configuring one configuration file. Moreover, the products to be tested and the test items correspond, that is, the products to be tested and the test items are associated. When configuring the configuration file, for each group of products to be tested, each test item of each group of products to be tested is abstracted according to the test parameters, so that one type of multiple Bluetooth products can be tested in one batch, and even multiple types of Bluetooth products can be tested in one batch. This is conducive to further improving the test efficiency and simplifying the test process.

[0023] In a possible implementation, feedback data generated by a target Bluetooth product in response to executing at least one test item is received; and a test document of the target Bluetooth product is generated according to the feedback data.

[0024] From the above, it can be seen that the present application further generates a test document for the target Bluetooth product after executing at least one test item, and records the data generated by the test phase of the target Bluetooth product. In this way, the test phase can be traced back through the test document. In the event that the target Bluetooth product test fails, it is helpful to obtain the cause of the test failure based on the test document, which is helpful to obtain more accurate and detailed test results.

[0025] In a possible implementation, the configuration file also includes result description data, which is used to indicate how the test result of the product to be tested is displayed in response to executing the at least one test item; and the Bluetooth product testing method further includes: generating an indication signal according to the result description data.

[0026] From the above, it can be seen that in this application, result description data is configured in the configuration file, which can display the test results of the product to be tested after executing at least one test item to improve the visibility of the test results, and can directly determine the test results through observation. Based on the indicator signal, it can quickly distinguish between Bluetooth products that succeeded and failed the test, which is conducive to further accelerating the test efficiency and simplifying the test process.

[0027] In a second aspect, the present application also provides a Bluetooth product testing device, which is applied to a terminal device, including: An acquisition unit is used to acquire a configuration file, wherein the configuration file includes condition information of the product to be tested and at least one test item, wherein the condition information of the product to be tested is used to define the standard for determining whether it is a product to be tested, and the at least one test item is used to define the test items of the product to be tested, and each of the at least one test item includes multiple test nodes.

[0028] The product determination unit is used to search for Bluetooth products that meet the conditions according to the condition information of the product to be tested, and store the product identifications corresponding to the found Bluetooth products in a queue of products to be tested in a certain order.

[0029] The test unit is used to establish connections with target Bluetooth products corresponding to product identifiers in the product queue to be tested in sequence, and execute at least one test item in sequence, and for each test item executed, execute multiple test nodes contained in the test item in sequence.

[0030] In a third aspect, the present application also provides a terminal device, comprising: at least one processor; and a memory communicatively connected to the at least one processor, wherein the memory stores instructions that can be executed by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor can execute the Bluetooth product testing method as in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0032] Figure 1 A schematic diagram of a communication architecture provided for an embodiment of the present application; Figure 2 A flowchart of a Bluetooth product testing method provided in an embodiment of the present application; Figure 3 A schematic diagram of the execution of a test node in a test item provided in an embodiment of the present application; Figure 4 A schematic diagram of a configuration file provided in an embodiment of the present application; Figure 5 A schematic diagram of another configuration file provided in an embodiment of the present application; Figure 6 A schematic diagram of another configuration file provided in an embodiment of the present application; Figure 7 A schematic diagram of a Bluetooth product testing device provided in an embodiment of the present application; Figure 8 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention. The terms used in the implementation mode of the present invention are only used to explain the specific embodiments of the present invention, and are not intended to limit the present invention.

[0034] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0035] See also Figure 1 , Figure 1 This is a schematic diagram of a communication architecture involved in the embodiment of the present application. Figure 1 Make an introduction.

[0036] Figure 1 The present invention includes five products to be tested, namely massager 101, massager 102, massager 103, massager 104 and massager 105. In the embodiment of the present application, the above-mentioned multiple products to be tested and the terminal device 20 all have Bluetooth functions, and communication can be established via Bluetooth to implement testing. Test instructions are issued to each product to be tested in turn via the terminal device 20.

[0037] The Bluetooth name of the massager 101 is AMY-101, the broadcast identifier is 04500042101, and the received signal strength indicator (Received Signal Strength Indicator) of the massager 101 received by scanning on the terminal device 20 is The Bluetooth name of massager 102 is AMY-102, the broadcast identifier is 04500042102, and the RSSI value of massager 102 received on terminal device 20 is -40; the Bluetooth name of massager 103 is AMY-103, the broadcast identifier is 04500042103, and the RSSI value of massager 103 received on terminal device 20 is -50; the Bluetooth name of massager 104 is AMY-104, the broadcast identifier is 04500042104, and the RSSI value of massager 104 received on terminal device 20 is -60; the Bluetooth name of massager 105 is AMY-105, the broadcast identifier is 04500042105, and the RSSI value of massager 105 received on terminal device 20 is -70.

[0038] The RSSI value is usually expressed as a negative number dBm (decibel milliwatt). The closer the RSSI value is to zero, the stronger the received signal strength is. The RSSI value is affected by the transmission distance, obstacles, interference, etc. Specifically, if the signal strength of the massager 101 received by the terminal device 20 is -30, and the signal strength of the massager 102 received by the terminal device 20 is -40, then the received signal strength from the massager 101 received on the terminal device 20 is stronger.

[0039] In the embodiments of the present application, the product to be tested is taken as a massager for example. Optionally, in other embodiments of the present application, the product to be tested may also be other products with Bluetooth function, such as an electric toothbrush, a massager, a Bluetooth headset, an electronic scale, a Bluetooth speaker or other products with Bluetooth function, which are not listed one by one here.

[0040] It should be noted that although Figure 1 It is shown that each massager 101 is directly connected to the terminal device 20, but this direct connection is a logical relationship. That is to say, even if each massager 101 is connected to the terminal device 20 through one or more relay devices, as long as the connection formed is logically interconnected between each massager 101 and the terminal device 20, it is a logical connection. Figure 1 Within the scope of the communication architecture shown.

[0041] It should be noted that in the embodiment of the present application, the number of products to be tested is 5 as an example. In other embodiments of the present application, the number of products to be tested may also be other numbers, such as 1, 10, 50, 100 or more.

[0042] It should be noted that the terminal device 20 can be a mobile device or a fixed terminal. The mobile device can be a handheld terminal, a laptop, a smart phone, a tablet computer, a machine type communication terminal, a controller or other devices; the fixed terminal can be a fixed test bench, a desktop computer or other devices.

[0043] At present, the testing of Bluetooth products is generally carried out by making a test board, and connecting the corresponding Bluetooth products through a specific test board to achieve the functional testing of Bluetooth products. During the test process, the products to be tested need to be connected to the test board one by one through Near Field Communication (NFC), that is, the test board needs to be close to the products to be tested one by one, or the products to be tested need to be close to the test board one by one, in order to achieve connection and testing. There is also a test method that requires the unique identifier (such as MAC address) of the product to be tested to be read into the test board one by one, and then establish a connection with the product to be tested one by one according to the unique identifier. When the number of products to be tested is large, this method is more troublesome to enter the MAC address; when there are many types of products to be tested, the test files in the test board need to be reconfigured, and even the test board needs to be replaced, which is inconvenient.

[0044] In this regard, the technicians of the present application provide a Bluetooth product testing method, which implements batch testing of multiple products to be tested through the above-mentioned terminal device 20.

[0045] See also Figure 2 , Figure 2 Flow chart of a Bluetooth product testing method provided in an embodiment of the present application. The Bluetooth product testing method is applied to a terminal device 20, such as Figure 2 As shown, the Bluetooth product testing method in the embodiment of the present application includes steps S200-S202.

[0046] Step S200 is: obtaining a configuration file, the configuration file including the condition information of the product to be tested and at least one test item, wherein the condition information of the product to be tested is used to define the standard for determining whether it is a product to be tested, and the at least one test item is used to define the test items of the product to be tested, and each of the at least one test item includes multiple test nodes. The description of steps S201 and S202 is detailed in the following text of this application document.

[0047] The configuration file is used to be imported into the terminal device when the Bluetooth product needs to be tested, so that the terminal device can know which Bluetooth products or types of Bluetooth products are the products to be tested, the test items to be tested on the products to be tested, and the various test nodes of the test process of each test item. During the Bluetooth product testing process, the configuration file is imported into the terminal device so that the terminal device can test multiple Bluetooth products or multiple types of Bluetooth products in batches according to the configuration file.

[0048] The configuration file includes condition information of the product to be tested and at least one test item, wherein the condition information of the product to be tested is configured with a standard for defining whether it is a product to be tested, and the condition information of the product to be tested can be used to determine which Bluetooth products or types of Bluetooth products are the products to be tested. For example, the Bluetooth products include massagers 101, massagers 102, and massagers 103. By configuring the condition information of the product to be tested, the standard that massagers 101 and 102 are the products to be tested can be defined. Therefore, during the Bluetooth product testing process, the terminal device can identify the products to be tested as massagers 101 and 102 among massagers 101, 102, and 103 based on the condition information of the product to be tested in the configuration file.

[0049] At least one test entry in the configuration file is used to define the test items of the product to be tested, and each of the at least one test entry includes multiple test nodes, wherein the test nodes contained in each test entry are various execution nodes of the test flow of each test item. During the Bluetooth product testing process, the terminal device can test each item to be tested for each product to be tested in turn according to the items to be tested defined in the configuration file, and for each test item executed, each test node of the test item is executed in turn.

[0050] For details on the test items, please refer to the attached Figure 3 , attached Figure 3 A schematic diagram of the execution of test nodes in the test entry provided in the present application. Test entry 301 includes n test nodes. According to the configuration order of the n test nodes in the test entry, when executing the test entry 301, test node 1, test node 2, test node 3, test node 4, until test node n are executed in sequence. After the n test nodes are executed in sequence, it means that the execution of test entry 301 is completed.

[0051] For example, a test item for querying the power level is configured in the configuration file, and two test nodes of the test item are configured according to the various execution nodes of the test process for querying the power level (such as establishing a secure link and querying the power level). During the Bluetooth product testing process, the terminal device can perform a power query test on each product to be tested in turn according to the test item defined in the configuration file, i.e., querying the power level, and for the test item for querying the power level in the configuration file, the two test nodes of establishing a secure link and querying the power level are executed in turn.

[0052] Step S201 is: searching for Bluetooth products that meet the conditions according to the condition information of the product to be tested, and storing the product identifications corresponding to the found Bluetooth products in a queue of products to be tested in a certain order. The description of step S202 is detailed in the following text of this application document.

[0053] In the embodiment of the present application, the terminal device searches according to the product condition information to be tested in the configuration file to find a Bluetooth product that meets the product standard to be tested defined by the product condition information to be tested, and then stores the product identifiers corresponding to the found qualified Bluetooth products in a queue to be tested in a certain order, so as to test the Bluetooth products corresponding to the product identifiers stored in the queue to be tested in turn.

[0054] Among them, the queue of products to be tested is used to store product identifiers that can distinguish each Bluetooth product that meets the conditions. Since the product identifiers stored in the queue of products to be tested can distinguish each Bluetooth product that meets the conditions, when testing is performed based on the product identifiers in the queue of products to be tested, the Bluetooth product to be tested can be identified based on the product identifiers in the queue of products to be tested. Moreover, the product identifiers are stored in the queue of products to be tested in an orderly manner. Each sequence number in the queue of products to be tested corresponds to only one product identifier. The queue of products to be tested can be used to sort the test order of the products to be tested, so that when testing is performed based on the queue of products to be tested, the Bluetooth product corresponding to each product identifier can be tested in an orderly manner.

[0055] It can be understood that the product identifier stored in the product queue to be tested in the embodiment of the present application can be a broadcast identifier, a Bluetooth name, a MAC address, or other identifiers that can be used to distinguish Bluetooth products.

[0056] It is understandable that the product identifications corresponding to the found Bluetooth products can be stored in a certain order in the queue of products to be tested: the product identifications corresponding to the found qualified Bluetooth products are stored in the queue of products to be tested in the order of signal strength from strong to weak; the product identifications corresponding to the found Bluetooth products are stored in a certain order in the queue of products to be tested. The storage order can also be other orders, such as the order of the found Bluetooth products, the product identifications of the Bluetooth products are stored in the order of A to Z, a to z, 9-0 according to the last digit, etc., which are not listed here one by one, and are all within the scope of protection of this application. The embodiment of the present application preferably stores the product identifications in the queue of products to be tested in the order of the signal strength of the Bluetooth products from strong to weak, so that a general test from near to far can be achieved.

[0057] Step S202 is: sequentially establishing connections with target Bluetooth products corresponding to product identifiers in the queue of products to be tested, and sequentially executing at least one test item, and for each test item to be executed, sequentially executing multiple test nodes included in the test item.

[0058] In an embodiment of the present application, after the product identifications corresponding to the found Bluetooth products are stored in a certain order in the product queue to be tested, since the product identifications stored in the product queue to be tested can distinguish each Bluetooth product, the terminal device can identify the Bluetooth product corresponding to each product identification based on the product identification. The terminal device can establish connections with the target Bluetooth products corresponding to the product identifications in the product queue to be tested in turn according to the product queue to perform testing.

[0059] After the terminal device establishes connection with the target Bluetooth product corresponding to the product identifier in the product queue to be tested, it will execute at least one test item in sequence according to at least one test item configured in the configuration file, and for each test item executed, it will execute multiple test nodes contained in the test item in sequence.

[0060] Generally speaking, the test items written into the configuration file will be executed sequentially. However, special cases are not excluded. For example, it is specified in the configuration file or the execution program, or through other means, that a test item written into the configuration file does not need to be executed. In this case, only some but not all test items can be executed. These are all included in the scope of "executing the at least one test item sequentially".

[0061] Among them, the terminal device establishes connections with the target Bluetooth products corresponding to the product identifiers in the product queue to be tested in turn, and executes at least one test item in turn, and for each test item executed, executes multiple test nodes contained in the test item in turn, specifically starting from the target Bluetooth product corresponding to the product identifier with a sequence number of 1, and completing the tests of the target Bluetooth products corresponding to the product identifiers in the product queue to be tested in turn.

[0062] The traversal method in which the terminal device sequentially establishes connection with the target Bluetooth products corresponding to the product identifiers in the product queue to be tested and tests them can be that after completing the test of the target Bluetooth product corresponding to the product identifier in the product queue to be tested, the product identifier is removed from the product queue to be tested, and the sequence numbers of the remaining product identifiers in the queue to be processed are all moved forward by one position, and the Bluetooth products corresponding to the product identifiers stored in the queue to be processed are tested sequentially until all the Bluetooth products corresponding to the product identifiers in the queue to be processed are tested. It is understandable that the product identifiers in the product queue to be tested may not be removed, and after completing the test of each target Bluetooth product corresponding to a product identifier, the sequence number may be increased by 1 until all the product identifiers in the product queue to be tested are sequentially traversed. Other methods that can sequentially traverse the product identifiers in the product queue to be tested may also be used, which are not listed here one by one.

[0063] In the Bluetooth product testing method provided in the present application, the product condition information for defining the standard of the product to be tested is configured in the configuration file to define the condition of a product as the product to be tested, and multiple qualified products to be tested can be screened out based on a configuration file for testing. That is to say, through the product condition information in the configuration file, multiple Bluetooth products can be screened in a range to achieve batch testing. Moreover, for the products to be tested that need to be tested, the same test items between the products to be tested are obtained, and the test of the products to be tested is abstracted into test items and each test node in the test items. In this way, by configuring a configuration file, multiple test items of at least one product to be tested can be automatically tested, which reduces the number of configuration files that need to be configured when testing multiple products to be tested, simplifies the test process, and is conducive to improving the testing efficiency of Bluetooth products.

[0064] Furthermore, the Bluetooth product testing method of the present application will store the product identifiers corresponding to the qualified Bluetooth products found according to the condition information of the product to be tested in a certain order into the queue of products to be tested. During the testing process, the Bluetooth products corresponding to the product identifiers in the queue of products to be tested will be tested in turn. Importing the configuration file can automatically test batches of Bluetooth products that meet the conditions specified in the configuration file, further improving the testing efficiency of Bluetooth products; moreover, the Bluetooth products that meet the conditions specified in the configuration file will be screened in advance, and only one screening process is required, which is conducive to reducing the occupancy of terminal device resources, further accelerating testing efficiency and simplifying the testing process.

[0065] Moreover, the Bluetooth product testing method of the present application is applied on a terminal device, which is portable. When a region or production line needs to be tested, the terminal device that is not being tested temporarily can be moved to a different region or production line for testing. This is beneficial to improving the flexibility of the use of test equipment when testing Bluetooth products, reducing the number of test equipment required for Bluetooth product testing, and reducing testing costs.

[0066] In summary, the Bluetooth product testing method provided in this application is conducive to improving testing efficiency, simplifying testing procedures, reducing terminal device resource usage, and reducing testing costs.

[0067] See also Figure 4 , attached Figure 4 Schematic diagram of the configuration file 40 in the embodiment of the present application. Figure 4 As shown, in the embodiment of the present application, in addition to the product condition information and test items, the configuration file may also include result description data to further indicate the display method of the test results of the product to be tested after executing one or more test items. Specifically, the configuration file 40 includes product configuration information 401, test items 4021 and 4022, and result description data 403.

[0068] The product configuration information 401 includes the condition information of the product to be tested and the description of the scan result. The condition information of the product to be tested is used to define whether the product is a standard of the product to be tested. The description of the scan result is used to characterize the search result after the product to be tested is scanned according to the condition information of the product to be tested.

[0069] The test items 4021 and 4022 are used to define the test items of the product to be tested. Each of the test items 4021 and 4022 may include multiple test nodes; each test node is a respective execution node of the test flow of each test item.

[0070] The result description data 403 is used to indicate the display method of the test result after the product to be tested executes one or more test items.

[0071] It is understandable that the configuration file may also include only product configuration information and at least one test item, but not result description data, that is, the test result is not displayed. The configuration file may also include other information related to the product test.

[0072] In the configuration file, the product configuration information has an association relationship with at least one test item. Preferably, the product configuration information and at least one test item can be associated through a preset association identifier (see association identifiers such as K01 and K02 in the subsequent embodiments of this application). Of course, the association relationship can also be established through other association methods, which are not limited here. Among them, when the product configuration information only includes the condition information of the product to be tested, the condition information of the product to be tested can also be directly associated with at least one test item in the configuration file.

[0073] Furthermore, when the configuration file includes other configuration information, it is also necessary to establish associations between the other configuration information and the corresponding product configuration information and test items. That is, in the embodiment of the present application, the product configuration information is associated with both the test item 4021 and the test item 4022, and the result description data 403 is also associated with the product configuration information 401.

[0074] The condition information of the product to be tested may include the broadcast identification template of the product to be tested and the critical value of the received signal strength of the product to be tested. The broadcast identification template refers to the same part of the broadcast identification in each product to be tested. Only products whose broadcast identification conforms to the broadcast identification template will be identified as the product to be tested. The critical value of the received signal strength of the product to be tested defines the minimum signal strength value received from the product to be tested on the terminal device 20. Only products whose received signal strength indication (RSSI) received at the terminal device exceeds the critical value of the received signal strength of the product to be tested will be identified as the product to be tested. By setting the critical value of the received signal strength of the product to be tested, products on the same test bench can be tested together, while products on another test bench that is farther away can be put together for the next step of testing. The broadcast identification template and the critical value of the received signal strength of the product to be tested together define all the conditions for a product to be a product to be tested, and thus constitute the condition information of the product to be tested.

[0075] It can be understood that the conditional information of the product to be tested can also include other forms of data, as long as it helps to identify which products are the products to be tested. For example, the conditional information of the product to be tested can be the Bluetooth name template of the product to be tested and the critical value of the received signal strength of the product to be tested. The Bluetooth name template refers to the same part of the Bluetooth name in each product to be tested. Only products whose Bluetooth names conform to the Bluetooth name template will be identified as products to be tested. The conditional information of the product to be tested can also be only a broadcast identification template without the critical value of the received signal strength of the product to be tested. That is to say, no matter how much the RSSI received at the terminal device is, as long as the broadcast identification of the product conforms to the broadcast identification template, it is identified as a product to be tested. The conditional information of the product to be tested can also be only a Bluetooth name template. As long as the Bluetooth name of the Bluetooth product conforms to the Bluetooth name template, it is identified as a product to be tested. The conditional information of the product to be tested can also include other identification information sufficient to identify a specific product.

[0076] When there are many products to be tested, the broadcast identification template and the critical value of the received signal strength of the product to be tested are combined to form the conditional information of the product to be tested, or the Bluetooth name template and the critical value of the received signal strength of the product to be tested are combined to form the conditional information of the product to be tested, or only the broadcast identification template is used as the conditional information of the product to be tested, or only the Bluetooth name template is used as the conditional information of the product to be tested, or other identifications that can distinguish the signals of the products to be tested within a certain range are used to configure the conditional information of the products to be tested. This can simplify the configuration process of the configuration file and reduce the difficulty of configuration of the configuration file.

[0077] It should be noted that the attached Figure 4The product condition information includes the broadcast identification template of the product to be tested and the critical value of the received signal strength of the product to be tested, which is an example of the case where the terminal device and the product to be tested are tested through Bluetooth communication. It can be understood that the product condition information can also include the Bluetooth name template of the product to be tested and the critical value of the received signal strength of the product to be tested, or other information. For the sake of ease of explanation and understanding, an example is used here, and the scope of protection is not limited.

[0078] The scan result description is used to characterize the search results after the terminal device completes scanning the product to be tested according to the product condition information to be tested. For example, the scan result description is used to display the number of scanned products on the display screen of the terminal device. It is understandable that the scan result description can also display other content on the terminal device, such as configuring a specific scan number in the scan result description, and after the scan is completed, the terminal device displays the scanned number and the unscanned number. The scan result description can also characterize the scan search results of the product condition information to be tested in other ways, such as characterizing the search results by means of a prompt sound, a light, etc.

[0079] It is understandable that the product configuration information may also only include the condition information of the product to be tested without the description of the scanning result, that is, the product configuration information can be used to identify whether the product is the product to be tested, and the specific scanning and searching results may not be displayed visually.

[0080] Each of the test items includes the test parameters corresponding to the test item. The test parameters may include an operation identifier, which is used to uniquely identify and distinguish the specific operation sent by the terminal device to perform the test, so as to ensure that the product under test can correctly understand and execute the corresponding action. For example, when the terminal device requires the application program in the product under test to execute the action of reading the power, the test instruction sent by the terminal device to the product under test must carry the operation identifier corresponding to the circuit reading action, so that the product under test can understand and execute the action of reading the power through the operation identifier.

[0081] In Bluetooth communication, the operation identifier can be, for example, a service identifier and a channel identifier. The channel identifier is a characteristic identifier used to distinguish each execution action under each service in Bluetooth communication. In a Bluetooth product, one service corresponds to one service identifier, and one service has multiple channel identifiers. Specifically, when a terminal device interacts with a Bluetooth product to allow the Bluetooth product to perform an action, the Bluetooth product will first find the corresponding service in the multiple services it can provide based on the service identifier sent by the terminal device, and then find the execution action corresponding to the channel identifier in the characteristic identifiers of the multiple execution actions under the service based on the channel identifier. In this way, in Bluetooth communication, the terminal device sends the service identifier and the channel identifier to the Bluetooth product together, and the Bluetooth product can uniquely identify and distinguish the terminal device's request to perform a specific operation based on the service identifier and the channel identifier. Finally, read and write data or monitor data based on the sent data.

[0082] Specifically, in Bluetooth communication, each Bluetooth product has a service UUID (i.e., service identifier). The service UUID is a unique identifier used to identify and distinguish different Bluetooth services in each Bluetooth product, that is, each Bluetooth product provides different services and has different service UUIDs. For example, the massager 101 provides massage services, and its service UUID is 46d99019-ab53-450f-98ea-f03d7025feee. The massager 101 provides LED lighting service UUID: 27861a72-4ec1-4e93-b6d9-36312a54ee00; the connected device needs to be able to accurately find and interact with the service. For example, when the terminal device 20 or the application in the massager 101 needs to control the indicator light of the massager 101, this function can be achieved by searching for the service with 27861a72-4ec1-4e93-b6d9-36312a54ee00 through the service UUID.

[0083] The technical personnel of this application have found that the service UUID corresponding to the same service in different Bluetooth products can be the same or different, and can be set by the manufacturer. However, under normal circumstances, the service UUID settings corresponding to the same service in different Bluetooth products are generally different; but in the case of Bluetooth products of the same type and different series manufactured by the same manufacturer, the manufacturer may also set the service UUID corresponding to the same service in the same type and different series of Bluetooth products to be the same, so that the differences between the communication between different series of Bluetooth products and the terminal on the same service can be ignored, and they can be treated as the same product for testing in the test, which can reduce the configuration work of the test file.

[0084] Furthermore, each service may also have a corresponding channel identifier. The channel identifier indicates the specific operation to be performed by a specific product under a specific service. The test of a specific function of a Bluetooth product is actually a combination of multiple specific operations included in the implementation of the function, and these combinations are represented by the channel identifier and the data being operated. It can be understood that during the test, when the product under test executes a certain test item, it first finds the specific service according to the service UUID, and then according to the channel identifier, it can find the executable action corresponding to the channel identifier in the product under test, so as to cooperate with the data sent by the terminal device to perform the corresponding action.

[0085] Typical channel identifiers are read-write feature identifiers (i.e., read-write feature UUIDs) and notification feature identifiers (i.e., notification feature UUIDs). In Bluetooth communication, specific actions need to be performed based on read-write feature UUIDs or notification feature UUIDs to read and write data to Bluetooth products or receive data sent by Bluetooth products. For example, when the massager 101 provides a service to light up the indicator light, the service has multiple feature identifiers for read-write purposes or notification purposes. Assuming that the read-write feature UUIDs for the two actions of setting the mode and starting the function are "6767d70b-4a11-4eaa-afd6-94cd573bee01", the specific operations that the massager 101 can perform under the service to light up the indicator light are: setting the mode for lighting up the indicator light and starting to light up the indicator light. Specifically, after the massager 101 finds a specific service (i.e., the indicator light service) based on the service UUID corresponding to the indicator light service, it then searches for the corresponding feature in multiple channel identifiers under the indicator light service based on the read-write feature UUID, and then determines the specific operation to be performed in conjunction with the data sent by the terminal device.

[0086] The read-write feature UUID (i.e., read-write feature identifier) ​​is a unique identifier in each massager that allows the terminal device 20 to read and write data. For example, when the massager 101 provides LED lighting services, the read-write feature UUID for controlling the on / off state of the LED light is 6767d70b-4a11-4eaa-afd6-94cd573bee01, which is used to write corresponding data to control the on / off state of the LED light on the massager 101. When the terminal device 20 is connected to the massager 101, the state of the LED light in the massager 101 can be changed based on the read-write feature UUID.

[0087] The notification feature UUID (i.e., notification feature identifier) ​​is a unique identifier of the massager that allows the terminal device 20 to receive real-time update information sent by the massager. For example, when the massager 101 provides LED lighting services, the notification feature UUID of the LED status update information is 6767d70b-4a11-4eaa-afd6-94cd573baa02. When the terminal device 20 is connected to the massager 101, it can subscribe to the LED status update information in the massager 101 based on the notification feature UUID, that is, based on the notification feature UUID, the massager 101 is required to send the updated status information to the terminal device 20 when the LED status is updated.

[0088] It should be noted that the read-write feature UUID and notification feature UUID do not refer to a specific UUID. There can be multiple channel identifiers under a service, and each channel identifier is identified by a UUID. The channel identifier has an attribute flag that can identify whether it is used for read-write operations or notification operations. The read-write feature identifier (read-write feature UUID) in this application is used to refer to a UUID used for read-write operations under a service, such as a UUID that only supports read operations, a UUID that only supports write operations, a UUID for write operations that do not require responses, a UUID that supports write operations with signatures, etc. The notification feature identifier (notification feature UUID) is used to refer to a UUID used for notification operations under a service, such as a UUID for notification operations that do not require terminal device confirmation, a UUID for notification operations that require terminal device confirmation, a UUID that supports broadcast operations, etc.

[0089] Among them, the service UUID, read-write feature UUID, and notification feature UUID of each Bluetooth product can be set during the product development stage. The service UUID, read-write feature UUID, and notification feature UUID of each Bluetooth product can use the UUID provided by the Bluetooth Technology Alliance, or a manufacturer-defined UUID; generally, it is customized by the manufacturer. The service UUID, read-write feature UUID, and notification feature UUID of existing Bluetooth products can be obtained in a variety of ways, such as asking the original product development engineer, using Bluetooth test tools, and obtaining through Bluetooth broadcast data packets.

[0090] The embodiment of the present application is aimed at the testing phase, and the service UUID, read-write feature UUID and notification feature UUID can be directly provided by the original product development engineer.

[0091] Furthermore, in the embodiment of the present application, the test parameters of the terminal device 20 and the massager to be tested 101 include a service identifier (service UUID) and a channel identifier, and the channel identifier is one of a read-write feature identifier (read-write feature UUID) and a notification feature identifier (notification feature UUID); it can be understood that the test parameters may also include other information related to the test items, such as sending data, receiving data, timeout period, etc.

[0092] That is to say, in the configuration file, the product configuration information is associated with a plurality of test items, and for the products to be tested defined in the product configuration information, the operation identifiers of the various test items that they need to test are the same.

[0093] It should be noted that, for each test item, the service identifier (i.e., service UUID) of each test node in the test item can be the same or different; for the same service UUID, the read-write feature UUIDs corresponding to different execution actions may be the same or different, and the notification feature UUIDs corresponding to different execution actions may be the same or different. In other words, under normal circumstances, if the service UUID of each test node in a test item is different, the corresponding read-write feature UUID and notification feature UUID will generally be different, but it is not ruled out that some manufacturers set the read-write feature UUID or notification UUID under some different services to be the same during the development stage; if the service UUID of each test node in a test item is the same, the read-write feature UUIDs corresponding to different test nodes may be the same or different, and the notification feature UUIDs corresponding to different test nodes may be the same or different. For ease of explanation, please refer to Table 1 below: Table 1 Test Node Name Service UUID Read and write characteristic UUID Notification characteristic UUID Sending Data Test Node 1 54e5314f-d7cb-4152-ab66-97ddddc1c450 b8d636e8-b891-4532-a6b2-29d091442052 600ba780-717f-42d4-8c2c-44462ee540f0 Aaa1 Test Node 2 c72a7c21-3aef-4594-b869-410d9e1370b4 1071d612-4368-4dc0-a824-4ad12803e97e 6767d70b-4a11-4eaa-afd6-94cd573baa02 52a Test Node 3 c72a7c21-3aef-4594-b869-410d9e1370b4 6767d70b-4a11-4eaa-afd6-94cd573bee01 6767d70b-4a11-4eaa-afd6-94cd573baa02 56c The test items in Table 1 include test node 1, test node 2 and test node 3. When the terminal device tests a product under test based on the configuration file, it will execute test node 1, test node 2 and test node 3 in the test item in sequence; wherein, the service UUID of test node 1 of the product under test in the test item is different from the service UUID of test node 2 and test node 3. When the service UUID is different, the read-write feature UUID and notification feature UUID of test node 1, test node 2 and test node 3 must be different. The service UUID in test node 2 and test node 3 is the same, and there are multiple channel identifiers in the service UUID. For different test nodes, the channel identifiers may be the same or different. For example, the read-write feature UUID in test node 2 is different from the read-write feature UUID in test node 3, and the notification feature UUID in test node 2 is the same as the notification feature UUID in test node 3.

[0094] However, for the products to be tested defined by the product condition information, the service UUID, read-write feature UUID and notification feature UUID of each test node of each product to be tested under the test item are the same. That is to say, assuming that the product condition information defines 5 products to be tested, for test node 1, these 5 products to be tested have the same service UUID, read-write feature UUID and notification feature UUID; for test node 2, these 5 products to be tested have the same service UUID, read-write feature UUID and notification feature UUID; for test node 3, these 5 products to be tested have the same service UUID, read-write feature UUID and notification feature UUID.

[0095] In the embodiment of the present application, the test parameters of each test node may include a test node name, a service UUID, a read-write feature UUID, a notification feature UUID, sent data, and received data. The node name is the name of each execution node corresponding to the test process of each test item; the sent data is the data sent by the terminal device to the product under test under the test node, and the product under test is driven to execute the action corresponding to the test node based on the sent data; the received data is the data that the product under test should return to the terminal device after executing the action corresponding to the test node, and the received data can also be used to determine whether the device under test has successfully executed the test node. If the received data returned by the product under test is the same as the received data configured for the test node, it means that the test node is executed successfully. It should be noted that the product under test does not generate and return data when executing each action corresponding to the test node.

[0096] It is understandable that the test parameters of each test node of the test item may also include a timeout time, which is the longest timeout time of the test node, that is, the longest execution time of the test node. The timeout time can be used to define the test result. For example, when the execution time of the test node is greater than the timeout time in the configuration file, the test fails. The timeout time can also be used to define the sending time of the corresponding test instruction of the next test node. For example, when the timeout time is reached and the product to be tested does not return the corresponding received data, the test instruction is generated according to the test parameters of the next test node and sent to the product to be tested. The test parameters of each test node of the test item may also include a verification description of successful execution. The verification description of successful execution is a visual representation method after the successful execution of the test item. For example, if the test item is to light up the indicator light, the verification description of successful execution can be to light up the indicator light. If the test item starts the spray function, the verification description of successful execution can be product spray. This is just an example, which can be configured by a technician according to the actual situation. The test parameters of each test node of the test item may also include other parameter information related to the test item.

[0097] The test entry includes multiple test nodes, where each test node in the test entry corresponds to each execution node of the test process of each test entry. Under each test node, the terminal device will generate a corresponding test instruction and send it to the corresponding product under test, so that the product under test executes each action based on the test instruction.

[0098] During the testing process, the technical staff of this application discovered that, under normal circumstances, the channel identifiers of different execution actions under a service are different; but some products have special configurations, and the channel identifiers of different execution actions under a service may be the same. In these cases, the service identifier, channel identifier and sending data are required to identify the executed action. In other words, under normal circumstances, each test node in the test entry can be distinguished based on the service identifier and channel identifier to allow the product under test to identify the action to be performed.

[0099] In some cases, each test node in the test entry needs to be distinguished based on the service identifier, channel identifier, and sent data so that the product under test can identify the action to be performed. Specifically, the terminal device will generate a test instruction based on the service UUID, read-write feature UUID, notification feature UUID, and sent data. The product under test will find one or more corresponding execution actions based on the service UUID, read-write UUID, and notification feature UUID in the test instruction, and further identify the specific execution action from one or more corresponding execution actions based on the sent data in the test instruction, and execute it according to the sent data.

[0100] For example, when the test node of test item 4021 is configured to establish a secure link, read the device code, read the status, set the mode, start the function, and read the status, the terminal device will generate test instructions according to each test node of test item 4021 and send them to the corresponding product under test. Specifically, the terminal device will first generate a test instruction according to the service UUID, read-write feature UUID, notification feature UUID, and send data of the test node "Establish a secure link" and send it to the corresponding product under test. After receiving the data returned by the product under test after performing an action according to the test instruction of the test node, or after a preset time, the terminal device will generate a test instruction according to the test node "Read device code" and send it to the corresponding product under test. After receiving the data returned by the product under test, or after a preset time, the terminal device will generate a test instruction according to the test node "Read status" in test item 4021 and send it to the corresponding product under test, until all the test nodes in test item 4021 are traversed in turn.

[0101] The test nodes of each test item are specifically configured by the technician according to the test flow required by each different test item. The name and number of the test nodes can be set according to the requirements, and the corresponding test nodes in different test items can be different or the same, which is specifically configured by the technician. For example, the test nodes of test item 4021 and test item 4022 are both configured to establish a secure link, read a device code, read a status, set a mode, start a function, and read a status, that is, the same test nodes are configured for different test items.

[0102] It should be noted that the attached examples in this application Figure 4 The configuration file 40 shown includes 2 test items. It can be understood that the configuration file may include 1 test item, 3 test items, 10 test items, 50 test items, or other larger number of test items.

[0103] Further, the result description data 403 in the configuration file is used to indicate the display method of the test result of the product to be tested after executing one or more test items. The result description data 403 includes: the test result description method and the test result description period. The test result description method includes the object that executes the test result description, the corresponding display module configuration information, and the indication content; wherein, the object that executes the test result description is the object that displays the test result, which can be a terminal device or a target Bluetooth product; the display module configuration information of the object of the test result description is the display module that the object of the test result description has and can be used to display the indication signal, such as LED lights, LED screens, LCD screens, OLED screens, etc.; and the relevant configuration information of the display module, such as screen model, driver IC, signal interface, voltage, etc.; the indication content is the representation method of the test result, such as indicating the conclusion of success or failure of the test result by flashing lights or lighting up LED lights on the corresponding product to be tested. The test result description period is used to define the time for the indication signal to be displayed, including displaying the result after each of the at least one test item corresponding to the target Bluetooth product is completed, and / or displaying the result after all the test items corresponding to the target Bluetooth product are tested.

[0104] The result description data is explained below by taking massagers 101, 102, 103, 104 and 105 in the aforementioned embodiments as examples. For example, the result description data indicates that the test results of the product to be tested after executing all test items are displayed in the following manner: the final test result is displayed on the terminal device as a conclusion of test success or test failure. Specifically, for example, when the massager 101 successfully lights up the indicator light test and fails to start the massage function test, after the massager 101 completes lighting the indicator light and starting the massage function test, the terminal device 20 displays "massager 101 test failed".

[0105] It is understandable that the result description data indicating the test results of the product to be tested in response to the execution of all test items can also be displayed on the corresponding product to be tested, such as by flashing lights or lighting up LED lights on the corresponding product to be tested to indicate the conclusion of success or failure of the test result.

[0106] It can be understood that the result description data can also be configured to indicate that after all the corresponding test items of each product to be tested are executed, the terminal device displays the conclusion of "test success" or "test failure" for each test item executed by each product to be tested. Specifically, the result description method is illustrated by taking the massager 101 as an example of a successful test of lighting the indicator light and a failed test of starting the massage function: since the result description data indicates that the display method of the test results of the product to be tested after executing two test items is: after each product to be tested has executed all the test items, the terminal device 20 displays the conclusion of a successful test or a failed test for each test item executed by the product to be tested. At this time, according to the configuration of the result description data in the configuration file, the terminal device 20 will display the conclusion of a successful test of lighting the indicator light and a failed test of starting the massage function on the display screen of the terminal device 20 based on the feedback data received after the massager 101 completes the test of lighting the indicator light according to the test instruction and the feedback data after the massager 101 completes the test of starting the massage function according to the test instruction.

[0107] It can be understood that the result description data can also be configured to indicate that each product to be tested is displayed after each test item is executed accordingly, such as after the massager 101 executes the test item of lighting the indicator light, it displays the conclusion that the test of the massager 101 lighting the indicator light is a success or a failure, and then after the test item of starting the massage function is executed, it displays the conclusion that the test of the massager 101 starting the massage function is a success or a failure. The result description data can also be configured to indicate that after all products to be tested have completed the test of all test items, the final test results of all products to be tested are displayed together, that is, after all products to be tested have completed all test items, only the final test results are displayed. Specifically, after the massagers 101, 102, 103, 104, and 105 have completed the test, the final test results of each product to be tested after executing all test items are all displayed together on the terminal device 20. Specifically, the product information (such as Bluetooth name, broadcast identifier, etc.) corresponding to the products to be tested that have succeeded and failed in the test can be displayed simultaneously through a list.

[0108] Specifically, the specific method for generating an indication signal according to the result description data includes: receiving feedback data returned by the target Bluetooth product, generating a description indication signal according to the feedback data and the test result description period; the description indication signal includes a first indication signal representing the test result corresponding to each test item executed by the target Bluetooth product, and / or a second indication signal representing the test result corresponding to the target Bluetooth product after the configuration file is executed in sequence in the at least one test item; when the object of the test result description in the result description data is a terminal device, generating a display signal according to the test result description method and the description indication signal, so that the display module of the terminal device displays the corresponding information according to the display signal. When the object of the test result description in the result description data is a target Bluetooth product, generating a display module control signal according to the test result description method and the description indication signal and sending it to the target Bluetooth product, so that the target Bluetooth product controls the display module to display the corresponding information according to the display module control signal.

[0109] Furthermore, the test results can also be displayed on the terminal device and the target Bluetooth product at the same time. At this time, a display signal is generated according to the test result description method and the description indication signal, so that the display module of the terminal device displays the corresponding information according to the display signal. At the same time, a display module control signal is generated according to the test result description method and the description indication signal, and sent to the target Bluetooth product, so that the target Bluetooth product controls the display module to display the corresponding information according to the display module control signal.

[0110] It is understandable that the configuration file may not include result description data; that is, the test results are not displayed after the test of the product to be tested is completed. Of course, it is preferred to provide result description data, which is conducive to a more intuitive display of the test results of the Bluetooth product and improves the test efficiency.

[0111] The following uses the massagers 101, 102, 103, 104 and 105 in the aforementioned embodiments as examples to specifically illustrate the configuration of the configuration file and the solution for testing the Bluetooth product based on the configuration file.

[0112] It should be noted that in this example description, the configuration file includes product configuration information, two test items, and result description data. This is only a specific example and does not limit the scope of this application.

[0113] First, the product configuration information in the configuration file is configured; the product configuration information includes the condition information of the product to be tested and the description of the scanning result.

[0114] In this embodiment of the present application, the condition information of the product to be tested includes a broadcast identification template and an RSSI critical value. The specific configuration of the condition information of the product to be tested is as follows: obtain the same part of the broadcast identification in massagers 101, 102, 103, 104, and 105, that is, 04500042; and determine the minimum received signal strength critical value from the product to be tested received on the terminal device 20 according to the RSSI values ​​of massagers 101, 102, 103, 104, and 105, which is -70. In this way, the broadcast identification template of the product to be tested in the condition information of the product to be tested is 04500042 and the received signal strength critical value of the product to be tested is -70, and the configuration of the condition information of the product to be tested is completed.

[0115] Further, the description of the scanning result is configured to display "X products have been scanned" on the terminal device 20, where X is the number of products scanned on the terminal device.

[0116] To facilitate understanding of the product configuration information, the product configuration information in the configuration file is displayed in a tabular form in the embodiment of the present application. The specific product configuration information is shown in Table 2 below.

[0117] Table 2

[0118] The configuration file includes two test items, which are lighting the indicator light and starting the massage function. The test parameters of each test item include the test node name, service identifier, read and write feature identifier, notification feature identifier, sending data and receiving data to illustrate the test item.

[0119] Configure each of the two test items in the configuration file. Specifically, obtain the service identifier (i.e., service UUID) for lighting the indicator light in massagers 101, 102, 103, 104, and 105, the read-write feature UUID (i.e., read-write feature identifier), the notification feature UUID (i.e., notification feature identifier), the sending data, and the receiving data; obtain the service UUID, read-write feature UUID, notification feature UUID, the sending data, and the receiving data for starting the massage function in massagers 101, 102, 103, 104, and 105; and based on the multiple test nodes preset in each test item, complete the configuration of the two test items in the configuration file.

[0120] In the embodiment of the present application, the service UUID, read-write feature UUID, and notification feature UUID for lighting the indicator lights in massagers 101, 102, 103, 104, and 105 are all the same; the service UUID, read-write feature UUID, and notification feature UUID for starting the massage function in massagers 101, 102, 103, 104, and 105 are all the same.

[0121] Furthermore, the multiple test nodes preset in each test entry are the execution nodes of the test process of each test entry; in the embodiment of the present application, the execution nodes of the test process of the test entry include establishing a secure link, reading a device code, reading a status, setting a mode, and starting a function as an example for explanation.

[0122] To facilitate understanding of the configuration information of the test items, the two test items of the configuration file are displayed in a table in the embodiment of the present application. Among them, the configuration information of the test item for lighting the indicator light is shown in Table 3 below: Table 3 Test Node Name Service UUID Read and write characteristic UUID Notification characteristic UUID Sending Data Receiving Data Establishing a secure link 27861a72-4ec1-4e93-b6d9-36312a54ee00 6767d70b-4a11-4eaa-afd6-94cd573bee01 6767d70b-4a11-4eaa-afd6-94cd573baa02 01 C0E2CA05 Read device code 27861a72-4ec1-4e93-b6d9-36312a54ee00 6767d70b-4a11-4eaa-afd6-94cd573bee01 6767d70b-4a11-4eaa-afd6-94cd573baa02 02 A30E00B2 Read Status 27861a72-4ec1-4e93-b6d9-36312a54ee00 6767d70b-4a11-4eaa-afd6-94cd573bee01 6767d70b-4a11-4eaa-afd6-94cd573baa02 03 01 Setting Mode 27861a72-4ec1-4e93-b6d9-36312a54ee00 6767d70b-4a11-4eaa-afd6-94cd573bee01 6767d70b-4a11-4eaa-afd6-94cd573baa02 0105140A C0E2CC01 Start function 27861a72-4ec1-4e93-b6d9-36312a54ee00 6767d70b-4a11-4eaa-afd6-94cd573bee01 6767d70b-4a11-4eaa-afd6-94cd573baa02 04 0EA2CCD3 The test items are configuration information for starting the massage function, as shown in Table 4: Table 4 Test Node Name Service UUID Read and write characteristic UUID Notification characteristic UUID Sending Data Receiving Data Establishing a secure link a8b17a9b-eaca-4cd2-ab1f-53f59e95d96f 17a06af2-7819-4c54-8c54-829af689e638 17a06af2-7819-4c54-8c54-829af689e741 01 C0E2CA05 Read device code a8b17a9b-eaca-4cd2-ab1f-53f59e95d96f 17a06af2-7819-4c54-8c54-829af689e638 17a06af2-7819-4c54-8c54-829af689e741 02 A30E00B2 Read Status a8b17a9b-eaca-4cd2-ab1f-53f59e95d96f 17a06af2-7819-4c54-8c54-829af689e638 17a06af2-7819-4c54-8c54-829af689e741 0105140B C0E2CC02 Setting Mode a8b17a9b-eaca-4cd2-ab1f-53f59e95d96f 17a06af2-7819-4c54-8c54-829af689e638 17a06af2-7819-4c54-8c54-829af689e741 06 0EEE89A3 Start function a8b17a9b-eaca-4cd2-ab1f-53f59e95d96f 17a06af2-7819-4c54-8c54-829af689e638 17a06af2-7819-4c54-8c54-829af689e741 04 02 Establish association relationships between the product configuration information in the configuration file and the test items of lighting the indicator light and starting the massage function, respectively. Specifically, the association identifier between the product configuration information and the test item of lighting the indicator light and the association identifier between the product configuration information and the test item of starting the massage function can be set to the same to achieve association, such as using the preset association identifier K01 as the common association identifier to achieve association.

[0123] The result description data 403 is configured to indicate the display method of the test results of the product to be tested after executing two test items in the configuration file: after each product to be tested executes at least one test item corresponding to the condition information of the product to be tested in turn, the corresponding conclusion of test success or test failure for each test item executed by the product to be tested is displayed on the terminal device 20. At this time, according to the configuration of the configuration file, the terminal device 20 will display the conclusion that the massager 101 successfully lit the indicator light test and failed the massage function start test on the display screen of the terminal device 20 based on the feedback data received after the massager 101 completed the test of lighting the indicator light according to the test instructions, and the feedback data after completing the test of starting the massage function according to the test instructions.

[0124] A configuration file is obtained based on the above product configuration information, 2 test items and result description data.

[0125] It should be noted that in the embodiment of the present application, the configuration file is described in the form of a table. Specifically, in actual applications, the configuration file can also be represented in various forms, such as a table file, or an independent data packet. Each independent file in the data packet corresponds to the configuration of the product condition information to be tested, each test item, and result description data, etc. Optionally, the configuration file can also be directly edited as an XML file. The specific form of the configuration file is not limited here, and can be set according to personnel in this field.

[0126] The configuration file is imported into the application corresponding to the terminal device 20. The terminal device 20 scans the Bluetooth broadcast signal based on the condition information of the product to be tested in the configuration file. At this time, since various Bluetooth products will continuously broadcast signals to the outside after being started, all Bluetooth products within a certain range around the terminal device 20 can be scanned. Based on the condition information of the product to be tested in the configuration file, a Bluetooth product corresponding to the broadcast identification template 04500042 and the received signal strength greater than the received signal strength critical value -70 can be searched among the scanned multiple Bluetooth products, and the product identification corresponding to the found qualified Bluetooth product (here taking the broadcast identification as an example) is stored in the queue of products to be tested in a certain order (here taking the order of signal strength from strong to weak as an example).

[0127] At this time, the storage order in the queue of products to be tested is as shown in Table 5 (an example of the queue of products to be tested): Table 5

[0128] Then, the terminal device 20 establishes a connection with the target Bluetooth product corresponding to the product identifier in the product queue to be tested in turn, and executes two test items in turn, and for each of the two test items, executes multiple test nodes contained in the test item in turn. Specifically, based on Table 5, the terminal device 20 first establishes a connection with the target Bluetooth product (i.e., massager 101) corresponding to the broadcast identifier with a sequence number of 1 in the product queue to be tested in the order of the broadcast identifiers stored in the product queue to be tested, first generates corresponding test instructions according to each test node of lighting the indicator light in turn, and sends the test instructions to the massager 101, the massager 101 performs the corresponding operation according to the test instructions, and after the massager 101 completes the indicator light lighting test according to the test instructions, it sends the test result information to the terminal device 20, wherein the test result information can be the data information preset by the developer when developing the product to complete the execution of the function / service, and the test result information can also be other data information preset for feedback indicating the success of the test in the test phase, such as when the massager 101 lights up the indicator light test successfully, it can be the "received data" corresponding to each test node in Table 3 above.

[0129] Then, the corresponding test instructions are generated according to each test node of the massage function, and the test instructions are sent to the massager 101, and the massager 101 performs the corresponding operation according to the test instructions. After the massager 101 completes the test of the massage function according to the test instructions, it sends the test result information to the terminal device 20.

[0130] The terminal device loops through the test action of massager 101 to test the Bluetooth products corresponding to the broadcast identifiers stored in the waiting queue in turn, until all the Bluetooth products corresponding to the broadcast identifiers in the waiting queue are tested. That is, the above test process is performed on massager 102, massager 103, massager 104, and massager 105 in turn until all the tests are completed.

[0131] Furthermore, after the target Bluetooth product completes the test corresponding to each test item according to the test instruction, it can further send feedback data to the terminal device, and the terminal device can further generate a test document corresponding to the test item by receiving the feedback data of the target Bluetooth product. Among them, the feedback data sent by the target Bluetooth product after completing the test of each test item may include: test result information and all data messages generated by the entire test link; the test result information can be the data information preset by the developer when developing the product after the execution of the function / service, such as when the test item corresponding to Table 3 is successfully tested, it can be the "received data" corresponding to each test node in Table 3, and the test result information can also be other data information preset for feedback during the test phase to indicate the success of the test.

[0132] It should be noted that the timing of generating the test document can be configured in the configuration file. The target Bluetooth product will usually generate and send the corresponding feedback data after executing each test node in each test item. In the embodiment of the present application, the terminal device receives the feedback data of the target Bluetooth product to generate the test document corresponding to the test item, which can be generated immediately after receiving the feedback data of the target Bluetooth product, that is, after the target Bluetooth product completes each test node in a test item, the terminal device generates the test document corresponding to the test node of each test item of the target Bluetooth product based on the feedback data of each test node received. It can be understood that the terminal device can also store the feedback data of the target Bluetooth product after receiving it, and then generate the test document corresponding to the test item after the target Bluetooth product has completely executed a test item. The terminal device can also store the feedback data of the target Bluetooth product after receiving it, and the terminal device generates the test document again after the target Bluetooth product responds to executing all the test items in the configuration file.

[0133] It should be noted that the target Bluetooth product may not generate feedback data in some test nodes, or may not return feedback data when the test node test fails. In this case, the test document can be generated based on the time when the target Bluetooth product executes the test node. It is understandable that in order to more accurately determine the test result of the target Bluetooth product, the test document can be further generated in combination with the time when the target Bluetooth product executes the test node and the feedback data of the target Bluetooth product.

[0134] It is understandable that the present application can also directly receive the feedback data generated by the target Bluetooth product after executing at least one test item, and directly determine the test result based on the test result information in the feedback data without generating a test document. Preferably, the test document of the target Bluetooth product is further generated based on the feedback data, so that the reasons for the failure of the Bluetooth product or the failed test nodes during the test process can be further analyzed according to the test document, and each test item and each test node in the test item can be traced back based on the test document, which is conducive to improving the reliability of Bluetooth product testing.

[0135] Still taking the products to be tested including: massager 101, massager 102, massager 103, massager 104, massager 105 as an example, the further generation of the configuration document is explained based on the test items in the configuration file configured as Table 3 and Table 4: the terminal device 20 first establishes a connection with the target Bluetooth product (i.e., massager 101) corresponding to the broadcast identifier with a sequence number of 1 in the queue of products to be tested in the order of the broadcast identifiers stored in the queue of products to be tested, first generates a corresponding test instruction according to the first test node "establishing a secure link" of the indicator light, and sends the test instruction to the massager 101, the massager 101 performs the corresponding operation according to the test instruction, and after testing the node according to the test instruction, the massager 101 sends feedback data to the terminal device 20, and the terminal device 20 receives the feedback data of the massager 101 and temporarily stores it; then, the corresponding test instructions are generated according to each test node of the indicator light in turn, and the test instructions are sent to the massager 101, the massager 101 performs the corresponding operation according to the test instruction. The test instruction executes the corresponding operation and returns the feedback data of executing the test node until each test node of the test item is completed, that is, the indicator light lighting test is completed. The terminal device 20 generates a test document corresponding to the massager 101 executing the indicator light lighting test according to the feedback data after the massager 101 executes each test node of the indicator light lighting test, thereby completing the test of the massager 101 lighting the indicator light, and then generates corresponding test instructions according to each test node of starting the massage function in turn, and sends the test instructions to the massager 101. The massager 101 executes the corresponding operation according to the test instruction and returns the feedback data of executing the test node. The terminal device 20 receives the feedback data of each test node of the massager 101 and stores it until the massager 101 completes the test of starting the massage function according to the test instructions of each test node in turn. The terminal device 20 generates a test document corresponding to the massager 101 executing the test of starting the massage function, thereby completing the test of the massager 101 starting the massage function.

[0136] Among them, the feedback data sent by the massager 101 after completing the test of each test item includes: test result information and all data messages generated by the entire test link; the test result information can be the "received data" corresponding to each test node in Table 3 and Table 4 when the test item is successfully tested.

[0137] The broadcast identifier corresponding to massager 101 is removed from the queue of products to be tested, and the order numbers of the remaining broadcast identifiers in the queue to be processed are all moved forward by one. The Bluetooth products corresponding to the broadcast identifiers stored in the queue to be processed are tested in turn, and a test document is generated until all the Bluetooth products corresponding to the broadcast identifiers in the queue to be processed are tested. That is, the above test process is performed on massagers 102, 103, 104, and 105 in turn, and a test document is generated until all the tests are completed.

[0138] It is understandable that in this example, the terminal device stores the feedback data received from each test node of the target Bluetooth product first, and then generates the test document corresponding to the test item after the target Bluetooth product completely executes a test item. Here, a specific solution is adopted to illustrate the generation of the test document for the convenience of understanding, and the timing of generating the test document is not limited.

[0139] See also Figure 5 , attached Figure 5 It is a schematic diagram of another configuration file provided in an embodiment of the present application. Another embodiment of the present application provides a schematic diagram of a configuration file including multiple groups of "product configuration information and at least one test item" relationships. In this embodiment, the configuration file 50 also includes the configuration file and the additional product condition information to be tested, and at least one additional test item corresponding to the additional product condition information to be tested, and the product corresponding to the product condition information to be tested and the product corresponding to the additional product condition information to be tested are tested in sequence, that is, the configuration file includes multiple groups of "product configuration information and at least one test item" relationships, and each group of "product configuration information and at least one test item" corresponding relationships can be associated by establishing a common association identifier. In a specific embodiment of the present application, the configuration file includes two groups of "product configuration information and at least one test item" relationships (hereinafter referred to as two groups of test categories), and both groups of test categories are associated with the same result description data 503.

[0140] That is, the first product configuration information 5011 is associated with the first test item 5021 and the second test item 5022 respectively through the association identifier, and the second product configuration information 5012 is associated with the third test item 5023 through the association identifier. The association identifier may be pre-set, such as the first product configuration information 5011 is associated with the first test item 5021 and the second test item 5022 respectively through the association identifier "K01", and the second product configuration information 5012 is associated with the third test item 5023 through the association identifier "K02". The first product configuration information 5011 and the second product configuration information 5012 can be associated with the result description data 503 by establishing an association identifier "Z01" of the result description. When it is necessary to execute the test result description action, the corresponding result description data can be obtained through the association identifier "Z01" for execution; the association identifiers "K01" and "K02" can also be associated with the result description data 503, that is, the same result description data 503 can be indexed through the association identifier "K01" and the association identifier "K02".

[0141] Furthermore, when the configuration file further includes additional product condition information to be tested and at least one additional test item corresponding to the additional product condition information to be tested, when the additional product to be tested is tested according to the configuration file, a Bluetooth product that meets the conditions may be searched according to the additional product condition information to be tested. When the Bluetooth products corresponding to the product identifications to be tested in the queue to be processed are all tested, the product identifications corresponding to the Bluetooth products found according to the additional product condition information to be tested are stored in the queue to be processed in a certain order, wherein the product identification to be tested is the product identification corresponding to the Bluetooth product that meets the conditions found according to the product condition information to be tested.

[0142] It can be understood that when additional products to be tested are tested according to the configuration file, when all Bluetooth products corresponding to the product identifiers to be tested in the queue to be processed are tested, the product identifiers corresponding to the Bluetooth products found according to the additional product condition information to be tested will be stored in the queue to be processed in a certain order. That is to say, when there are multiple groups of "product configuration information and at least one test item" relationships, a batch of products to be tested will be scanned first, that is, a group of products to be tested corresponding to the relationship between "product configuration information and at least one test item" will be scanned first, and after the queue to be processed is cleared, the next batch will be scanned.

[0143] It can be understood that when the configuration file also includes additional product condition information to be tested and at least one additional test item corresponding to the additional product condition information to be tested, the product identifiers corresponding to the Bluetooth products found according to the product condition information to be tested in the configuration file can be stored in a queue to be processed in a certain order, and the product identifiers corresponding to the Bluetooth products found according to the additional product condition information to be tested can be stored in a queue to be processed in a certain order, and then connections are established with the target Bluetooth products corresponding to the product identifiers in the queue to be tested in turn, and at least one test item is executed in turn, and for each test item to be executed, multiple test nodes contained in the test item are executed in turn, that is, the products to be tested defined by multiple product condition information to be tested in the configuration file are first scanned and added to the queue to be processed in turn, and then processed in turn in the order of the queue to be processed.

[0144] In this way, the same points of the operation identifiers of each product to be tested on the test items will be utilized to abstract the tests of different types of products or different series of products of the same type into test items, and the various test nodes in the test items, so that the product to be tested is corresponded to at least one test item. Therefore, by configuring a configuration file, multiple types of products or multiple series of products within a type can be tested in a batch, thereby realizing batch testing of multiple products to be tested that need to test different test items, which is conducive to further improving test efficiency and simplifying the test process.

[0145] It should be noted that in the embodiment of the present application, the same result description data is configured for all test category groups in the configuration file; it is understandable that different test category groups in the configuration file may also be configured with different result description data, and associated through corresponding association identifiers.

[0146] See also Figure 6 , attached Figure 6 Another embodiment of the present application provides a schematic diagram of a configuration file in which different result description data are configured for different correspondences between "product configuration information and at least one test item" in the configuration file.

[0147] Attached Figure 6 In the configuration file 60, the product configuration information 6011 and the product configuration information 6012 are respectively configured with different result description data. Specifically, the first product configuration information 6011 is respectively associated with the first test item 6021 and the second test item 6022, and the second product configuration information 6012 is associated with the third test item 6023; and the product configuration information 6011 is associated with the result description data 6031, and the product configuration information 6012 is associated with the result description data 6032, so that when displaying the test results, different test result display methods can be used, such as the product configuration information 6011 displays the test results on the terminal device, and the product configuration information 6012 displays the test results on the target Bluetooth product. It is also possible to configure the same result description data for some test category groups. In this case, it is necessary to set an association identifier for the result description data and the product condition information to be tested, so as to realize the association between the result description data in the configuration file and the corresponding multiple product condition information to be tested, and the association between the product condition information to be tested and at least one test item.

[0148] Furthermore, the embodiment of the present application can search for qualified Bluetooth products based on the new condition information of the products to be tested after all the Bluetooth products corresponding to the product identifiers in the queue of products to be tested have been tested, and store the product identifiers corresponding to the found Bluetooth products in a certain order in the queue of products to be tested. Specifically, when all the Bluetooth products corresponding to the product identifiers in the queue to be processed have been tested, the qualified Bluetooth products are searched based on the additional condition information of the products to be tested, and the product identifiers corresponding to the found Bluetooth products are stored in a certain order in the queue to be processed; wherein the product identifier to be tested is the product identifier corresponding to the qualified Bluetooth product found according to the condition information of the products to be tested.

[0149] The embodiment of the present application can also search for qualified Bluetooth products based on all the product condition information to be tested in the configuration file, and store the product identifications corresponding to all the found Bluetooth products in the product queue to be tested in turn according to the configuration order of each product condition information to be tested in the configuration file, and then find at least one test entry corresponding to the target Bluetooth product corresponding to the product identification currently to be tested based on the association identification of each group of product condition information to be tested and at least one test entry, so as to realize the testing of each product to be tested.

[0150] The above embodiments have already specifically introduced the relevant configuration information of the configuration file and the test method of the target Bluetooth product in the embodiments of the present application, and will not be repeated here.

[0151] As can be seen from the above, the configuration file in the embodiment of the present application can further include additional product condition information to be tested and at least one additional test item corresponding to the additional product condition information to be tested. For products to be tested that need to test different test items, the same test items between the products to be tested are obtained, and the commonalities of the products to be tested in the test items are used to correspond the products to be tested to at least one test item. The correspondence between multiple different products to be tested and at least one test item is configured in one configuration file. In this way, by configuring one configuration file, batch testing of multiple products to be tested that need to test different test items can be achieved, which is conducive to further improving testing efficiency and simplifying the testing process.

[0152] See also Figure 7 , attached Figure 7 The embodiment of the present application also provides a Bluetooth product testing device, which is applied to a terminal device. Specifically, the Bluetooth product testing device 70 includes an acquisition unit 701, a product determination unit 702, and a testing unit 703.

[0153] Among them, the acquisition unit 701 is used to obtain a configuration file, which includes condition information of the product to be tested and at least one test item, wherein the condition information of the product to be tested is used to define the standard for determining whether it is a product to be tested, and the at least one test item is used to define the test items of the product to be tested, and each of the at least one test item includes multiple test nodes.

[0154] The product determination unit 702 is used to search for Bluetooth products that meet the conditions according to the condition information of the product to be tested, and store the product identifiers corresponding to the found Bluetooth products in a queue of products to be tested in a certain order.

[0155] The test unit 703 is used to sequentially establish connections with target Bluetooth products corresponding to product identifiers in the product queue to be tested, and sequentially execute at least one test item, and for each test item executed, sequentially execute multiple test nodes included in the test item.

[0156] At least one test entry includes a test parameter, wherein the test parameter includes an operation identifier.

[0157] The operation identifier includes a service identifier and a channel identifier, and the channel identifier includes a read-write feature identifier or a notification feature identifier.

[0158] The condition information of the product to be tested includes the Bluetooth name template and the critical value of the received signal strength of the product to be tested; the Bluetooth name template of the product to be tested is the same part of the Bluetooth name of the product to be tested, and the critical value of the received signal strength is used to define the minimum signal strength value received from the product to be tested on the terminal device. Or, the condition information of the product to be tested includes the broadcast identification template and the critical value of the received signal strength of the product to be tested; the broadcast identification template of the product to be tested is the same part of the broadcast identification of the product to be tested.

[0159] The condition information of the product to be tested and the at least one test item are associated with each other.

[0160] Furthermore, the configuration file also includes additional product condition information to be tested and at least one additional test item corresponding to the additional product condition information to be tested, and the product corresponding to the product condition information to be tested and the product corresponding to the additional product condition information to be tested are tested in sequence.

[0161] Furthermore, the Bluetooth product testing device 70 also includes a receiving unit and a test document generating unit.

[0162] The receiving unit is used to receive feedback data generated by the target Bluetooth product in response to executing at least one test item, and the test document generating unit is used to generate a test document of the target Bluetooth product according to the feedback data.

[0163] The configuration file further includes result description data, and the result description data is used to indicate the display method of the test result of the product to be tested in response to executing one or more test results of at least one test item.

[0164] The Bluetooth product testing device 70 further includes an indication signal generating unit, which is used to generate an indication signal according to the result description data.

[0165] Since the technical personnel of this application found that the conditions that can be used to distinguish the products to be tested have some of the same features in the same category of products, based on this discovery, these partially identical features are extracted as conditions for distinguishing the products to be tested, and range distinction can be achieved in multiple types of Bluetooth products. In the Bluetooth product testing method provided in this application, the standard product condition information for defining the products to be tested in the configuration file defines the conditions for a product to be tested by utilizing the same features that can be extracted in the same category of products, and can screen out multiple qualified products to be tested based on a configuration file for testing to achieve batch testing. Moreover, for the products to be tested that need to be tested, the same test items between the products to be tested are obtained, and the test of the products to be tested is abstracted into test items and each test node in the test items. In this way, by configuring a configuration file, multiple test items of multiple products to be tested can be automatically tested, reducing the number of configuration files that need to be configured in the case of multiple products to be tested, and simplifying the test process; based on the configuration file, it is possible to test multiple products of one type in a batch, and even to test multiple types of products in a batch, which is conducive to improving the testing efficiency of Bluetooth products.

[0166] Furthermore, the Bluetooth product testing method of the present application will store the product identifiers corresponding to the qualified Bluetooth products found according to the condition information of the product to be tested in a certain order into the queue of products to be tested. During the testing process, the Bluetooth products corresponding to the product identifiers in the queue of products to be tested will be tested in turn. Importing the configuration file can automatically test batches of Bluetooth products that meet the conditions specified in the configuration file, further improving the testing efficiency of Bluetooth products; moreover, the Bluetooth products that meet the conditions specified in the configuration file will be screened in advance, and only one screening process is required, which is conducive to reducing the occupancy of terminal device resources, further accelerating testing efficiency and simplifying the testing process.

[0167] Moreover, the Bluetooth product testing method of the present application is applied on a terminal device, which is portable. When a region or production line needs to be tested, the terminal device that is not being tested temporarily can be moved to a different region or production line for testing. This is beneficial to improving the flexibility of the use of test equipment when testing Bluetooth products, reducing the number of test equipment required for Bluetooth product testing, and reducing testing costs.

[0168] See also Figure 8 , Figure 8 Schematic diagram of the structure of a terminal device provided in an embodiment of the present application. Figure 8As shown, another embodiment of the present application further proposes a terminal device, comprising: at least one processor 801; and a memory 802 communicatively connected to the at least one processor 801; wherein the memory 802 stores instructions executable by the at least one processor 801, and the instructions are executed by the at least one processor 801 so that the at least one processor 801 can execute the Bluetooth product testing method as described above.

[0169] Specifically, the terminal device may include: a processor 801, a memory 802, a communication interface 803 and a bus 804. The processor 801, the memory 802 and the communication interface 803 are connected to each other in communication within the device through the bus 804.

[0170] The processor 801 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0171] The memory 802 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory can store an operating system and other application programs. When the technical solution provided in the embodiment of the present application is implemented by software or firmware, the relevant program code is stored in the memory and called and executed by the processor.

[0172] The communication interface 803 is used to connect to a communication module (not shown in the figure) to realize communication interaction between the device and other devices. The communication module can realize communication through Bluetooth communication or wired communication (such as USB, network cable, etc.).

[0173] The bus 804 comprises a pathway that transmits information between the various components of the device (eg, processor, memory, input / output interface, and communication interface).

[0174] It should be noted that, although the above device only shows the processor 801, the memory 802, the communication interface 803 and the bus 804, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiment of the present application, and does not necessarily include all the components shown in the figure.

[0175] The terminal device of the above embodiment is used to implement the Bluetooth product testing method in the above corresponding embodiment, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0176] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A Bluetooth product testing method, characterized in that: The test method is applied to a terminal device, and the test method comprises: Obtain a configuration file, the configuration file including condition information of a product to be tested and at least one test item, wherein the condition information of the product to be tested is used to define a standard for determining whether it is a product to be tested, the at least one test item is used to define a test item of the product to be tested, and each of the at least one test item includes a plurality of test nodes; Searching for Bluetooth products that meet the conditions according to the condition information of the product to be tested, and storing the product identifiers corresponding to the found Bluetooth products in a queue of products to be tested in a certain order; Establish connections with target Bluetooth products corresponding to product identifiers in the queue of products to be tested in sequence, execute the at least one test item in sequence, and for each test item executed, execute multiple test nodes included in the test item in sequence.

2. The Bluetooth product testing method according to claim 1, characterized in that: The at least one test entry includes a test parameter, wherein the test parameter includes an operation identifier.

3. The Bluetooth product testing method according to claim 2, characterized in that: The operation identifier includes a service identifier and a channel identifier, wherein the channel identifier includes a read-write feature identifier or a notification feature identifier.

4. The Bluetooth product testing method according to claim 1, characterized in that: The condition information of the product to be tested includes a Bluetooth name template and a received signal strength threshold value of the product to be tested, wherein the Bluetooth name template of the product to be tested is the same part of the Bluetooth name of the product to be tested, and the received signal strength threshold value is used to define the minimum signal strength value from the product to be tested received on the terminal device; Alternatively, the product condition information to be tested includes a broadcast identification template of the product to be tested and the critical value of the received signal strength, wherein the broadcast identification template of the product to be tested is the same part of the broadcast identification of the product to be tested.

5. The Bluetooth product testing method according to claim 1, characterized in that: The product condition information to be tested and the at least one test item are associated with each other.

6. The method for testing a Bluetooth product according to any one of claims 1 to 5, characterized in that: The configuration file also includes additional product condition information to be tested and at least one additional test item corresponding to the additional product condition information to be tested, and the Bluetooth product corresponding to the product condition information to be tested and the Bluetooth product corresponding to the additional product condition information to be tested are tested in sequence.

7. The Bluetooth product testing method according to any one of claims 1 to 5, characterized in that: The test method also includes: receiving feedback data generated by the target Bluetooth product in response to executing the at least one test item; A test document for the target Bluetooth product is generated according to the feedback data.

8. The Bluetooth product testing method according to any one of claims 1 to 5, characterized in that: The configuration file further includes result description data, the result description data being used to indicate a display method of the test result of the product to be tested in response to executing one or more of the at least one test item; And the Bluetooth product testing method further includes: generating an indication signal according to the result description data.

9. A Bluetooth product testing device, characterized in that: Applied to terminal equipment, including: an acquisition unit, configured to acquire a configuration file, wherein the configuration file includes condition information of a product to be tested and at least one test item, wherein the condition information of the product to be tested is used to define a standard for determining whether it is a product to be tested, and the at least one test item is used to define a test item of the product to be tested, and each of the at least one test item includes a plurality of test nodes; A product determination unit is used to search for Bluetooth products that meet the conditions according to the condition information of the product to be tested, and store the product identifications corresponding to the found Bluetooth products in a queue of products to be tested in a certain order; The test unit is used to establish connections with target Bluetooth products corresponding to product identifiers in the product queue to be tested in sequence, and execute the at least one test item in sequence, and for each test item executed, execute multiple test nodes contained in the test item in sequence.

10. A terminal device, characterized in that: include: at least one processor; and a memory communicatively coupled to the at least one processor, The memory stores instructions that can be executed by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor can execute the Bluetooth product testing method as described in any one of claims 1-8.

Images