CN113656283A - Project testing method and device, electronic equipment and computer readable storage medium - Google Patents
Project testing method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN113656283A CN113656283A CN202110814117.3A CN202110814117A CN113656283A CN 113656283 A CN113656283 A CN 113656283A CN 202110814117 A CN202110814117 A CN 202110814117A CN 113656283 A CN113656283 A CN 113656283A
- Authority
- CN
- China
- Prior art keywords
- test
- task
- tasks
- project
- trigger
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Abstract
The embodiment of the application provides a project testing method and device, electronic equipment and a computer readable storage medium, and relates to the technical field of computers. The method comprises the following steps: the method comprises the steps of obtaining at least two test tasks of a target project, wherein the at least two test tasks correspond to different test platforms, linking test trigger inlets of the at least two test tasks to obtain a test case assembly line and a corresponding total trigger inlet, and triggering the total trigger inlet when a test trigger condition is met, executing the test tasks in the test case assembly line, and obtaining a current test result corresponding to the test tasks. Therefore, the flow of multi-platform testing is simplified, and the project testing efficiency is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a project testing method and apparatus, an electronic device, and a computer-readable storage medium.
Background
When the application project is developed, the project can be tested on a plurality of platforms, the actual operation effect and performance of the project can be effectively evaluated, whether a coping scheme aiming at various faults is feasible or not is detected, and the various performances of the project can be further optimized.
At present, when a project needs to be tested on a plurality of platforms, a test task corresponding to each platform generally needs to be triggered respectively, and parameter setting is performed on each test task respectively, so that the test efficiency is low.
Disclosure of Invention
The purpose of the present application is to solve at least one of the above technical drawbacks, in particular, the technical drawback of inefficient project testing.
In a first aspect, a project testing method is provided, which includes:
acquiring at least two test tasks of a target project, wherein the at least two test tasks correspond to different test platforms;
linking the test trigger entries of at least two test tasks to obtain a test case pipeline and a corresponding total trigger entry;
and responding to the test triggering condition meeting the target project, triggering the total triggering inlet, executing the test task in the test case assembly line, and obtaining the current test result corresponding to the test task.
In an optional embodiment of the first aspect, further comprising:
receiving the setting operation of a user for the test parameters in each test task through a test parameter setting interface;
and storing the test parameters corresponding to the test parameter setting operation and the tasks corresponding to the test parameter setting operation in an associated manner.
In an optional embodiment of the first aspect, receiving, through the test parameter setting interface, a setting operation of a user for a test parameter in each test task includes:
responding to the triggering of the total triggering entrance, and displaying prompt information, wherein the prompt information is used for prompting whether to set the testing parameters;
responding to the test parameter setting confirmation operation of a user, and displaying a test parameter setting interface;
and receiving the setting operation of the user aiming at the test parameters in each test task through the test parameter setting interface.
In an optional embodiment of the first aspect, the meeting of the test trigger condition comprises at least one of:
receiving a test trigger instruction aiming at a target item;
receiving a test code packet of a target project;
reaching the appointed time;
the time length from the last time the total trigger entrance is triggered is equal to the set time interval.
In an alternative embodiment of the first aspect, executing the test tasks in the testcase pipeline comprises:
and if the selection operation aiming at the test task in the test case pipeline is received before the test task in the test case pipeline is executed, executing the test task corresponding to the selection operation.
In an optional embodiment of the first aspect, for each test task performed, the method further comprises:
acquiring a standard test result corresponding to the test task;
after obtaining the current test result corresponding to the test task, the method further comprises the following steps:
and for each test task, generating a comparison result between the current test result and the standard test result based on the current test result and the standard test result corresponding to the test task.
In an optional embodiment of the first aspect, after obtaining the current test result corresponding to the test task, the method further includes:
sending test related information, wherein the test related information comprises at least one of the following:
and testing the current test result, the standard test result, the comparison result, the test report and the test log corresponding to the task.
In a second aspect, there is provided an apparatus for project testing, the apparatus comprising:
the task acquisition module is used for acquiring at least two test tasks of the target project, wherein the at least two test tasks correspond to different test platforms;
the link module is used for linking the test trigger entries of at least two test tasks to obtain a test case assembly line and a corresponding total trigger entry;
and the test module is used for responding to the test trigger condition meeting the target project, triggering the total trigger inlet, executing the test task in the test case assembly line and obtaining the current test result corresponding to the test task.
In an optional embodiment of the second aspect, the system further includes a parameter setting module, specifically configured to:
receiving the setting operation of a user for the test parameters in each test task through a test parameter setting interface;
and storing the test parameters corresponding to the test parameter setting operation and the tasks corresponding to the test parameter setting operation in an associated manner.
In an optional embodiment of the second aspect, when receiving, through the test parameter setting interface, a setting operation of a user for a test parameter in each test task, the parameter setting module is specifically configured to:
responding to the triggering of the total triggering entrance, and displaying prompt information, wherein the prompt information is used for prompting whether to set the testing parameters;
responding to the test parameter setting confirmation operation of a user, and displaying a test parameter setting interface;
and receiving the setting operation of the user aiming at the test parameters in each test task through the test parameter setting interface.
In an alternative embodiment of the second aspect, the meeting of the test trigger condition comprises at least one of:
receiving a test trigger instruction aiming at a target item;
receiving a test code packet of a target project;
reaching the appointed time;
the time length from the last time the total trigger entrance is triggered is equal to the set time interval.
In an optional embodiment of the second aspect, when the test module executes the test task in the test case pipeline, the test module is specifically configured to:
and if the selection operation aiming at the test task in the test case pipeline is received before the test task in the test case pipeline is executed, executing the test task corresponding to the selection operation.
In an optional embodiment of the second aspect, for each executed test task, the system further includes a comparison module, specifically configured to:
acquiring a standard test result corresponding to the test task;
after obtaining the current test result corresponding to the test task, the method further comprises the following steps:
and for each test task, generating a comparison result between the current test result and the standard test result based on the current test result and the standard test result corresponding to the test task.
In an optional embodiment of the second aspect, the apparatus further includes a sending module, specifically configured to:
sending test related information, wherein the test related information comprises at least one of the following:
and testing the current test result, the standard test result, the comparison result, the test report and the test log corresponding to the task.
In a third aspect, an electronic device is provided, which includes:
the system comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the project testing method of any one of the embodiments.
In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the method of project testing of any of the above embodiments.
In a fifth aspect, a computer program product or computer program is provided, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device implements the method provided in the first aspect embodiment or the second aspect embodiment when executed.
The project testing method comprises the steps of obtaining a plurality of testing tasks of a project to be tested, wherein the testing tasks are used for testing on different testing platforms, linking the testing trigger inlets of the testing tasks together to obtain a testing case assembly line and a corresponding total trigger inlet, triggering the total trigger inlet when the testing trigger conditions are met, executing the testing tasks in the testing case assembly line, and then sending a testing result corresponding to the testing tasks. By triggering the total triggering entry, a plurality of testing tasks tested on different platforms are uniformly triggered, the flow of multi-platform testing is simplified, and the project testing efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic flowchart of a project testing method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a pipeline in a project testing method according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram illustrating stages of a pipeline in a project testing method according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart of a project testing method according to an embodiment of the present application;
FIG. 5 is a schematic structural diagram of a project testing apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an electronic device for project testing according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
At present, the entertainment content related to electronic products is increasing, and the vigorously developing network application market attracts the attention of countless manufacturers. The stable operation of multiple platforms is undoubtedly the decisive advantage of an application product, and the stable operation of multiple platforms has no departure from the mass test of the application product on multiple platforms. For the multi-platform test requirements, parameters are generally required to be set for each test task independently, and the test tasks corresponding to each platform are triggered respectively, so that the test process is complicated, and the test efficiency is low.
The application provides a project testing method, a project testing device, an electronic device and a computer-readable storage medium, which aim to solve at least one technical problem in the prior art.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
The project testing method provided by the embodiment of the application can be applied to a server and can also be applied to a terminal.
Those skilled in the art will understand that the "terminal" used herein may be a Personal computer, a Mobile phone, a tablet computer, a PDA (Personal Digital Assistant), an MID (Mobile Internet Device), etc.; a "server" may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.
An embodiment of the present application provides a method for testing a project, for example, where the method is applied to a terminal, and as shown in fig. 1, the method includes:
step S101, at least two test tasks of a target project are obtained, and the at least two test tasks correspond to different test platforms.
In the embodiment of the present application, a to-be-tested item may refer to an item that needs to be tested on each testing platform, that is, an application that needs to be tested, for example, a certain research and development project group needs to develop a game software, the game software needs to test each function of the game software before online, the game software may be understood as the to-be-tested item, a task created to complete testing of each function of the game software is a testing task, and in order to meet actual application requirements, task creation needs to be performed for different testing platforms, so as to determine whether functions of different platform testing software meet requirements.
The test platform is a platform which needs a test function, a software environment and a hardware environment, and can include a World Wide Web (World Wide Web) platform, a native platform and various common application platforms for manufacturers.
The native platform may include Android, iOS, Mac, Windows, and the like, and the various small game platforms may refer to games and software platforms developed and designed by various operators.
For example, a game item to be tested on a PC (Personal Computer) side may be tested on a steam platform, and a game item to be tested on a mobile side may be tested on a game platform developed by each mobile side manufacturer.
The tasks to be tested for the project to be tested may include at least two testing tasks corresponding to different testing platforms, which may include, but are not limited to, the following:
(1) one test task may correspond to a plurality of test platforms. Specifically, if a plurality of test platforms receive test tasks in the same format and the content of the test performed on each platform according to the project requirements is the same, a test task meeting the format requirement can be obtained and tested on each test platform;
(2) each test task may correspond to a different test platform. Specifically, because each test platform receives test tasks in different formats, the content of tests performed on different platforms is different, and each test task can correspond to different test platforms;
(3) according to the specific requirements of the project, the situation that part of the test tasks correspond to different test platforms and the situation that part of the test tasks correspond to the same test platform can exist.
In the embodiment of the application, a plurality of platforms to be tested can be determined according to the project testing requirements, and at least two testing tasks corresponding to the plurality of testing platforms are obtained.
And S102, linking the test trigger entries of at least two test tasks to obtain a test case pipeline and a corresponding total trigger entry.
In the embodiment of the application, the test trigger entries of at least two test tasks are linked together to generate a test case pipeline and a corresponding total trigger entry. The test case assembly line comprises a plurality of test tasks which are linked together, and the total trigger inlet is triggered to uniformly execute the plurality of test tasks in the test case assembly line, so that each test task does not need to be triggered, and the efficiency of project testing is improved.
The test trigger entry may be an Application Program Interface (API) for triggering a corresponding test task, the test trigger entries of at least two test tasks are linked to obtain a test case pipeline and a corresponding total trigger entry, the total trigger entry may be an Application program Interface for triggering a corresponding test case pipeline, and a plurality of test tasks in the test case pipeline may be triggered uniformly through the total trigger entry.
In the embodiment of the application, the test trigger entries of at least two test tasks may be linked together by the test plug-in to obtain the total trigger entry. The test plug-in or the software can be a matched test application program developed by a developer according to project requirements, can realize the function of linking the test trigger entries of a plurality of test tasks together, is convenient for uniformly triggering the plurality of test tasks to test on different platforms, and can further comprise a plurality of auxiliary functions, such as displaying a visual configuration interface, automatically acquiring test packets required by the test, providing a plurality of trigger modes for a user to select, and the like.
In the embodiment of the application, the trigger entries of at least two test tasks can be linked together to obtain a test case pipeline and a corresponding total trigger entry. Among them, pipeline (pipeline) may refer to: groups of events or jobs that may be executed that are linked together in sequence.
The application does not limit which plug-in is used to connect at least two test tasks. In some embodiments, Jenkins pipeline plug-ins, an open source tool for building a continuous integration and continuous delivery (CI/CD) pipeline, can be used that can provide an integration solution for interfaces to other applications, software libraries, build tools, etc., that can perform and automate tasks.
The Jenkins pipeline can declare the pipeline structure in two grammars, one declarative and one scripting. The scripted grammar is less restrictive and provides richer grammatical features than the declarative grammar, and in some embodiments of the present application, the scripted grammar may be used, or a combination of the declarative grammar and the scripted grammar may be used, thereby providing more flexibility in designing and configuring the pipeline.
Further, a series of stages of the pipeline may be configured to facilitate understanding and designing the pipeline in compliance with project testing requirements, wherein a pipeline may be logically divided into a number of stages (stages), each stage representing a set of operations. Step (step) is the most basic unit of operation, indicating that the pipeline is specifically to execute the task, and the step may be defined within a stage, as shown in fig. 2, and may include multiple steps under each stage. In this embodiment, each stage in the pipeline may correspond to each test task to be executed, and the step indicates the content of each test task to be tested.
In one example, the execution state of the pipeline may be transparently, visually exposed to the user through various stages in the pipeline via plug-ins, such as with a Stage View plug-in. As shown in fig. 3, a pipeline "# 1" may be constructed, with the date and time of pipeline setup on the left side of the phase view interface and the execution time of the three phases on the right side of the phase attempt interface, where "phase 1: preparing an application library address which can be used for filling an interface test project and acquiring authentication information required by a test case; "stage 2: building' shell (command line) script which can be used for filling and executing interface test; "stage 3: and the result can be used for publishing the generated test report and filing after the interface test execution is completed.
In the embodiment of the application, a developer can write a commonly-used Jenkins pipeline task template or obtain the task template from an open-source program library. The pipeline script fragments can be compiled based on the acquired task template, and simultaneously, variables which can be automatically acquired and exported in the task template and parameters required by the execution of the script fragments can be specified. Further, the research and development can adjust the task templates according to the requirements, arrange and combine the adjusted task templates to obtain the production line template, and in addition, the production line template can also be directly obtained from an open-source program library. When the assembly line needs to be constructed, research personnel can obtain an initial assembly line close to the project requirement from the assembly line template, and a target assembly line meeting the project testing requirement is obtained by adjusting the initial assembly line.
And step S103, responding to the test triggering condition meeting the target project, triggering the total triggering inlet, executing the test task in the test case assembly line, and obtaining the current test result corresponding to the test task.
In this embodiment of the present application, a test trigger condition may be preset, and when the preset test trigger condition is met, the master trigger entry is automatically triggered to execute a test task in the test flow case, specifically, when the test task is executed, the corresponding test task is executed on the test platform corresponding to each executed test task. The test trigger condition may be configured according to an actual test requirement, and the embodiment of the present application is not limited.
In alternative embodiments, meeting the test trigger condition may include at least one of: receiving a test trigger instruction aiming at a target item; receiving a test code packet of a target project; reaching the appointed time; the time length from the last time the total trigger entrance is triggered is equal to the set time interval.
The test trigger instruction may be issued by a user or automatically issued after the upstream system is completed, and the upstream system may be a project packaging system, and the test may not be performed immediately after receiving a package for performing a test, but the total trigger entry is triggered after waiting for receiving the test trigger instruction.
The test code package of the target project may be directly obtained from a preset test database, or may be obtained by an upstream system, for example, after the project packaging system is packaged, specifically, the test code package may include an installation package of the project to be tested, description information of the project to be tested, a resource package of the project to be tested, a test case, a test framework, and the like, a corresponding relationship may exist between the test code package and the test task, and data information in the test code package is used for executing the test task on a corresponding test platform. The installation package of the items to be tested can be used for installing the items to be tested on the corresponding platforms; the description information of the project to be tested can comprise name information, version information, path information, operating system information, engine information and the like of the project to be tested; the test case can be used for specifying a specific test operation event, namely test content aiming at the item to be tested, which needs to be completed in the test; the test framework may include test script commands that match the items to be tested for describing and controlling the test flow.
The total trigger entry of the testcase pipeline may be triggered when a specified time arrives, or when a time period from the last time the total trigger entry was triggered equals a set time interval. The specified time may refer to a preset time point, for example, a total trigger entry of an automatic trigger test case pipeline at 7 am may be set, and a test task in the test case pipeline is executed; or triggering the total trigger entry of the test case pipeline at preset time intervals, for example, triggering the total trigger entry once every 8 hours, so as to implement multiple tests and record test results.
Specifically, when the testcase pipeline is not updated, the total trigger entry is not changed, and multiple triggers may be performed on the same total trigger entry, for example, when the time length from the last time the total trigger entry was triggered is equal to the set time interval, the total trigger entry is triggered. If the test case pipeline is updated, the test content changes, and the updated total trigger entry is obtained, the updated total trigger entry can be triggered when the time length from the last time the total trigger entry before updating is triggered is equal to the set time interval.
In one embodiment, several of the above triggering manners may be used in combination, and priority is set between the various triggering manners. Specifically, an immediate test option corresponding to the test trigger condition of "receiving a test code packet of a target item" may be set first, when the immediate test option is checked, the rest of the test trigger conditions are ignored, and when the test code packet of the target item is received, the total trigger entry is triggered immediately to enter the test flow. When the immediate test option is not checked, setting the test trigger condition of "receiving the test code packet of the target item" to be in a failure state, and satisfying any one of the following test trigger conditions, namely triggering the total trigger entry: the method comprises the following steps that a test trigger instruction is received under the condition one; the second condition is that the time length from the specified time or the last time that the total trigger entrance is triggered is equal to the set time interval, wherein the priority of the first condition is higher than that of the second condition, and if the test trigger instruction is not received, the total trigger entrance is triggered at the specified time or at every preset time interval; and if a test trigger instruction is received, immediately triggering a total trigger inlet to enter a test flow.
In the embodiment of the present application, the test result corresponding to the test task may refer to test data obtained by a single test, or may refer to an analyzed test result obtained after comparing with a standard test result or a historical test result.
In the above embodiment, at least two test tasks corresponding to different platforms in the item to be tested are obtained first, the test trigger entries of the at least two test tasks are linked together to obtain the test case pipeline and the corresponding total trigger entry, when the test trigger condition is met, the total trigger entry is triggered, the test tasks in the test case pipeline are executed, and the corresponding test result is sent to the specified electronic device. The trigger entries corresponding to the test tasks of different test platforms are linked together through the production line, so that a plurality of test tasks are uniformly triggered through the total trigger entry, the flow of multi-platform test is simplified, and the project test efficiency is improved.
In the embodiment of the application, the setting operation of the user for the test parameters in each test task can be received through the test parameter setting interface, and the test parameters corresponding to the test parameter setting operation and the tasks corresponding to the test parameter setting operation are stored in an associated manner.
The setting options specifically included in the parameter setting interface are not limited in the present application, and the test parameter setting operation includes, but is not limited to: inputting a numerical value which accords with a preset range, checking options, adjusting the numerical value by dragging a button and the like.
In some embodiments, the parameter setting interface may include a sub-interface for each test task, and the parameter of each test task may be set through the sub-interface in detail, and further, by setting test parameters corresponding to different test tasks of different test platforms, test content may be enriched, and problems that may occur when the project runs on different platforms may be detected more comprehensively, so as to optimize the project. In addition, the parameter setting interface can also comprise a total parameter setting interface, and parameters are uniformly transmitted to the test task by setting the parameters on the total parameter setting interface, so that the project test efficiency is improved.
In other embodiments, the parameter setting interface may provide an interface option for each test task, where the interface option may be used to select a test task to be executed in the test from the test case pipeline, and when the total trigger entry of the test case pipeline is triggered, only the selected test task may be executed. When the user does not check the interface option, the general trigger entry can be triggered by default, and all test tasks are executed.
In the embodiment of the application, the visual parameter setting panel is used for setting the parameters of the test task, so that the unified setting can be selected, the setting can be respectively carried out, the parameter setting scheme is flexible, the technical effect of conveniently configuring the test parameters is realized, and the project testing efficiency is improved.
In one example, when the test parameter setting interface is a visual parameter setting interface in a Jenkins pipeline, the parameter setting interface may include a parameter setting sub-interface of each test task, and parameters to be transmitted by each test task may be set carefully through the sub-interfaces, or may include a total parameter setting interface, and by setting parameters on the total parameter setting interface, the parameters are uniformly transmitted to the test tasks, so that the project test efficiency is improved.
And when the total trigger inlet is triggered, transmitting parameters customized by a parameter setting interface to each test task in the Jenkins assembly line, and covering default parameters of the test tasks. In the subsequent test flow, the method for modifying the parameter of any test task may include: and transmitting the modified parameters through the script and modifying the parameters through a parameter setting interface corresponding to the test task.
In this embodiment of the present application, receiving, through a test parameter setting interface, a setting operation of a user for a test parameter in each test task may include the following steps: responding to the triggering of the total triggering entrance, and displaying prompt information, wherein the prompt information is used for prompting whether to set the testing parameters; responding to the test parameter setting confirmation operation of a user, and displaying a test parameter setting interface; and receiving the setting operation of the user aiming at the test parameters in each test task through the test parameter setting interface.
Specifically, when the total trigger entry is triggered, a preset prompt message may be displayed before the test task in the test case pipeline is executed, and the prompt message may be used to prompt the user to select whether the test parameter needs to be set. Furthermore, if the user performs the parameter setting confirmation operation, a test parameter setting interface can be displayed, and the user sets the test parameters of each test task through the test parameter setting interface; if the user chooses not to set the parameters, the preset default parameters can be used when the test task is executed.
In the embodiment of the present application, if a selection operation for a test task in a test case pipeline is received before the test task in the test case pipeline is executed, a test task corresponding to the selection operation may be executed.
The generation manner of the selection operation is not limited in the present application.
In an optional embodiment, a preset selection prompt message may be skipped before the test task is executed, the selection prompt message is used to prompt a user whether to select a preset number of test tasks from the test case pipeline, if so, the user jumps to a preset test task selection panel or an interface selection area of the test tasks on the parameter setting panel, so that the user can select the test tasks to be executed conveniently, and if not, all the test tasks are executed by default.
In other optional embodiments, a developer may write a corresponding test task selection panel according to a project requirement, the test task selection panel may visualize a test task of a project to be tested, and the test task to be executed may be selected from the test case pipeline through the test task selection panel.
In the embodiment of the present application, if selection information for a test task is not received, all test tasks may be executed after triggering the total trigger entry by default, or a test may be executed according to a preset configuration test policy, for example, a preset number of test tasks are tested in one test flow.
By selecting a certain number of test tasks from the test case assembly line to execute, a certain performance of the item to be tested can be tested more pertinently, and the test efficiency is improved.
In an embodiment of the present application, for each test task performed, the method may further include: acquiring a standard test result corresponding to the test task; after obtaining the current test result corresponding to the test task, the method further comprises the following steps: and for each test task, generating a comparison result between the current test result and the standard test result based on the current test result and the standard test result corresponding to the test task.
The standard test result may refer to an expected result of the test task, and the closer the current test result of each test task is to the standard test result, the better the test effect of the test task is, and the closer the test effect of a part of modules in a project corresponding to the test task is to the expected result. The current test result and the standard test result corresponding to the test task can be compared, and a comparison result between the current test result and the standard test result is generated and used for describing the test effect of the test task.
In some embodiments, the test results may be in the form of a picture. For each executed test task, the current test result may include a current test result picture, the standard test result may include a standard test result picture, and the comparison result between the current test result and the standard test result may be a difference picture generated based on a difference between the current test result picture and the standard test result picture, the difference picture for clearly displaying a difference between the current test result and the standard test result. The test result analysis picture can be further generated based on the current test result picture, the standard test result picture and the difference picture, and is used for conveniently evaluating the test effect of the project.
In this embodiment of the present application, after obtaining the current test result corresponding to the test task, the method may further include: sending test related information, wherein the test related information comprises at least one of the following: and testing the current test result, the standard test result, the comparison result, the test report and the test log corresponding to the task.
The test related information may be sent to a designated server for storage, or may be automatically sent to a terminal of a project related person in the form of an email after obtaining the test related information corresponding to the test task through an email plug-in, or may be sent in other manners, such as a prompt message, and the like, which is not limited in the present application.
The current test result may be a test result corresponding to the test task obtained in the current test process, the standard test result may be an expected test result corresponding to the test task, and the comparison result may be generated based on a difference between the current test result and the standard test result.
The test report may be automatically analyzed and generated according to a preset test effect evaluation standard, for example, if the similarity of the comparison result between the current test result and the standard test result corresponding to a certain test task reaches 90%, the test report is marked with "excellent"; if the similarity of the comparison result is between 70% and 90%, marking 'good' on the test report; if the similarity of the comparison result is between 60 and 70 percent, marking the test report to reach the standard; and if the similarity of the comparison result is less than 60%, marking the test report as 'not meeting the standard'. Specifically, when the test result is in the form of a picture, a corresponding test report may be automatically generated based on a difference picture generated according to a difference between the current test result picture and the standard test result picture.
The test log may be a record of a test process of a single test for a single test task, for example, record time consumption of the single test task in different test links, or record a test result of the test task within a period of time, for example, record a test result for a certain test task within ten days, and analyze what kind of change trend occurs in the test result of the test task within the ten days, so as to further optimize a project to be tested.
In some embodiments, when the test related information corresponding to the test task is obtained, the test related information may be archived, which facilitates the user to review the historical test results by searching.
In one embodiment, the present application provides a project testing method, as shown in FIG. 4, comprising the following steps.
Step S401, at least two test tasks of a target project are obtained, wherein the at least two test tasks correspond to different test platforms; one test task may correspond to a plurality of test platforms, each test task may correspond to a different test platform, or according to the specific requirements of the project, a case where a part of the test tasks correspond to a plurality of test platforms and a case where a part of the test tasks correspond to the same test platform may exist.
Step S402, linking the test trigger entries of at least two test tasks to obtain a test case pipeline and a corresponding total trigger entry; wherein, can link the test trigger entry of two at least test tasks through Jenkins pipeline plug-in components, it is concrete, can use the script formula grammar in the Jenkins pipeline.
Step S403, responding to the test triggering condition meeting the target item, and triggering a total triggering inlet; the test trigger condition being met includes at least one of: receiving a test trigger instruction aiming at a target item; receiving a test code packet of a target project; the time length from the specified time to the last time the total trigger entrance is triggered is equal to the set time interval.
Step S404, judging whether the selection operation aiming at the test task in the test case pipeline is received, if so, entering step S409, otherwise, entering step S405.
Step S405, displaying prompt information, wherein the prompt information is used for prompting a user whether to set test parameters; and responding to the test parameter setting confirmation operation of the user, and displaying a test parameter setting interface.
Step S406, receiving the test parameter setting operation of the user for all the test tasks in the test case pipeline through the test parameter setting interface.
Step S407, storing the test parameters corresponding to the test parameter setting operation and the tasks corresponding to the test parameter setting operation in an associated manner.
Step S408, all test tasks in the test case pipeline are executed, a current test result corresponding to each test task is obtained, and step S413 is proceeded.
Step S409, displaying prompt information, wherein the prompt information is used for prompting a user whether to set test parameters; and responding to the test parameter setting confirmation operation of the user, and displaying a test parameter setting interface.
Step S410, receiving the test parameter setting operation of the user aiming at each test task in the selected test tasks through the test parameter setting interface; the selected test task is determined based on the selection operation of the test tasks in the test case pipeline.
Step S411, the test parameters corresponding to the test parameter setting operation and the test tasks corresponding to the test parameter setting operation are stored in an associated manner.
Step S412, executing the test task corresponding to the selection operation to obtain the current test result corresponding to the selected test task.
Step S413, for each executed test task, obtaining a standard test result corresponding to the test task, and generating a comparison result between the current test result and the standard test result based on the current test result and the standard test result corresponding to the test task.
Step S414, sending the test related information to the designated server, where the test related information may include the current test result, the standard test result, and the comparison result.
In order to more clearly explain the project testing method of the present application, the project testing method will be further explained with reference to specific examples.
In one example, in the first step, at least two test tasks of the target project may be obtained, where the at least two test tasks correspond to different test platforms, and each test task is used for performing a test on the corresponding test platform. The target item can be a game item which needs to be tested on each testing platform, and the testing task can be generated according to the data format requirements of different testing platforms.
And secondly, linking the trigger entries of at least two test tasks through a Jenkins pipeline to obtain a total trigger entry, specifically, using a script grammar when compiling the pipeline in the application, wherein the script grammar has fewer limitations and provides richer grammar characteristics compared with a declarative grammar. Further, a series of stages of the pipeline may be configured to facilitate understanding and designing the pipeline in compliance with project testing requirements, wherein a pipeline may be logically divided into a number of stages (stages), each stage representing a set of operations. A step (step) is the most basic unit of operation, indicating that the pipeline is specifically to perform a task, and may be defined within stages, each stage comprising a number of steps. In this embodiment, each stage in the pipeline may correspond to each test task to be executed, and the step indicates the content of each test task to be tested.
And thirdly, triggering the total trigger entrance when the preset test trigger condition is met. Wherein, satisfying the test trigger condition may include at least one of: receiving a test trigger instruction aiming at a target item; receiving a test code packet corresponding to a target project; reaching the appointed time; the time length from the last time the total trigger entrance is triggered is equal to the set time interval.
Fourthly, responding to the triggering of the total triggering entrance, and displaying prompt information which can be used for prompting whether to set the testing parameters; when the user confirms the operation, a test parameter setting interface can be displayed, and then the setting operation of the user for the test parameters in each test task is received through the test parameter setting interface.
The test parameter setting interface can be a parameter configuration interface corresponding to a test function in a development platform, and can also be a visual parameter setting interface in a Jenkins assembly line, and the visual parameter setting interface is used for visually configuring the assembly line.
Specifically, when the test parameter setting interface is a visual parameter setting interface in a Jenkins production line, the parameter setting interface can comprise a parameter setting sub-interface of each test task, parameters required to be transmitted by each test task can be set meticulously through the sub-interfaces, the parameter setting interface can also comprise a total parameter setting interface, parameters are uniformly transmitted to the test tasks through the parameters set on the total parameter setting interface, and the project test efficiency is improved.
And when the total trigger inlet is triggered, transmitting parameters customized by a parameter setting interface to each test task in the Jenkins assembly line, and covering default parameters of the test tasks. In the subsequent test flow, the method for modifying the parameter of any test task may include: and transmitting the modified parameters through the script and modifying the parameters through a parameter setting interface corresponding to the test task.
In addition, the test parameter setting interface can also provide an interface option of each test task, and the interface option can be used for selecting the test task from the test case pipeline.
Fifthly, if the selection operation aiming at the test task in the test case assembly line is received before the test task in the test case assembly line is executed, executing the test task corresponding to the selection operation to obtain the current test result corresponding to the executed test task; if no selection operation is received, all test tasks may be performed by default. The selection operation aiming at the test task in the test case pipeline can be received through the test parameter setting interface.
Sixthly, acquiring a standard test result corresponding to each test task, and acquiring a current test result and a standard test result corresponding to each executed test task; and generating a comparison result between the current test result and the standard test result based on the current test result and the standard test result corresponding to the test task. For example, when the test result is in the form of a picture, a test result picture and a standard result picture corresponding to the task may be acquired, the standard result picture may be used to display a test standard result, a difference picture may be further generated according to a difference between the test result picture and the standard result picture, a test analysis picture may be generated based on the test result picture, the standard result picture and the difference picture, and the test analysis picture may display a similarity between the test result picture and the standard result picture, so as to conveniently evaluate the test effect of the tested test task.
A seventh step of sending the test related information to a designated server, wherein the test related information may include at least one of the following: and testing the current test result, the standard test result, the comparison result, the test report and the test log corresponding to the task. Specifically, the test-related information may be sent to a designated server by mail. In addition, the test related information can be filed, and a user can conveniently review historical test results through retrieval.
An embodiment of the present application provides an electronic device, including: a memory and a processor; at least one program stored in the memory for execution by the processor, which when executed by the processor, implements: the multi-platform test process is simplified, and the project test efficiency is improved.
An embodiment of the present application provides a project testing apparatus, as shown in fig. 5, the project testing apparatus 50 may include: a task obtaining module 501, a linking module 502 and a testing module 503,
the task obtaining module 501 is configured to obtain at least two test tasks of a target project, where the at least two test tasks correspond to different test platforms;
a linking module 502, configured to link the test trigger entries of the at least two test tasks to obtain a test case pipeline and a corresponding total trigger entry;
the testing module 503 is configured to trigger the total trigger entry in response to a test trigger condition that meets the target item, execute the test task in the test case pipeline, and obtain a current test result corresponding to the test task.
The project testing device obtains a plurality of testing tasks of a project to be tested, wherein the testing tasks are used for testing on different testing platforms, the testing trigger inlets of the plurality of testing tasks are linked together by using the production line to obtain a total trigger inlet, when the testing trigger condition is met, the total trigger inlet is triggered, the testing tasks in the test case production line are executed, and then the testing result corresponding to the testing task is sent to the appointed server. By triggering the total triggering inlet, a plurality of testing tasks tested on different platforms are uniformly triggered, the flow of multi-platform testing is simplified, and the project testing efficiency is improved.
In an embodiment of the present application, the system further includes a parameter setting module, specifically configured to:
receiving the setting operation of a user for the test parameters in each test task through a test parameter setting interface;
and storing the test parameters corresponding to the test parameter setting operation and the tasks corresponding to the test parameter setting operation in an associated manner.
In this embodiment of the present application, when receiving, through the test parameter setting interface, a setting operation of a user for a test parameter in each test task, the parameter setting module is specifically configured to:
responding to the triggering of the total triggering entrance, and displaying prompt information, wherein the prompt information is used for prompting whether to set the testing parameters;
responding to the test parameter setting confirmation operation of a user, and displaying a test parameter setting interface;
and receiving the setting operation of the user aiming at the test parameters in each test task through the test parameter setting interface.
In an embodiment of the present application, the test trigger condition being met includes at least one of:
receiving a test trigger instruction aiming at a target item;
receiving a test code packet of a target project;
reaching the appointed time;
the time length from the last time the total trigger entrance is triggered is equal to the set time interval.
In this embodiment of the present application, when the test module 503 executes a test task in a test case pipeline, it is specifically configured to:
and if the selection operation aiming at the test task in the test case pipeline is received before the test task in the test case pipeline is executed, executing the test task corresponding to the selection operation.
In this embodiment of the present application, for each executed test task, the system further includes a comparison module, specifically configured to:
acquiring a standard test result corresponding to the test task;
after obtaining the current test result corresponding to the test task, the method further comprises the following steps:
and for each test task, generating a comparison result between the current test result and the standard test result based on the current test result and the standard test result corresponding to the test task.
In an embodiment of the present application, the apparatus further includes a sending module, specifically configured to:
sending test related information, wherein the test related information comprises at least one of the following:
and testing the current test result, the standard test result, the comparison result, the test report and the test log corresponding to the task.
In an alternative embodiment, an electronic device is provided, as shown in fig. 6, the electronic device 4000 shown in fig. 6 comprising: a processor 4001 and a memory 4003. Processor 4001 is coupled to memory 4003, such as via bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, and the transceiver 4004 may be used for data interaction between the electronic device and other devices, such as transmission of data and/or reception of data. In addition, the transceiver 4004 is not limited to one in practical applications, and the structure of the electronic device 4000 is not limited to the embodiment of the present application.
The Processor 4001 may be a CPU (Central Processing Unit), a general-purpose Processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 4001 may also be a combination that performs a computational function, including, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
The Memory 4003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), a magnetic Disc storage medium or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these.
The memory 4003 is used for storing application program codes (computer programs) for executing the present scheme, and is controlled by the processor 4001 to execute. Processor 4001 is configured to execute application code stored in memory 4003 to implement what is shown in the foregoing method embodiments.
The electronic devices include, but are not limited to, mobile terminals such as mobile phones, notebook computers, PADs, etc., and fixed terminals such as digital TVs, desktop computers, etc.
The present application provides a computer-readable storage medium, on which a computer program is stored, which, when running on a computer, enables the computer to execute the corresponding content in the foregoing method embodiments. Compared with the prior art, the trigger entries corresponding to the test tasks of different test platforms are linked together through the production line, so that a plurality of test tasks are uniformly triggered through the total trigger entry, the flow of multi-platform test is simplified, and the project test efficiency is improved.
Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device realizes the following when executed:
the method comprises the steps of obtaining at least two test tasks corresponding to at least two platforms in a project to be tested, linking test trigger entries of the at least two test tasks together to obtain a total trigger entry, triggering the total trigger entry when a test trigger condition is met, executing the test tasks in a test case assembly line, obtaining corresponding test results and sending the corresponding test results to a designated server.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, several modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.
Claims (10)
1. A method of project testing, comprising:
acquiring at least two test tasks of a target project, wherein the at least two test tasks correspond to different test platforms;
linking the test trigger entries of the at least two test tasks to obtain a test case pipeline and a corresponding total trigger entry;
and triggering the total trigger entrance in response to the test trigger condition meeting the target project, and executing the test task in the test case assembly line to obtain the current test result corresponding to the test task.
2. The method of claim 1, wherein prior to said executing the test tasks in the testcase pipeline, the method further comprises:
receiving the setting operation of a user for the test parameters in each test task through a test parameter setting interface;
and storing the test parameters corresponding to the test parameter setting operation and the tasks corresponding to the test parameter setting operation in an associated manner.
3. The method according to claim 2, wherein the receiving, through the test parameter setting interface, a user setting operation for the test parameters in each of the test tasks includes:
responding to the triggering of the total triggering entrance, and displaying prompt information, wherein the prompt information is used for prompting whether to set testing parameters;
responding to test parameter setting confirmation operation of a user, and displaying the test parameter setting interface;
and receiving the setting operation of the user aiming at the test parameters in each test task through a test parameter setting interface.
4. The project testing method of claim 1, wherein said meeting of a test trigger condition comprises at least one of:
receiving a test trigger instruction aiming at the target item;
receiving a test code packet of the target project;
reaching the appointed time;
the time length from the last time the total trigger entrance is triggered is equal to the set time interval.
5. The project testing method of any of claims 1 to 4, wherein said executing a test task in said testcase pipeline comprises:
and if the selection operation aiming at the test task in the test case pipeline is received before the test task in the test case pipeline is executed, executing the test task corresponding to the selection operation.
6. The project testing method of claim 1, wherein for each of said test tasks performed, said method further comprises:
acquiring a standard test result corresponding to the test task;
after the current test result corresponding to the test task is obtained, the method further includes:
and for each test task, generating a comparison result between the current test result and the standard test result based on the current test result and the standard test result corresponding to the test task.
7. The project testing method of claim 6, wherein after said obtaining a current test result corresponding to said test task, said method further comprises:
sending test related information, wherein the test related information comprises at least one of:
and the current test result, the standard test result, the comparison result, the test report and the test log corresponding to the test task.
8. An item testing apparatus, comprising:
the task acquisition module is used for acquiring at least two test tasks of the target project, wherein the at least two test tasks correspond to different test platforms;
the link module is used for linking the test trigger entries of the at least two test tasks to obtain a test case pipeline and a corresponding total trigger entry;
and the test module is used for responding to the test trigger condition meeting the target project, triggering the total trigger inlet, executing the test task in the test case assembly line and obtaining the current test result corresponding to the test task.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the project testing method of any of claims 1-7 when executing the program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the project testing method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110814117.3A CN113656283A (en) | 2021-07-19 | 2021-07-19 | Project testing method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110814117.3A CN113656283A (en) | 2021-07-19 | 2021-07-19 | Project testing method and device, electronic equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113656283A true CN113656283A (en) | 2021-11-16 |
Family
ID=78477489
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110814117.3A Pending CN113656283A (en) | 2021-07-19 | 2021-07-19 | Project testing method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113656283A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103544101A (en) * | 2012-07-16 | 2014-01-29 | 深圳市世纪光速信息技术有限公司 | Wireless platform development automatic test system and method |
| US20180137286A1 (en) * | 2016-11-16 | 2018-05-17 | International Business Machines Corporation | Method and apparatus for security testing of application flows that cannot be automated through http replay |
| CN110347085A (en) * | 2019-07-16 | 2019-10-18 | 广州小鹏汽车科技有限公司 | Automatization test system, method, vehicle and computer-readable medium |
| CN111914262A (en) * | 2020-08-12 | 2020-11-10 | 中国工商银行股份有限公司 | Test method, device, system, electronic equipment and storage medium |
| CN112256265A (en) * | 2020-10-14 | 2021-01-22 | 北京百家科技集团有限公司 | H5 page stability testing method and device, storage medium and electronic equipment |
-
2021
- 2021-07-19 CN CN202110814117.3A patent/CN113656283A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103544101A (en) * | 2012-07-16 | 2014-01-29 | 深圳市世纪光速信息技术有限公司 | Wireless platform development automatic test system and method |
| US20180137286A1 (en) * | 2016-11-16 | 2018-05-17 | International Business Machines Corporation | Method and apparatus for security testing of application flows that cannot be automated through http replay |
| CN110347085A (en) * | 2019-07-16 | 2019-10-18 | 广州小鹏汽车科技有限公司 | Automatization test system, method, vehicle and computer-readable medium |
| CN111914262A (en) * | 2020-08-12 | 2020-11-10 | 中国工商银行股份有限公司 | Test method, device, system, electronic equipment and storage medium |
| CN112256265A (en) * | 2020-10-14 | 2021-01-22 | 北京百家科技集团有限公司 | H5 page stability testing method and device, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109933522B (en) | Test method, test system and storage medium for automatic case | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| CA2915619C (en) | Method and apparatus for customized software development kit (sdk) generation | |
| CN110134386B (en) | Program editing method and device | |
| CN110659198A (en) | Application program test case execution method and device and software test system | |
| CN111181805B (en) | Micro-service test baffle generation method and system based on test case | |
| CN110320378B (en) | Method, apparatus, device and computer readable storage medium for applying for a quality control test | |
| CN111475390A (en) | Log collection system deployment method, device, equipment and storage medium | |
| CN108132876B (en) | Embedded software object code unit testing method based on injection mode | |
| CN112506785A (en) | Automatic testing method, device, equipment and medium for login of Html5 game page | |
| CN113535567B (en) | Software testing method, device, equipment and medium | |
| CN113485882A (en) | Chip verification method and device and computer readable storage medium | |
| CN117370203A (en) | Automatic test method, system, electronic equipment and storage medium | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN111435328B (en) | Application testing method and device, electronic equipment and readable storage medium | |
| CN113656283A (en) | Project testing method and device, electronic equipment and computer readable storage medium | |
| CN114297088A (en) | Method, device, equipment and medium for testing front end vue frame assembly | |
| CN113515263B (en) | Industrial APP mechanism model deployment method, device, equipment and readable storage medium | |
| CN115658069A (en) | Project packaging and online compiling method for release platform | |
| CN112988588B (en) | Client software debugging method and device, storage medium and electronic equipment | |
| CN111427770B (en) | Resource testing method and related equipment | |
| CN114564213A (en) | Pre-installed software deployment method, system, terminal and storage medium | |
| CN115705187A (en) | Item dependency relationship display method and device, terminal equipment and storage medium | |
| CN112486497A (en) | Compiling configuration file generation method and device, electronic equipment and storage medium | |
| CN113608996B (en) | Mirror image compiling test method, system, device and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |