Method and system for generating test case based on burying point data and electronic equipment

Abstract

The invention provides a method and a system for generating a test case based on burying point data and electronic equipment, the method abandons a traditional mode of generating the test case by video playback, the burying point data generated by user operation is acquired in real time, and when a tester needs to test a to-be-tested functional node, the test case is generated in real time. The method comprises the following steps: in response to a to-be-tested function node selected by a tester, obtaining real-time buried point data generated by a user and associated with the to-be-tested function node, page display information of an interactive interface of a to-be-tested object, interface information of the to-be-tested object and other target information; and generating a test case file according to the data after standardization processing of the target information. Thus, a large number of real-time buried point data generated when a user actually uses the to-be-tested object is obtained, operation logic exists between the obtained real-time buried point data, when actual operation changes occur, the generated test case is still effective, and the problem that the test case generated through traditional video playback cannot adapt to actual operation offset is effectively solved.

Description

Technical Field

[0001] This application relates to the field of software testing technology, and in particular to a method, system, and electronic device for generating test cases based on embedded data. Background Technology

[0002] After developers complete the development of software or a specific function within software, testers typically test the software or its functionality to verify whether the software's functions, performance, and other metrics meet expectations. Test cases, as standardized test documents used in software testing, specify the test objects, test methods, and expected test results. Testers frequently apply these cases during the testing process to test the software or its functions according to the methods defined in the test cases, and ultimately determine whether the test results meet the expected results specified in the test cases.

[0003] Test cases are typically generated by testers through a step-by-step process of requirements analysis, business logic decomposition, and classic testing methodologies, requiring a significant amount of manual labor. To save time in manually generating test cases, related technologies propose using tools or scripts to replace manual labor. These tools automatically generate executable code or scripts as test cases based on the software's interaction scenarios or execution business requirements.

[0004] Common methods for automating test case generation include using tools to record every step a tester takes on the software interface in real time, and then automatically generating corresponding script files based on the tester's actions. However, this method of generating test case files through video playback only records the actions but cannot determine the reasons behind them. If the actual actions deviate from those recorded in the playback, the generated test cases will be unable to test those actions, rendering the test cases invalid. Summary of the Invention

[0005] In view of this, embodiments of this application provide a method, system, and electronic device for generating test cases based on embedded data, in order to solve the problem that traditional video playback test case generation cannot adapt to actual operational deviations.

[0006] In a first aspect, embodiments of this application provide a method for generating test cases based on embedded data, wherein the method includes: Real-time tracking data associated with user identity information is obtained based on user identity information; wherein, the real-time tracking data is: real-time operation data generated by the user on the interactive interface of the object to be tested; In response to the functional node to be tested selected by the tester, target information associated with the functional node to be tested is obtained and the target information is standardized; the target information includes at least: the real-time data points, the page display information of the interactive interface of the object under test, and the interface information of the object under test; Based on the data obtained from the standardization process, a test case file for the object under test is generated.

[0007] Secondly, embodiments of this application provide a system for generating test cases based on embedded data, wherein the system includes: an interaction unit, a data processing unit, and a test case management unit, wherein: The interaction unit is used to obtain real-time tracking data associated with the user identity information based on the user identity information; wherein, the real-time tracking data is: real-time operation data generated by the user on the interactive interface of the object to be tested; The data processing unit is used to respond to the test node selected by the tester, acquire target information associated with the test node, and perform standardized processing on the target information; the target information includes at least: the real-time data points, the page display information of the interactive interface of the test object, and the interface information of the test object; The test case management unit is used to generate test case files for the object under test based on the data obtained from the standardization process.

[0008] Thirdly, embodiments of this application provide an electronic device, wherein the electronic device includes: a processor; and a memory storing a program; wherein the program includes instructions, which, when executed by the processor, cause the processor to perform the method for generating test cases based on embedded data as described in the first aspect.

[0009] Fourthly, embodiments of this application provide a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to execute the method for generating test cases based on embedded data as described in the first aspect.

