Gray scale test method and device based on battery replacement demand, and storage medium

Abstract

The invention discloses a gray scale test method and device based on a power conversion demand, and a storage medium, and belongs to the technical field of gray scale test. The method comprises the following steps: determining a mobile terminal in which a preset APP is downloaded, and obtaining a software version number of the APP of the mobile terminal; determining an IMEI (International Mobile Equipment Identity) equipment code and use data of the mobile terminal; the IMEI equipment code is analyzed to determine equipment data of the mobile terminal, and the equipment data comprises at least one of a brand name, an equipment model and an operating system version number; integrating the use data and the equipment data into a gray scale test database; acquiring a test requirement; screening a gray scale test database based on a test requirement to determine a gray scale test sample; and carrying out gray scale test based on the gray scale test sample. According to the method, a proper user can be selected as a gray level test object.

Description

[0001] This application claims priority based on the invention patent application titled "A Gray-Box Testing Method, Device, and Storage Medium Based on Battery-Swap Requirements" with an application number of 202311866262.1 and filed with the China National Intellectual Property Administration on December 29, 2023. This application incorporates the entire text of the above-mentioned Chinese patent application by reference. Technical Field

[0002] This application relates to the technical field of gray-box testing, and particularly to a gray-box testing method, device, and storage medium based on battery-swap requirements. Background Art

[0003] Gray-box testing means that before a product or application is officially released, a specific group of people are selected for trial use, and the number of trial users is gradually expanded to promptly discover and correct problems existing in the product or application.

[0004] A battery-swap station is a station that centrally stores, charges, and distributes a large number of batteries through a centralized charging station, and provides battery replacement services for electric vehicles in the battery distribution station or integrates battery charging, logistics distribution, and battery-swap services.

[0005] The update of an offline battery-swap station or the update of an online battery-swap service will result in the update of the corresponding APP of the battery-swap station. When updating, it is necessary to select appropriate users as test objects according to the update requirements.

[0006] Therefore, how to select appropriate users as the objects of gray-box testing has become an urgent problem to be solved. Summary of the Invention

[0007] Embodiments of this application provide a gray-box testing method, device, and storage medium based on battery-swap requirements to solve the following technical problem: how to select appropriate users as the objects of gray-box testing.

[0008] In a first aspect, embodiments of this application provide a gray-box testing method based on battery-swap requirements. The method includes: determining a mobile terminal with a preset APP downloaded thereon and obtaining the software version number of the APP of the mobile terminal; determining the IMEI device code and usage data of the mobile terminal; parsing the IMEI device code to determine the device data of the mobile terminal, where the device data includes at least one of brand name, device model, and operating system version number; integrating the usage data and the device data into a gray-box testing database; obtaining test requirements; screening the gray-box testing database based on the test requirements to determine gray-box testing samples; and performing gray-box testing based on the gray-box testing samples.

[0009] In an implementation of the present application, determining the IMEI device code of the mobile terminal specifically includes: when the APP is started, determining the permission setting of the mobile terminal for the APP; determining the data acquisition range of the APP based on the permission setting, and acquiring the usage data based on the data acquisition range; wherein, the data acquisition range is the permission opened by the APP; when the APP is determined to be in the whitelist, acquiring the IMEI device code of the mobile terminal and associating it with the user.

[0010] In an implementation of the present application, parsing the IMEI device code to determine the device data of the mobile terminal, where the device data includes at least one of brand name, device model, and operating system version number, specifically includes: acquiring an IMEI code database; wherein, the IMEI database includes a type allocation code database and a verification database; disassembling the IMEI device code to obtain a type code, a production sequence code, and a verification code; comparing the IMEI device code with the IMEI database to determine the brand name and device model of the mobile terminal; determining the operating system version number based on the brand name and device model of the mobile terminal.

[0011] In an implementation of the present application, disassembling the IMEI device code to obtain a type code, a production sequence code, and a verification code specifically includes: determining whether the IMEI device code contains special characters, and deleting the special characters when the IMEI device code contains special characters; wherein, the special characters are any characters other than numbers; when the IMEI device code does not contain special characters, intercepting the first eight characters of the IMEI device code to obtain the type code; when the IMEI device code does not contain special characters, intercepting the ninth to fourteenth characters of the IMEI device code to obtain the production sequence code; when the IMEI device code does not contain special characters, intercepting the fifteenth character of the IMEI device code to obtain the verification code.

[0012] In an implementation of the present application, integrating the usage data and the device data into a gray test database specifically includes: associating the IMEI device code with the brand name, device model, software version number, and operating system version number; associating the IMEI device code and the usage data with the user; when the brand name, device model, software version number, and operating system version number of at least two IMEI device codes are the same, determining whether the at least two IMEI device codes belong to the same natural person user, and marking the data of the same natural person user; constructing a gray test database with the IMEI device code as the reference.

[0013] In an implementation manner of the present application, when the brand names, device models, software version numbers, and operating system version numbers of the IMEI device codes greater than or equal to two are the same, it is determined whether the IMEI device codes greater than or equal to two belong to the same natural person user, and the data of the same natural person user is marked. Specifically, it includes: sending a request to obtain the MEID to the mobile terminal corresponding to the IMEI device code, and determining whether the MEID can be obtained according to the feedback of the request to obtain the MEID; for the mobile terminal that cannot obtain the MEID, determining whether the IMEI device codes greater than or equal to two belong to the same natural person user through the usage data; for the mobile terminal that can obtain the MEID, determining whether the IMEI device codes greater than or equal to two belong to the same natural person user through the MEID.

[0014] In an implementation manner of the present application, the gray test database is screened based on the test requirements to determine gray test samples. Specifically, it includes: screening the gray test database based on the test requirements to determine preliminary gray test samples, and sending a gray test invitation to the mobile terminals of the preliminary gray test samples; receiving the feedback of the gray test invitation within a preset time, and determining the gray test samples according to the test requirements.

[0015] In an implementation manner of the present application, the gray test database is screened based on the test requirements to determine preliminary gray test samples. Specifically, it includes: determining the test weight and test range according to the test requirements; screening the gray test database based on the test range to obtain a first gray test database; processing the first gray test database based on the test weight, and arranging the first gray test database in the order of weights to obtain a second gray test database; screening the IMEI device codes of the same natural person user in the second gray test database, and retaining one IMEI device code in the order to obtain the preliminary gray test samples.

[0016] In an implementation manner of the present application, the feedback of the gray test invitation is received within a preset time, and the gray test samples are determined according to the test requirements. Specifically, it includes: receiving and storing the feedback of the gray test invitation in sequence within a preset time to determine a first gray test sample; determining the gray test samples based on the test requirements and the number of the first gray test samples.

[0017] In a second aspect, an embodiment of the present application further provides a gray-box testing device based on battery swapping requirements. The device includes: a first acquisition module, configured to determine a mobile terminal with a preset APP downloaded thereon and acquire the software version number of the APP of the mobile terminal; a data determination module, configured to determine the IMEI device code and usage data of the mobile terminal; a parsing module, configured to parse the IMEI device code to determine the device data of the mobile terminal, where the device data includes at least one of a brand name, a device model, and an operating system version number; an integration module, configured to integrate the usage data and the device data into a gray-box testing database; a second acquisition module, configured to acquire testing requirements; a screening module, configured to screen the gray-box testing database based on the testing requirements to determine gray-box testing samples; and a testing module, configured to perform gray-box testing based on the gray-box testing samples.

[0018] In a third aspect, an embodiment of the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the method for gray-box testing based on battery swapping requirements as described in any one of the above is implemented.

[0019] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method for gray-box testing based on battery swapping requirements as described in any one of the above is implemented.

[0020] A method, device, and storage medium for gray-box testing based on battery swapping requirements provided by an embodiment of the present application can obtain the usage data, IMEI device code, software version number, and operating system version number of a mobile terminal by determining the permission opening and whitelist status of a mobile terminal with a preset APP downloaded thereon, thereby constructing a gray-box testing database. By organizing the above data, data belonging to the same natural person can be integrated, so as to avoid, to a certain extent, users with multiple accounts from being repeatedly selected as objects for gray-box testing, thereby improving the gray-box testing; after obtaining the testing requirements, the gray-box testing database is screened based on the testing requirements, the testing objects are determined, the testing willingness of the testing objects is received, and then the testing receipts are received in sequence, so as to screen out, to a certain extent, users who do not want to participate in the testing. If the received testing receipts exceed the predetermined number of testing people, screening can be performed to select an appropriate number of testing people, thereby generating gray-box testing samples, that is, appropriate users can be selected as objects for gray-box testing. Description of the Drawings