[0010] The beneficial effects of this application are: This application provides a method, system, and electronic device for generating test cases based on event tracking data. This method abandons the traditional method of generating test cases by playing back video recordings. By acquiring event tracking data generated by user operations in real time, when testers need to test the functional node under test, the method responds to the functional node under test selected by the testers, acquires the real-time event tracking data generated by users associated with the functional node under test, the page display information of the interactive interface of the object under test, and the interface information of the object under test, and generates test case files by standardizing the data of these target information.

[0011] By selecting the embodiments of this application, a large amount of real-time tracking data generated by users when actually using the object under test is obtained. There is operational logic among the real-time tracking data, rather than simply the position of page elements. The real-time tracking data and interface information are standardized to know which interfaces the user calls. Then, the test cases generated based on this information cover more complete operation types and know the reasons for the specific operations. When actual operation changes, the generated test cases are still valid, effectively solving the problem that traditional video playback test cases cannot adapt to actual operation deviations. Attached Figure Description

[0012] Further details, features, and advantages of this application are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which: Figure 1 This paper illustrates a flowchart of a method for generating test cases based on embedded data provided in this application. Figure 2 This illustration shows an example of the effect of real-time data processing provided in this application; Figure 3 This illustration shows a schematic diagram of the test case display interface provided in this application. Figure 4 This illustration shows a demonstration effect of a single test case provided in this application; Figure 5 This illustration shows a demonstration effect of one of the test cases provided in this application; Figure 6 This paper illustrates an execution effect diagram of one of the test cases provided in this application; Figure 7 This diagram illustrates another execution effect of the test cases provided in this application; Figure 8 This diagram illustrates another execution effect of the test cases provided in this application; Figure 9 This diagram illustrates another execution effect of the test cases provided in this application; Figure 10 This paper presents a schematic diagram of a system architecture for generating test cases based on embedded data, as provided in this application. Figure 11 A structural block diagram of an exemplary electronic device that can be used to implement embodiments of this application is shown. Detailed Implementation

[0013] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While some embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this application. It should be understood that the drawings and embodiments of this application are for illustrative purposes only and are not intended to limit the scope of protection of this application.

[0014] It should be understood that the steps described in the method embodiments of this application may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this application is not limited in this respect.

[0015] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc., mentioned in this application are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0016] It should be noted that the terms "a" and "a plurality of" used in this application are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0017] To better understand the problems with traditional methods of generating test cases through video playback, the applicant provides the following example: When using video playback to generate test cases, the playback records the coordinates of the specific actions performed by the tester on the screen. For example, the login icon in the upper right corner of the screen corresponds to coordinates x=100, y=200. If the software is updated and the coordinates of the login icon change to x=100, y=400, the test logic of the previously generated test cases for the login function will no longer be able to test for that login icon, resulting in a "login failed, please retry" error. Therefore, it is necessary to re-record the operation and generate new test cases.

[0018] It is evident that traditional methods for generating test cases based on video playback cannot adapt to situations where deviations occur during actual operation. Therefore, this application provides a method, system, and electronic device for generating test cases based on event tracking data. Specifically, in its first aspect, this application provides a method for generating test cases based on event tracking data. This method is applicable to any electronic device capable of generating test cases based on event tracking data, including but not limited to personal mobile terminals, computers, or servers. Figure 1 As shown, the method includes the following steps: S11. Obtain real-time tracking data associated with the user identity information based on the user identity information; wherein, the real-time tracking data is: real-time operation data generated by the user on the interactive interface of the object to be tested; S12. In response to the test node selected by the tester, acquire the target information associated with the test node and standardize the target information; the target information includes at least: the real-time data points, the page display information of the interactive interface of the test object, and the interface information of the test object. S13. Generate test case files for the object under test based on the data obtained from the standardization process.

[0019] This method abandons the traditional approach of generating test cases through video playback. Instead, it acquires real-time data from user actions and, when testers need to test a functional node, it responds to the selected functional node by acquiring real-time data from users associated with that functional node, page display information of the interactive interface of the object under test, and interface information of the object under test. After standardizing these target information, it generates test case files.