[0021] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments and descriptions thereof of the present application are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0022] Figure 1 Flow chart of a gray box testing method based on battery swapping requirements provided by an embodiment of the present application;

[0023] Figure 2 Schematic diagram of the internal structure of a gray box testing device based on battery swapping requirements provided by an embodiment of the present application. Detailed implementation manners

[0024] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part rather than all of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the scope of protection of the present application.

[0025] The embodiments of the present application provide a gray box testing method, device and storage medium based on battery swapping requirements to solve the following technical problem: how to select appropriate users as the objects of gray box testing.

[0026] The technical solutions proposed in the embodiments of the present application will be described in detail below with reference to the drawings.

[0027] Figure 1 Gray box testing flow chart based on battery swapping requirements provided by an embodiment of the present application. As Figure 1 shown, a gray box testing method based on battery swapping requirements provided by an embodiment of the present application specifically includes the following steps:

[0028] Step 1: Determine a mobile terminal with a preset APP downloaded thereon, and obtain the software version number of the APP on the mobile terminal.

[0029] The gray box testing and screening method in the embodiments of the present application is based on an APP related to a real battery swapping station, so it is necessary for the testing object to download the preset APP.

[0030] In a specific example, when the user downloads the preset APP and during the registration phase, the user registers an account according to their own data (such as mobile phone number, email, etc.), then the mobile terminal with the preset APP downloaded thereon can be determined. The mobile terminal can be a device that can be carried around, such as a tablet or a mobile phone.

[0031] Step 2: Determine the IMEI device code and usage data of the mobile terminal.

[0032] APP embedding technology is a technology used to collect user behavior data in an APP. By setting up embeds in the APP, it is possible to monitor user operations on the APP, such as clicks, swipes, searches, etc., as well as relevant user behavior data, such as user stay time, page jumps, etc.

[0033] It should be noted that the APP embedding technology needs to comply with certain conditions, that is, the user needs to be aware of the scope of data acquisition by the APP.

[0034] The usage data includes data such as vehicle models, vehicle battery swapping records, and user usage levels. The vehicle battery swapping records include data such as battery swapping time, battery swapping location, and battery swapping mileage.

[0035] Step 21: When the APP starts, determine the permission settings of the mobile terminal for the APP.

[0036] In a specific example, when the APP starts, the APP asks the user of the terminal whether to open the camera permission, address book permission, and location acquisition permission. After the user opens the camera permission, address book permission, and location acquisition permission for the APP device, the APP can obtain information such as QR codes through the camera of the mobile terminal.

[0037] Step 22: Based on the permission settings, determine the data acquisition scope of the APP, and obtain usage data based on the data acquisition scope.

[0038] Referring to Step 21, after determining the permission settings of the mobile terminal for the APP, the usage data can be obtained according to the permission settings, and the data acquisition scope is the permissions opened by the APP.

[0039] Step 23: When the APP is determined to be in the whitelist, obtain the IMEI device code of the mobile terminal and associate it with the user.

[0040] Because in some mobile terminals, the user needs to manually operate to place the APP in the whitelist. After the user places the APP in the whitelist, the device code of the mobile terminal can be obtained. After obtaining the device code, the device code is associated with the user to facilitate associating the parsed data of the IMEI device code with the user in subsequent gray box testing.

[0041] Step 3: Parse the IMEI device code to determine the device data of the mobile terminal, where the device data includes at least one of brand name, device model, and operating system version number.

[0042] IMEI device code, that is, International Mobile Equipment Identity, is equivalent to the ID card of a mobile phone and is used to identify each independent mobile terminal such as a mobile phone in a mobile phone network. The IMEI code consists of 15 to 17 digits. The first 8 digits are the model approval number, that is, the type code, which is the code for distinguishing mobile phone brands and models. The next 2 digits are the final assembly number, representing the code for the final assembly. After that, 6 digits are the serial number, representing the production sequence number. The last 1 digit is the verification code, which is used to verify whether the IMEI device code is accurate.

[0043] The specific process is shown in Steps 31 to 33.

[0044] Step 31: Obtain the IMEI code database.

[0045] The IMEI database includes a type allocation code database and a verification library.

[0046] Type allocation code database: Stores the brand names and device models of mobile terminals corresponding to the type codes and type numbers.

[0047] Verification library: Stores the verification code algorithms corresponding to each type code.

[0048] Step 32: Decompose the IMEI device code to obtain the type code, production sequence code, and verification code.