[0020] By selecting the embodiments of this application, a large amount of real-time tracking data generated by users when actually using the object under test is obtained. There is operational logic among the real-time tracking data, rather than simply the position of page elements. The real-time tracking data and interface information are standardized to know which interfaces the user calls. Then, the test cases generated based on this information cover more complete operation types and know the reasons for the specific operations. When actual operation changes, the generated test cases are still valid, effectively solving the problem that traditional video playback test cases cannot adapt to actual operation deviations.

[0021] The following will provide a detailed explanation of steps S11 to S13 with specific examples: In this application, real-time event tracking data refers to the behavioral data (such as button clicks or interface browsing) generated by a user during an interaction with the application, which is captured, processed, and transmitted in real time to the application's backend server. In this application, the object under test refers to the software testing object, which can specifically refer to the application under test or a specific application function under test.

[0022] When capturing real-time event tracking data, the user's interaction logic on the application interface can be determined based on the business type of the operation page corresponding to the captured real-time event tracking data and the time corresponding to the captured real-time event tracking data. Specifically, the user's operation sequence logic can be determined based on the timestamp of the real-time event tracking data generated by the user. Alternatively, the business chain of the user's operation can be determined based on the business type of the page elements on the operation page corresponding to the user's real-time event tracking data. For example, if the user operates element a (identity authentication), element b (application submission), and element c (transaction), the user's business behavior pattern on the operation page can be determined through the business chain expression: identity authentication a - application submission b - transaction c. When capturing real-time event tracking data generated by the user, the real-time event tracking data generated by the user can be associated and stored according to the user's identity identification information (such as user ID information or user device identification information) and stored under a specified real-time event tracking data path. This allows all real-time event tracking data bound to the user's identity identification information to be retrieved from this real-time event tracking data path during step S11, using the user's identity identification information as an index.

[0023] Among them, user identification information can be user ID, which is a unique user ID that the application automatically assigns to the user when the user accesses the online application or is extracted from the user's login and other operations. User identification information can be used for subsequent tracking and association of relevant information of the user.

[0024] The method provided in this application is applied to software testing scenarios. When testers need to perform software testing, they need to obtain corresponding test instances to verify the software functions. At this time, testers can input the functions to be tested in the interactive interface of the test system based on event tracking data generation provided in this application. Typically, a software application has several functions. For example, an e-commerce application may have different functions such as login, transaction, and product listing. A single page may also contain several functions. In this application, the functions contained in the object under test are broken down into nodes, with one function corresponding to one function node. When testers need to test a certain function or several functions, they can select or input the functions to be tested in the interactive interface to obtain the corresponding function nodes to be tested.

[0025] In some possible embodiments, the functional node under test can also be the smallest functional unit with clear business semantics and testability, formed by data aggregation and semantic refinement based on the actual online user operation path and core business process. This functional node under test is the key to connecting user behavior data with the automated generation of test cases. The functional node under test has business relevance, and testers can select the key operation path according to the user operation path generated in the following step S11-1: Based on the user identity information, obtain all data associated with the user identity information, and assemble them according to preset assembly rules to generate user operation path information.

[0026] In other words, in this application, the functional node to be tested can be a user operation path. As one implementation method, this key operation path can be a high-frequency user operation chain within a business scenario, such as login verification - order submission - payment confirmation. This high-frequency user operation chain can be considered as a functional node to be tested. Simply put, different test functional nodes can be understood as the sum of key functional steps frequently performed by real users, the corresponding operation types, operation conditions, and expected results for each key functional step.

[0027] As one implementation method, after acquiring all data associated with user identification information, it is assembled according to a preset assembly rule to generate user operation path information. This assembly can be performed according to the order of business transactions or the order in which operations occur. As one implementation method, the assembly of all data associated with user identification information can be achieved through the following steps: Based on the timestamps and business types carried by all data associated with the user identity information, the data belonging to the same business type are arranged and assembled in chronological order according to the timestamps to obtain the user operation path information.

[0028] In step S11, real-time event tracking data associated with user identity information is obtained. This real-time event tracking data is initially unordered and disorganized. Based on the timestamps and business flow information within the real-time event tracking data, all data is organized into a time-series dataset in chronological order. This process can be achieved by using page data as the statistical unit, connecting all user actions on the same page in chronological order.

[0029] The method provided in this application is applied to a test case generation system, which serves testers in performing functional testing of software. This test case generation system includes (e.g., Figures 2-9As shown in the interactive interface, testers can directly select the required content and then generate test cases based on the information selected by the testers.

[0030] In one implementation method, when performing step S11, it can be as follows: Figure 2 As shown, testers can enter a user ID and select the basic information associated with that user ID in the interactive interface. They can also select a date and time period to choose which time period's basic information they want to retrieve. The backend can then retrieve all the basic information associated with that user ID within that time period, based on the selected time period and user ID. This basic information includes: real-time event tracking data. Real-time event tracking data includes information about the various pages the user interacts with while using the application, such as information from the homepage and the data entry page. The basic information also includes the data interfaces corresponding to the page elements the user interacts with, such as interface A and interface B, where different data interfaces correspond to different input and output parameters.

[0031] Furthermore, all information belonging to the same page is aggregated into a file corresponding to that page, using page nodes as the statistical unit. At this point, a file corresponding to a page can serve as a node for a function to be tested. When testers need to test software functionality on a specific page, they can select the corresponding file. The system, responding to the selected node, can retrieve all basic information under that node and generate corresponding test case files based on that information. For example, it can be done as follows... Figure 3 As shown, all information belonging to the Loan_Trial Calculation Page is summarized under the Loan_Trial Calculation Page_Display file, all information from the Loan-Supplement Page is summarized under the Loan_Supplement Page_Display file, and so on.

[0032] Based on this, when performing step S12 to standardize the target information, standardization can be performed on all information under the same file corresponding to the same page node. Each functional node to be tested corresponds to real-time tracking data, page display information of the interactive interface, and interface information of the object under test. Here, the interactive interface refers to the interactive interface of the object under test, not the interactive interface of the test system. As an example, it can be as follows... Figure 4 As shown, assuming the tester selects the "Loan_Calculation Page_Display" node as the function to be tested, the tester can obtain the display and operation corresponding to that function node.

[0033] Furthermore, the target information corresponding to the functional node under test is standardized. In some possible embodiments, the target information can be standardized through the following steps: The target information is standardized according to a unified data format and data unit to generate standardized target information. The information in the standardized target information is integrated to generate the closed-loop chain data of the interface corresponding to each operation page of the user operation; The step of generating a test case file for the object under test based on the data obtained from the standardization process includes: Based on the closed-loop chain data of the interfaces corresponding to each operation page, generate test case files for each operation page of the object under test.

[0034] In this application, the standardization process for the target information includes: converting the data into the same data format and data units according to a unified data format and units, and then transmitting the standardized data through a method such as... Figure 5 The interactive interface shown is presented to testers. Among other things, it can be seen that... Figure 5 As shown, the target information includes real-time tracking data (corresponding to the operation type "page show" in the diagram), page display information, and interface information of the object under test (corresponding to the interface call in the diagram), as well as terminal capability information and front-end caching information, and parameter extraction.

[0035] In this application, the interface information of the object under test is a general term for the interfaces of the application. The interface information of the object under test included in the target information mainly refers to the backend data interface information corresponding to the page elements operated by the user in the real-time tracking data. Here, "end capability" can be understood as the permission level corresponding to the user's client. Different users have different permission levels, and the corresponding end capabilities are also different. Front-end caching refers to the content of previously operated interface information cached in the cache path. For example, if a user previously opened and closed page A, and then opened page A again, some cached data from page A will be cached in the specified path.

[0036] As one implementation method, each type of real-time tracking data can be assigned a clear and unique business semantic according to a preset set of standardized fields, avoiding inconsistencies in field names and meanings across different scenarios. When standardizing target data associated with the functional node under test, information conforming to the preset standardized fields can be extracted. For example, user operation events can be obtained by extracting the EventID field associated with the functional node under test, user-generated sessions can be obtained by extracting the SessionID field, and the user's login client IP address can be obtained by extracting the clientIP, etc.

[0037] Furthermore, the standardized target information is integrated, specifically according to the following three dimensions: Interface information integration: The interface information involved in the test cases is integrated into the interface information. Specifically, the calling method, parameter requirements, and expected return results of the application's interfaces are integrated into the interface information statistical unit, thereby providing underlying support for the interface interaction part involved in the subsequent generation of test cases.

[0038] Page display information integration: The page element information involved in the test cases is integrated into the page display information. Specifically, the position, style, display rules, and corresponding interfaces of the application's page elements are integrated into the page display information statistical unit, providing underlying support for the subsequent generation of test cases to accurately identify and operate page elements.

[0039] User operation information integration: The collected routine user operations are integrated, and abnormal operation data generated by users are removed during the process. The flow, frequency and sequence of user operations are analyzed to obtain the shortest path of user operation as a typical user operation path. The shortest path of user operation is then determined as the closed-loop chain data of the interface corresponding to the operation page of the user operation.

[0040] For example, it can be as follows Figure 5 As shown, the contents of fields such as eventKey, selector, className, and type involved in the operation type are integrated into a preset user operation information field table to obtain integrated user operation information, which also belongs to the integrated target information. Other integration methods for target details such as interface calls, terminal capabilities, front-end caching, and parameter extraction are similar and will not be elaborated here.

[0041] Further execution step S13 involves generating test case files for each operation page of the object under test based on the integrated interface information, page display information, and user operation information corresponding to the interface closed-loop chain data. Specifically, in some possible embodiments, execution step S13 can be implemented through the following steps: Based on the data obtained from the standardization process, prototype data for test cases is generated, wherein the prototype data is the original basis and foundational material upon which the test cases depend. Determine the basic structure of the test cases, wherein the basic structure includes the fixed fields and logical framework that the test cases depend on; The prototype data is populated into the basic structure to generate the test case file.

[0042] Among them, the prototype data of test cases serves as the original basis and foundation for generating test cases, specifically including: prototype data of UI automation test cases, which is further subdivided into global variables of test cases (such as...). Figure 6Global variables in the case statements and global variables in the operation steps (e.g.) Figure 6 The global variable for operation steps (in the context of `step`). This global variable is further subdivided into Data, UI elements, Request, extracted parameters, and front-end cache.

[0043] The basic structure of test cases is designed by testers and can be visualized as follows: Figure 6 The data structure shown has logical relationships between the data items. The generated prototype data is then processed according to the following... Figure 6 Fill the corresponding fields with the pre-defined basic structure shown to obtain the corresponding test case file.

[0044] In some possible embodiments, the method further includes: The test case file is distributed to the test environment and executed to obtain the test results, which include: test pass rate and number of covered scenarios. Based on the test results, generate test case evaluation values, output and display the test case evaluation values.

[0045] In some possible embodiments, executing the test case file includes: Based on the page display information included in the test case file, generate test content for the corresponding page display logic, and verify whether the page element display results in the test page corresponding to the page display information meet the expected page element display results based on the test content of the page display logic. Based on the user operation information included in the test case file, test content corresponding to the user operation logic is generated. Based on the test content of the user operation logic, the user operation in the user operation information is simulated, the corresponding operation response result is obtained, and it is determined whether the response result meets the expected operation response result.

[0046] In this application, the logic corresponding to the test cases can be generated by the data factory in the test case management unit of the testing system. Specifically, the data factory can generate the following two aspects of logic: Page display logic generation: Based on the page display information included in the prototype data, generate test content related to the page display logic in the test cases, and verify whether the display of page elements meets the expected effect. Specifically, it can determine whether page elements are displayed correctly and whether the display style is accurate, etc.

[0047] User operation logic generation: Specifically generate user operation steps and simulate various user operation behaviors, such as clicking, inputting, etc. according to the extracted typical user path, in order to test whether the application responds normally under user operation.

[0048] As an example, such as Figures 6-9 As shown, the test cases can test the target information contained in the test cases, obtain the corresponding actual results, compare them with the expected results, calculate the test pass rate and the number of covered scenarios based on the comparison results, and finally output the corresponding test pass rate and the number of covered scenarios.

[0049] In this way, it is possible to generate UI automation test cases using online user data, achieving a deep integration of user-driven and data-driven UI automation testing, which significantly improves testing efficiency, scenario coverage and the fit with actual business.

[0050] Based on the method provided in the first aspect, in the second aspect, this application provides a system for generating test cases based on embedded data, wherein, as... Figure 10 As shown, the system includes: The interaction unit is used to obtain real-time tracking data associated with the user identity information based on the user identity information; wherein, the real-time tracking data is: real-time operation data generated by the user on the interactive interface of the object to be tested; The data processing unit is used to respond to the test node selected by the tester, acquire target information associated with the test node, and perform standardized processing on the target information; the target information includes at least: the real-time data points, the page display information of the interactive interface of the test object, and the interface information of the test object; The test case management unit is used to generate test case files for the object under test based on the data obtained from the standardization process.

[0051] The interaction unit executes step S11 above, assembling query information based on online user IDs to obtain real-time user operation information associated with those IDs. It then aggregates user operation paths based on this information, allowing testers to select appropriate path nodes. The data processing unit responds to the selected path node by querying information to obtain interface information, page display information, user operation information, endpoint capability information, and frontend cache. It then extracts and standardizes the acquired information to obtain standardized target information, which is output to the test case management unit. This unit generates raw test case data (prototype data), which is then processed by the data factory to generate page display steps and user operation steps. This process generates corresponding test cases, reducing the cost of automated test case writing and improving testing efficiency.

[0052] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in this application comply with relevant laws and regulations and do not violate public order and good morals.

[0053] The names of the messages or information exchanged between multiple devices in the embodiments of this application are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0054] Thirdly, exemplary embodiments of this application also provide an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the electronic device to perform a method according to an embodiment of this application.