[0049] The specific steps are shown in Steps 321 to 323.

[0050] Step 321: Determine whether the IMEI device code contains special characters, and delete the special characters if they exist in the IMEI device code.

[0051] Special characters are any characters other than numbers. There may be special characters in the IMEI device code. In order to reduce the storage pressure in the type allocation code database, the type codes in the type allocation code database are those with special characters removed.

[0052] Step 322: When there are no special characters in the IMEI device code, intercept the first eight characters of the IMEI device code to obtain the type code.

[0053] As can be seen from Step 3, the first 8 digits are the model approval number, that is, the type code, which is the code for distinguishing mobile phone brands and models. Therefore, the type code can be obtained.

[0054] Step 323: When there are no special characters in the IMEI device code, intercept the ninth to fourteenth characters of the IMEI device code to obtain the production sequence code.

[0055] As can be seen from Step 3, the next 6 digits are the serial number, representing the production sequence number. Therefore, the production sequence code can be obtained.

[0056] Step 324: When there are no special characters in the IMEI device code, intercept the fifteenth character of the IMEI device code to obtain the verification code.

[0057] As can be seen from Step 3, the last digit is the verification code, which is used to verify whether the IMEI device code is accurate.

[0058] Step 33: Compare the IMEI device code with the IMEI database to determine the brand name and device model of the mobile terminal.

[0059] Step 34: Determine the operating system version number based on the brand name and device model of the mobile terminal.

[0060] The operating system version number can be known through the brand name and device model of the device. This technology is an existing technology and will not be elaborated here.

[0061] Step 4: Integrate the usage data and the device data into a gray test database.

[0062] After obtaining various data, it is necessary to bind the more similar data to the user, that is, integrate the usage data, IMEI device code, software version number, brand name, device model, and operating system version number into a gray test database. The specific steps can be seen from Step 41 to Step 44.

[0063] Step 41: Associate the IMEI device code with the brand name, device model, software version number, and operating system version number.

[0064] Step 42: Associate the IMEI device code and the usage data with the user.

[0065] Step 43: When the brand name, device model, software version number, and operating system version number of two or more IMEI device codes are the same, determine whether two or more IMEI device codes belong to the same natural person user, and mark the data of the same natural person user.

[0066] In the existing technology, mobile phones generally support dual SIM dual standby, and mobile phones with dual SIM dual standby have two IMEI device codes. There are also some mobile phones with triple SIM triple standby, etc. Generally, one mobile phone corresponds to one natural person. If a user registers two accounts in the APP through two different mobile phone numbers of the same mobile phone, the obtained IMEI device codes are two. If these two device codes are selected in the gray test, it will undoubtedly reduce the accuracy of the gray test. Therefore, it is necessary to select and merge these two device codes. The specific steps are shown in Step 431 to Step 433.

[0067] Step 431: Send a request to obtain the MEID to the mobile terminal corresponding to the IMEI device code, and determine whether the MEID can be obtained according to the feedback of the request to obtain the MEID.

[0068] MEID is the abbreviation of Mobile Equipment Identifier, which is the identification code of a mobile phone and also the unique identification code for each mobile phone or communication tablet. Through this identification code, the network side can track and supervise the mobile phone. The value range of MEID is in hexadecimal, similar to the format of IMEI. MEID is mainly assigned to each unique mobile phone.

[0069] Send a request instruction to obtain the MEID. The user selects whether to send the MEID and will obtain feedback. Based on the feedback, it can be determined whether the MEID can be obtained.

[0070] Step 432: For a mobile terminal that cannot obtain the MEID, use data to determine whether at least two IMEI device codes belong to the same natural person user.

[0071] For a mobile terminal that cannot obtain the MEID, it can be determined whether the IMEI device codes belong to the same natural person user according to the usage data.

[0072] In a specific case, there are two IMEI device codes with the same brand name, device model, software version number, and operating system version number. The usage data is as follows:

[0073] IMEI1: Vehicle model A, battery replacement record at 12:01 on January 4 in area B, 12 minutes of using the APP on January 4, etc.;

[0074] IMEI2: Vehicle model A, battery replacement record at 12:01 on January 4 in area B, 12 minutes of using the APP on January 4, etc.

[0075] It can be determined that IMEI1 and IMEI2 belong to the same natural person user.

[0076] Step 433: For a mobile terminal that can obtain the MEID, use the MEID to determine whether at least two IMEI device codes belong to the same natural person user.