[0055] An exemplary embodiment of this application also provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a computer's processor, is used to cause the computer to perform a method according to an embodiment of this application.

[0056] An exemplary embodiment of this application also provides a computer program product, including a computer program, wherein, when executed by a computer's processor, the computer program is used to cause the computer to perform a method according to an embodiment of this application.

[0057] refer to Figure 11 The following is a structural block diagram of an electronic device 110 that can serve as a server or client of this application, which is an example of a hardware device that can be applied to various aspects of this application. The electronic device is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the application described and / or claimed herein.

[0058] like Figure 11As shown, the electronic device 110 includes a computing unit 111, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM 112) or a computer program loaded from a storage unit 118 into a random access memory (RAM 113). The RAM 113 may also store various programs and data required for the operation of the electronic device 110. The computing unit 111, ROM 112, and RAM 113 are interconnected via a bus 114. An input / output interface (I / O interface 115) is also connected to the bus 114.

[0059] Multiple components in electronic device 110 are connected to I / O interface 115, including: input unit 116, output unit 117, storage unit 118, and communication unit 119. Input unit 116 can be any type of device capable of inputting information to electronic device 110. Input unit 116 can receive input digital or character information and generate key signal inputs related to user settings and / or function control of the electronic device. Output unit 117 can be any type of device capable of presenting information and may include, but is not limited to, a display, speaker, video / audio output terminal, vibrator, and / or printer. Storage unit 118 may include, but is not limited to, disks and optical discs. Communication unit 119 allows electronic device 110 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers, and / or chipsets, such as Bluetooth™ devices, WiFi devices, WiMax devices, cellular communication devices, and / or the like.

[0060] The computing unit 111 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 111 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 111 performs the various methods and processes described above. For example, in some embodiments, the aforementioned method for generating test cases based on embedded data can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 118. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 110 via ROM 112 and / or communication unit 119. In some embodiments, the computing unit 111 can be configured by any other suitable means (e.g., by means of firmware) to perform the aforementioned method for generating test cases based on embedded data.

[0061] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0062] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0063] As used in this application, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and / or apparatus (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0064] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0065] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0066] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other.

Claims

1. A method for generating test cases based on embedded data, characterized in that, The method includes: Real-time tracking data associated with user identity information is obtained based on user identity information; wherein, the real-time tracking data is: real-time operation data generated by the user on the interactive interface of the object to be tested; In response to the functional node to be tested selected by the tester, target information associated with the functional node to be tested is obtained and the target information is standardized; the target information includes at least: the real-time data points, the page display information of the interactive interface of the object under test, and the interface information of the object under test; Based on the data obtained from the standardization process, a test case file for the object under test is generated.

2. The method according to claim 1, characterized in that, After the step of obtaining real-time tracking data associated with the user identity information based on the user identity information, the method further includes: Based on the user identity information, all data associated with the user identity information are obtained and assembled according to a preset assembly rule to generate user operation path information; The step of responding to a test node selected by the tester, acquiring target information associated with the test node, and standardizing the target information includes: In response to the functional node to be tested, the target user operation path information associated with the functional node is obtained, and the target user operation path information is standardized.