[0077] For a mobile terminal that can obtain the MEID, it can be determined whether at least two IMEI device codes belong to the same natural person user through the association relationship, which will not be elaborated here.

[0078] Step 44: Build a gray test database based on the IMEI device code.

[0079] Since there is an association relationship between the IMEI device code and other data, a gray test database can be built according to the IMEI device code.

[0080] Step 5: Obtain test requirements.

[0081] In the gray-box testing, there are test requirements based on the APP update, then obtain the test requirements.

[0082] Step 6: Filter the gray-box testing database based on the test requirements to determine the gray-box testing samples.

[0083] Different updates require different testers for testing, and the specific steps are shown from Step 61 to Step 62.

[0084] Step 61: Filter the gray-box testing database based on the test requirements to determine the preliminary gray-box testing samples, and send gray-box testing invitations to the mobile terminals of the preliminary gray-box testing samples.

[0085] Step 611: Determine the test weights and test scope according to the test requirements.

[0086] In a specific example, the APP has updated a new service. This service is mainly to establish some commercial vehicle battery swapping stations to enable better battery swapping services for commercial vehicles, and a part of commercial vehicle battery swapping stations have been deployed in City B first.

[0087] Then the test scope: commercial vehicles, vehicles in City B.

[0088] Test weights: commercial mileage (weight 3), activity range (weight 4), etc.

[0089] Step 612: Filter the gray-box testing database based on the test scope to obtain the first gray-box testing database.

[0090] By filtering the gray-box testing database through the test scope, the first gray-box testing database can be determined. This first testing database is a database that includes the test scope.

[0091] Step 613: Process the first gray-box testing database based on the test weights and sort the first gray-box testing database in the order of weights to obtain the second gray-box testing database.

[0092] By multiplying each data item in the first gray-box testing database by the test weights, the weighted part of each data can be obtained. Sorting according to the weight size, the second gray-box testing database can be obtained.

[0093] Step 614: Filter the IMEI device codes of the same natural person user in the second gray-box testing database and retain one IMEI device code in order to obtain the preliminary gray-box testing samples.

[0094] During the screening process, because multiple IMEI device codes of the same device are not distinguished, there may be multiple IMEI device codes of the same natural person in the second grayscale test database. In this case, one IMEI device code can be selected by marking the multiple IMEI device codes of the same natural person, thereby obtaining a preliminary grayscale test sample.

[0095] It should be noted that an IMEI device code can be selected manually, or the IMEI device code with the highest ranking can be selected in order.

[0096] Step 62: Receive feedback on the grayscale test invitation within a preset time, and determine a grayscale test sample according to the test requirements.

[0097] Step 621: Receive and store grayscale test invitation feedback in sequence within a preset time to determine a first grayscale test sample.

[0098] After sending the grayscale test invitation to the mobile terminal of the preliminary grayscale test sample, the user chooses whether to participate in the grayscale test according to his / her wishes, that is, obtains feedback on the grayscale test invitation, and combines the data associated with the feedback on the grayscale test invitation to determine the first grayscale test sample.

[0099] Step 622: Determine grayscale test samples based on the test requirements and the number of first grayscale test samples.

[0100] For the first grayscale test samples obtained, if the number of the first grayscale test samples obtained exceeds the test requirement, it is necessary to delete part of the data in the first test sample, that is, determine the deletion number according to the test requirement and the number of the first grayscale test samples to obtain grayscale test samples.

[0101] It should be noted that if the number of the first grayscale test samples is less than the test requirement, step 6 may be repeated until the test requirement is met.

[0102] Step 7: Perform a grayscale test based on the grayscale test sample.

[0103] After obtaining the grayscale test sample, the grayscale test can be carried out according to the grayscale test sample, for example, an update package is sent to users in the grayscale test sample.

[0104] The above is an embodiment of the method proposed in this application. Based on the same inventive concept, the embodiment of this application also provides a grayscale testing device based on battery replacement requirements, the device comprising:

[0105] A first acquisition module, configured to determine a mobile terminal with a preset APP downloaded thereon, and acquire the software version number of the APP of the mobile terminal; a data determination module, configured to determine the IMEI device code and usage data of the mobile terminal; a parsing module, configured to parse the IMEI device code to determine device data of the mobile terminal, where the device data includes at least one of a brand name, a device model, and an operating system version number; an integration module, configured to integrate the usage data and the device data into a gray test database; a second acquisition module, configured to acquire a test requirement; a screening module, configured to screen the gray test database based on the test requirement to determine a gray test sample; a test module, configured to perform a gray test based on the gray test sample.