3. The method according to claim 2, characterized in that, The assembly according to the preset assembly rules includes: Based on the timestamps and business types carried by all data associated with the user identity information, the data belonging to the same business type are arranged and assembled in chronological order according to the timestamps to obtain the user operation path information.

4. The method according to claim 1, characterized in that, The target information also includes: terminal capability information and front-end cache information, and the standardization processing of the target information includes: The target information is standardized according to a unified data format and data unit to generate standardized target information. The information in the standardized target information is integrated to generate the closed-loop chain data of the interface corresponding to each operation page of the user operation; The step of generating a test case file for the object under test based on the data obtained from the standardization process includes: Based on the closed-loop chain data of the interfaces corresponding to each operation page, generate test case files for each operation page of the object under test.

5. The method according to claim 1, characterized in that, The step of generating a test case file for the object under test based on the data obtained from the standardization process includes: Based on the data obtained from the standardization process, prototype data for test cases is generated, wherein the prototype data is the original basis and foundational material upon which the test cases depend. Determine the basic structure of the test cases, wherein the basic structure includes the fixed fields and logical framework that the test cases depend on; The prototype data is populated into the basic structure to generate the test case file.

6. The method according to claim 1, characterized in that, The method further includes: The test case file is distributed to the test environment and executed to obtain the test results, which include: test pass rate and number of covered scenarios. Based on the test results, generate test case evaluation values, output and display the test case evaluation values.

7. The method according to claim 6, characterized in that, The execution of the test case file includes: Based on the page display information included in the test case file, generate test content for the corresponding page display logic, and verify whether the page element display results in the test page corresponding to the page display information meet the expected page element display results based on the test content of the page display logic. Based on the user operation information included in the test case file, test content corresponding to the user operation logic is generated. Based on the test content of the user operation logic, the user operation in the user operation information is simulated, the corresponding operation response result is obtained, and it is determined whether the response result meets the expected operation response result.

8. A system for generating test cases based on embedded data, characterized in that, The system includes: an interaction unit, a data processing unit, and a test case management unit, wherein: The interaction unit is used to obtain real-time tracking data associated with the user identity information based on the user identity information; wherein, the real-time tracking data is: real-time operation data generated by the user on the interactive interface of the object to be tested; The data processing unit is used to respond to the test node selected by the tester, acquire target information associated with the test node, and perform standardized processing on the target information; the target information includes at least: the real-time data points, the page display information of the interactive interface of the test object, and the interface information of the test object; The test case management unit is used to generate test case files for the object under test based on the data obtained from the standardization process.

9. An electronic device, characterized in that, The electronic device includes: a processor and a memory storing a program; wherein the program includes instructions that, when executed by the processor, cause the processor to perform the method according to any one of claims 1-7.

10. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-7.

Images