[0106] The above is the method embodiment provided by this application. Based on the same inventive concept, the embodiment of this application also provides a gray test electronic device based on a battery swapping requirement, and its structure is as Figure 2 shown.

[0107] Figure 2 This is a schematic internal structure diagram of a gray test device based on a battery swapping requirement provided by an embodiment of this application. As Figure 2 shown, the device includes:

[0108] At least one processor 201;

[0109] And a memory 202 communicatively connected to at least one processor;

[0110] Wherein, the memory 202 stores instructions executable by at least one processor, and the instructions are executed by at least one processor 201 so that at least one processor 201 can:

[0111] Determine a mobile terminal with a preset APP downloaded thereon, and acquire the software version number of the APP of the mobile terminal; determine the IMEI device code and usage data of the mobile terminal; parse the IMEI device code to determine device data of the mobile terminal, where the device data includes at least one of a brand name, a device model, and an operating system version number; integrate the usage data and the device data into a gray test database; acquire a test requirement; screen the gray test database based on the test requirement to determine a gray test sample; perform a gray test based on the gray test sample.

[0112] In other embodiments of this application, when the instructions are executed by at least one processor 201, the steps of the gray test method based on the battery swapping requirement in any of the above embodiments can also be implemented.

[0113] Some embodiments of this application provide corresponding to Figure 1A non-volatile computer storage medium for gray-box testing based on battery swapping requirements, storing computer-executable instructions, and the computer-executable instructions are set as follows:

[0114] Identify mobile terminals that have downloaded a preset APP, and obtain the software version number of the APP on the mobile terminals; determine the IMEI device code and usage data of the mobile terminals; parse the IMEI device code to determine the device data of the mobile terminals, where the device data includes at least one of the brand name, device model, and operating system version number; integrate the usage data and the device data into a gray-box testing database; obtain testing requirements; screen the gray-box testing database based on the testing requirements to determine gray-box testing samples; perform gray-box testing based on the gray-box testing samples.

[0115] In other embodiments of the present application, the executable instructions may also implement the steps of the gray-box testing method based on battery swapping requirements in any of the above embodiments.

[0116] The embodiments in the present application are all described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the embodiments of the Internet of Things devices and media, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments.

[0117] The systems and media provided by the embodiments of the present application correspond one by one to the methods. Therefore, the systems and media also have beneficial technical effects similar to those of the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the systems and media will not be elaborated here.

[0118] Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program codes.

[0119] This application is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, as well as the combination of flows and / or blocks in the flowchart and / or block diagram. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce means for implementing the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0120] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufactured article including instruction means that implement the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0121] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0122] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0123] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0124] A computer-readable medium includes both permanent and non-permanent, removable and non-removable media and can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer-readable medium does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0125] It should also be noted that the term "comprising", "including" or any other variation thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.

[0126] The above are only examples of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. A gray-box testing method based on battery swapping requirements, characterized in that The method includes: Determine a mobile terminal with a preset APP downloaded, and obtain the software version number of the APP on the mobile terminal; Determine the IMEI device code and usage data of the mobile terminal; Analyze the IMEI device code to determine the device data of the mobile terminal, where the device data includes at least one of brand name, device model, and operating system version number; Integrate the usage data and the device data into a gray test database; Obtain test requirements; Filter the gray test database based on the test requirements to determine gray test samples; Conduct a gray test based on the gray test samples.

2. The gray box testing method based on battery swapping requirements according to claim 1, wherein Determine the IMEI device code of the mobile terminal, specifically including: When the APP is started, determine the permission settings of the mobile terminal for the APP; Determine the data acquisition range of the APP based on the permission settings, and obtain the usage data based on the data acquisition range; where the data acquisition range is the permissions opened by the APP; When the APP is determined to be in the whitelist, obtain the IMEI device code of the mobile terminal and associate it with the user.

3. A gray-box testing method based on battery swapping requirements according to claim 1, characterized in that Analyze the IMEI device code to determine the device data of the mobile terminal, where the device data includes at least one of brand name, device model, and operating system version number, specifically including: Obtain an IMEI code database; where the IMEI database includes a type allocation code database and a verification database; Decompose the IMEI device code to obtain a type code, a production sequence code, and a verification code; Compare the IMEI device code with the IMEI database to determine the brand name and device model of the mobile terminal; Determine the operating system version number based on the brand name and device model of the mobile terminal.

4. The gray-box testing method based on battery swapping requirements according to claim 3, characterized in that Decompose the IMEI device code to obtain a type code, a production sequence code, and a verification code, specifically including: Determine whether the IMEI device code contains special characters, and when the IMEI device code contains special characters, delete the special characters; where the special characters are any characters other than numbers; When the IMEI device code does not contain special characters, intercept the first eight characters of the IMEI device code to obtain the type code; When the IMEI device code does not contain special characters, intercept the ninth to fourteenth characters of the IMEI device code to obtain the production sequence code; When the IMEI device code does not contain special characters, intercept the fifteenth character of the IMEI device code to obtain the verification code.

5. A gray-box testing method based on battery swapping requirements according to claim 1, characterized in that Integrate the usage data and the device data into a gray test database, specifically including: Associate the IMEI device code with the brand name, device model, software version number, and operating system version number; Associate the IMEI device code and usage data with the user; When the brand name, device model, software version number, and operating system version number of at least two IMEI device codes are the same, determine whether the at least two IMEI device codes belong to the same natural person user, and mark the data of the same natural person user; Construct a gray-box testing database based on the IMEI device code.

6. The gray box testing method based on battery swapping requirements according to claim 5, wherein When the brand names, device models, software version numbers, and operating system version numbers of the IMEI device codes that are greater than or equal to two are the same, determine whether the IMEI device codes that are greater than or equal to two belong to the same natural user, and label the data of the same natural user, specifically including: Send a request to obtain the MEID to the mobile terminal corresponding to the IMEI device code, and determine whether the MEID can be obtained according to the feedback of the request to obtain the MEID; For mobile terminals that cannot obtain the MEID, determine whether the IMEI device codes that are greater than or equal to two belong to the same natural user through the usage data; For mobile terminals that can obtain the MEID, determine whether the IMEI device codes that are greater than or equal to two belong to the same natural user through the MEID.

7. A gray box testing method based on battery swapping requirements according to claim 1, characterized in that Filter the gray-box testing database based on the testing requirements to determine gray-box testing samples, specifically including: Filter the gray-box testing database based on the testing requirements to determine preliminary gray-box testing samples, and send a gray-box testing invitation to the mobile terminals of the preliminary gray-box testing samples; Receive the feedback of the gray-box testing invitation within a preset time, and determine the gray-box testing samples according to the testing requirements.

8. A gray box testing method based on battery swapping requirements according to claim 7, characterized in that, Filter the gray-box testing database based on the testing requirements to determine preliminary gray-box testing samples, specifically including: Determine the testing weights and testing scope according to the testing requirements; Filter the gray-box testing database based on the testing scope to obtain a first gray-box testing database; Process the first gray-box testing database based on the testing weights, and arrange the first gray-box testing database in the order of weights to obtain a second gray-box testing database; Filter the IMEI device codes of the same natural user in the second gray-box testing database, and retain one IMEI device code in the order to obtain the preliminary gray-box testing samples.

9. A gray box testing method based on battery swapping requirements according to claim 7, characterized in that Receive the feedback of the gray-box testing invitation within a preset time, and determine the gray-box testing samples according to the testing requirements, specifically including: Receive and store the feedback of the gray-box testing invitation in order within a preset time to determine the first gray-box testing samples; Determine the gray-box testing samples based on the testing requirements and the number of the first gray-box testing samples.

10. A gray box testing device based on battery swapping requirements, characterized in that, The device includes: A first acquisition module, used to determine a mobile terminal with a preset APP downloaded, and obtain the software version number of the APP of the mobile terminal; A data determination module, used to determine the IMEI device code and usage data of the mobile terminal; An analysis module, used to analyze the IMEI device code to determine the device data of the mobile terminal, and the device data includes at least one of a brand name, a device model, and an operating system version number; An integration module, used to integrate the usage data and the device data into a gray-box testing database; A second acquisition module, used to obtain testing requirements; A filtering module, used to filter the gray-box testing database based on the testing requirements to determine gray-box testing samples; A testing module, used to perform gray-box testing based on the gray-box testing samples.

11. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method for gray-box testing based on battery swapping requirements described in any one of claims 1-9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the method for gray-box testing based on battery swapping requirements described in any one of claims 1-9.

Images