CN114385510A

CN114385510A - Test method and device and electronic equipment

Info

Publication number: CN114385510A
Application number: CN202210049561.5A
Authority: CN
Inventors: 梁浩; 赵国玉
Original assignee: Beijing Ziroom Information Technology Co Ltd
Current assignee: Beijing Ziroom Information Technology Co Ltd
Priority date: 2022-01-17
Filing date: 2022-01-17
Publication date: 2022-04-22

Abstract

The invention relates to the field of testing, in particular to a testing method and device and electronic equipment. The method comprises the following steps: the method comprises the steps of obtaining a test instruction, wherein the test instruction comprises an identification of a module to be tested in target application, matching a historical test case corresponding to the module to be tested in a test database based on the identification of the module to be tested when the module to be tested is determined to exist based on the identification of the module to be tested, obtaining the target test case to test the module to be tested when the historical test case is not matched, determining a test result, establishing a corresponding relation between the target test case and the module to be tested, and storing the corresponding relation into the test database to update the test database. By introducing the database, the use case is repeatedly utilized, and meanwhile, due to the existence of the database, the historical test case can be used and updated wherever the database is connected, so that the working efficiency is greatly improved.

Description

Test method and device and electronic equipment

Technical Field

The invention relates to the field of testing, in particular to a testing method and device and electronic equipment.

Background

With the development of computer technology, more and more scenes are used by software, and in order to ensure the reliability of software operation, the software needs to be tested.

Decentralized management of various types of test cases, management lack of functional cases, management lack of test cases of a mobile terminal, test, research, development and fracture: the test case execution result and the constructed and deployed version have no intermediate dependency relationship, and the test scheduling is split: the test link is cracked, no unified public test task scheduling service exists, and the test report is summarized off-line: and (5) summarizing and transmitting related informed personnel under the test report line.

Even if some cooperative software exists, the cooperative software only stays in a short-term storage mode such as local page rendering or caching, and once a user changes the used equipment, the previous test case cannot be used.

Disclosure of Invention

In view of this, embodiments of the present invention provide a testing method and apparatus, and an electronic device, so as to solve the problem that the management or testing cannot be performed effectively for a long time.

According to a first aspect, an embodiment of the present invention provides a method for testing, including:

acquiring a test instruction, wherein the test instruction comprises an identifier of a module to be tested in a target application;

when the module to be tested is determined to exist based on the identification of the module to be tested, matching a historical test case corresponding to the module to be tested in a test database based on the identification of the module to be tested;

when the historical test case is not matched, acquiring a target test case to test the module to be tested, and determining a test result;

and establishing a corresponding relation between the target test case and the module to be tested, and storing the corresponding relation into the test database to update the test database.

The test method provided by the embodiment of the invention realizes the repeated use of the use case by introducing the database, and meanwhile, due to the existence of the database, the historical test use case can be used and updated wherever the database is connected, so that the working efficiency is greatly improved.

With reference to the first aspect, in a first implementation manner of the first aspect, when it is determined that the module to be tested exists based on the identifier of the module to be tested, matching a historical test case corresponding to the module to be tested in a test database based on the identifier of the module to be tested, further includes:

when the module to be tested does not exist based on the identification of the module to be tested, establishing a corresponding new application based on the identification of the module to be tested;

establishing a corresponding module to be tested in the new application based on the identifier of the module to be tested;

and updating the new application and the module to be tested into a test database.

According to the testing method provided by the embodiment of the invention, the unprocessed application and the corresponding module are newly built and added to the database, so that the applications covered by the test case and the modules covered by the test are wider and wider, the corresponding database is more robust and more perfect, and the working efficiency is greatly improved.

With reference to the first aspect, in a second implementation manner of the first aspect, the obtaining a target test case to test the module to be tested when the historical test case is not matched to determine a test result includes:

and when the historical test case is matched, the historical test case is used as a target test case to test the module to be tested, and a test result is determined.

According to the testing method provided by the embodiment of the invention, when the corresponding test case exists in the database clearly, the previous test case can be reused without repeated new establishment, so that the working efficiency is greatly improved.

With reference to the first aspect, in a third implementation manner of the first aspect, when the historical test case is not matched, the obtaining a target test case to test the module to be tested, and determining a test result further includes:

corresponding each item in the target test case with each item in the module to be tested, and determining a corresponding relation;

judging whether a project daily report needs to be created or not;

when the project daily report does not need to be created, testing each project in each module to be tested according to each corresponding project directly according to the corresponding relation, and determining a test result;

and uploading the test result to the database.

The testing method provided by the embodiment of the invention ensures the accuracy and comprehensiveness of the test result through testing each project one by one, avoids the whole detection result from being wrong due to the missing test of a certain project, and further improves the working efficiency.

With reference to the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the determining whether the project daily report needs to be created further includes:

when project daily reports need to be created, testing each project of each module to be tested according to the corresponding relation, and determining the test result of each project;

and outputting the test result according to a preset daily report template.

According to the testing method provided by the embodiment of the invention, the detection result is output in a daily report form, so that the detection result can be timely and accurately sent to relevant processing personnel, the relevant processing personnel can timely perform relevant processing according to the detection result, and the working efficiency is further improved.

With reference to the third embodiment of the first aspect, in the fifth embodiment of the first aspect, the method further includes:

judging whether to send a daily report or not;

and when the daily newspaper needs to be sent, responding to the sending operation of the daily newspaper sending interface, and sending the daily newspaper to the client.

The testing method provided by the embodiment of the invention ensures that the daily report can be timely and accurately sent to related processing personnel by determining the manner of sending the daily report, so that the related personnel can timely perform related processing according to the detection result, and the working efficiency is further improved.

With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner of the first aspect, when it is necessary to generate a daily report, generating the daily report in response to a creation operation of a daily report creation interface includes:

responding to a risk selection operation of a daily report creation interface, and determining a risk type of the daily report;

filling the risk type into the daily report.

According to the test method provided by the embodiment of the invention, the risk option is added into the daily report, so that the detection result is simply and clearly displayed preliminarily, the risk can be conveniently confirmed by related processing personnel, and the working efficiency is further improved.

According to a second aspect, an embodiment of the present invention provides a device for testing, including:

the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a test instruction, and the test instruction comprises an identifier of a module to be tested in a target application;

the first processing unit is used for matching a historical test case corresponding to the module to be tested in a test database based on the identifier of the module to be tested when the module to be tested is determined to exist based on the identifier of the module to be tested;

the second processing unit is used for acquiring a target test case to test the module to be tested and determining a test result when the historical test case is not matched;

and the third processing unit is used for establishing the corresponding relation between the target test case and the module to be tested and storing the corresponding relation into the test database so as to update the test database.

According to a third aspect, an embodiment of the present invention provides an electronic device, including: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory having stored therein computer instructions, and the processor executing the computer instructions to perform the method of testing described in the first aspect or any one of the embodiments of the first aspect.

According to a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to perform the method of testing described in the first aspect or any one of the implementation manners of the first aspect.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a flow chart of a testing method according to an embodiment of the invention;

FIG. 2 is a flow chart of a testing method according to an embodiment of the invention;

FIG. 3 is a flow chart of a testing method according to an embodiment of the invention;

FIG. 4 is a schematic diagram of a test workflow in conjunction with a state presentation platform according to an embodiment of the present invention;

FIG. 5 is a block diagram of a test apparatus according to an embodiment of the present invention;

fig. 6 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

In accordance with an embodiment of the present invention, there is provided a method embodiment of testing, it being noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.

In this embodiment, a testing method is provided, which can be used in an electronic device, such as a computer, a server, a tablet computer, etc., fig. 1 is a flowchart of the testing method according to an embodiment of the present invention, and as shown in fig. 1, the testing method includes the following steps:

s11, acquiring a test instruction, wherein the test instruction comprises an identifier of a module to be tested in the target application;

specifically, one application may include a plurality of modules.

For example, if there is an application a, there are a module to be tested [00], a module to be tested [01], and a module to be tested [02] in the application a, and if the test instruction includes the identifier "a [01 ]", it is determined that the module to be tested [02] in the application a is found.

S12, when the module to be tested is determined to exist based on the identifier of the module to be tested, matching a historical test case corresponding to the module to be tested in a test database based on the identifier of the module to be tested;

specifically, still taking the application a as an example, if the module [00] in the application a is tested once but the module [02] to be tested is not tested, the historical test case cannot be matched.

Details about this step will be described later.

S13, when the historical test case is not matched, acquiring a target test case to test the module to be tested, and determining a test result;

specifically, still taking the application a as an example, when the module [02] to be tested is to be tested, a new test case new needs to be created for the module [02] to be tested, and the new test case is used to test the module [02] to be tested, so as to determine the test result.

Details about this step will be described later.

S14, establishing the corresponding relation between the target test case and the module to be tested, and storing the corresponding relation into the test database to update the test database.

Specifically, taking the module to be tested [02] as an example, the relationship between the module to be tested [02] and the newly-built test case new is updated to the test database.

In this embodiment, a testing method is provided, which can be used in electronic devices, such as computers, servers, tablet computers, and the like, fig. 2 is a flowchart of the testing method according to the embodiment of the present invention, as shown in fig. 2, the flowchart includes the following steps:

s21, acquiring a test instruction, wherein the test instruction comprises an identifier of a module to be tested in the target application;

please refer to S11 in fig. 1, which is not described herein again.

S22, when the module to be tested is determined to exist based on the identifier of the module to be tested, matching a historical test case corresponding to the module to be tested in a test database based on the identifier of the module to be tested;

specifically, S22 includes:

s221, when the module to be tested does not exist based on the identification of the module to be tested, establishing a corresponding new application based on the identification of the module to be tested;

specifically, for example, if a module to be tested is identified as X, where the identifier X corresponds to the module to be tested [ X ], and the module to be tested [ X ] belongs to the application Y, then the application Y is newly created.

S222, establishing a corresponding module to be tested in the new application based on the identifier of the module to be tested;

specifically, taking the above-mentioned module to be tested identifier X as an example, after the application Y is newly built, the module to be tested [ X ] is newly built in Y.

And S223, updating the new application and the module to be tested into a test database.

Specifically, taking the new application Y and the corresponding module to be tested [ x ] as an example, the new application Y and the corresponding module to be tested [ x ] are updated into the test database.

S23, when the historical test case is not matched, acquiring a target test case to test the module to be tested, and determining a test result;

specifically, S23 includes:

s231, when the historical test case is matched, the historical test case is used as a target test case to test the module to be tested, and a test result is determined.

Specifically, still taking the application a as an example, assuming that the module [00] in the application a is tested once and a corresponding test case alpha is generated, when the module to be tested in the test instruction is identified as "a [00 ]", the historical test case alpha can be directly used to determine the test result.

S232, corresponding each item in the target test case to each item in the module to be tested, and determining a corresponding relation;

specifically, one module under test may include a plurality of items.

For example, if a module to be tested is assumed to be a login module of an application, the login module is assumed to include an "input item", "button item" and "judgment item", and a corresponding time-measuring case log includes an item a, an item b and an item c, where the item a is related content of test input, the item b is related content of a test button, and the item c is related content of test judgment, the item a in the test case corresponds to the "input item" in the module to be tested, the item b in the test case corresponds to the "button item" in the module to be tested, and the item c in the test case corresponds to the "judgment item" in the module to be tested.

S233, judging whether project daily reports need to be created;

in some optional implementations of this embodiment, the S233 may include:

(1) when project daily reports need to be created, testing each project of each module to be tested according to the corresponding relation, and determining the test result of each project;

specifically, still taking the above-mentioned login module as an example, the "input item", "button item" and "judgment item" in the login module are detected, and it is assumed that the detection results of the "input item", "button item" and "judgment item" are respectively good, faulty and serious.

(2) And outputting the test result according to a preset daily report template.

Specifically, when the daily newspaper needs to be output, the detection results of the "input item", "button item" and "judgment item" are output according to a preset daily newspaper format.

S234, when the project daily report does not need to be created, testing each project in each module to be tested according to each corresponding project directly according to the corresponding relation, and determining a test result;

specifically, this step is the same as step S233(1), and is not described here again.

And S235, uploading the test result to the database.

Specifically, still taking the above-mentioned login module and detection result as examples, the detection results of the input item, "button item" and "judgment item" are respectively good, faulty and serious, and are input into the database.

S24, establishing the corresponding relation between the target test case and the module to be tested, and storing the corresponding relation into the test database to update the test database.

Please refer to S14 in fig. 1, which is not described herein again.

As a specific application example of the present embodiment. As shown in fig. 3, the test method includes:

and S1, acquiring a test instruction.

S2, judging whether the test command has history application and module, if yes, executing step S3, otherwise executing step S4.

And S3, selecting the corresponding application and module.

And S4, newly building a corresponding application module.

S5, inquiring whether a corresponding test case exists through the database, if so, executing the step S7, otherwise, executing the step S6.

And S6, creating a new test case.

S7, the test is started.

And S8, matching the items in the test cases with the corresponding modules.

S9, judging whether project daily report needs to be created, if so, executing step S10, otherwise, executing step S11.

And S10, creating a project daily report and generating the project daily report.

S11, judging whether the daily newspaper is generated, if yes, executing step S12.

And S12, selecting risks and generating a daily report.

As an embodiment of the present invention, the present invention may also perform workflow display, as shown in fig. 4, when the workflow is in an untested state, the current working state is sent to the state display platform, so that the state display platform displays "in development" or "demand creation", and the quality assurance platform can generate a test case according to the current development state, and display the state as "not started", when the workflow is in a test state, case addition can be performed, so that the state display is "in progress" or "in test", and when the workflow state is in test completion, the state display platform displays "test completion" and sends a test report.

In this embodiment, a testing apparatus is further provided, and the apparatus is used to implement the foregoing embodiments and preferred embodiments, and the description of the apparatus is omitted for brevity. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

The present embodiment provides a testing apparatus, as shown in fig. 5, including:

an obtaining unit 51, configured to obtain a test instruction, where the test instruction includes an identifier of a module to be tested in a target application;

the first processing unit 52 is configured to, when it is determined that the module to be tested exists based on the identifier of the module to be tested, match a historical test case corresponding to the module to be tested in a test database based on the identifier of the module to be tested;

the second processing unit 53 is configured to, when the historical test case is not matched, obtain a target test case to test the module to be tested, and determine a test result;

and a third processing unit 54, configured to establish a corresponding relationship between the target test case and the module to be tested, and store the corresponding relationship in the test database to update the test database.

The firmware refresh apparatus in this embodiment is presented in the form of functional units, where a unit refers to an ASIC circuit, a processor and a memory executing one or more software or fixed programs, and/or other devices that may provide the above-described functionality.

Further functional descriptions of the modules are the same as those of the corresponding embodiments, and are not repeated herein.

The embodiment of the invention also provides electronic equipment which is provided with the testing device shown in the figure 5.

Referring to fig. 6, fig. 6 is a schematic structural diagram of an electronic device according to an alternative embodiment of the present invention, and as shown in fig. 6, the electronic device may include: at least one processor 61, such as a CPU (Central Processing Unit), at least one communication interface 63, memory 64, at least one communication bus 62. Wherein a communication bus 62 is used to enable the connection communication between these components. The communication interface 63 may include a Display (Display) and a Keyboard (Keyboard), and the optional communication interface 63 may also include a standard wired interface and a standard wireless interface. The Memory 64 may be a high-speed RAM Memory (volatile Random Access Memory) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The memory 64 may optionally be at least one memory device located remotely from the processor 61. Wherein the processor 61 may be in connection with the apparatus described in fig. 6, an application program is stored in the memory 64, and the processor 61 calls the program code stored in the memory 64 for performing any of the above-mentioned method steps.

The communication bus 62 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 62 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 6, but this is not intended to represent only one bus or type of bus.

The memory 64 may include a volatile memory (RAM), such as a random-access memory (RAM); the memory may also include a non-volatile memory (english: non-volatile memory), such as a flash memory (english: flash memory), a hard disk (english: hard disk drive, abbreviated: HDD) or a solid-state drive (english: SSD); the memory 64 may also comprise a combination of the above types of memory.

The processor 61 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of CPU and NP.

The processor 61 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

Optionally, the memory 64 is also used to store program instructions. The processor 61 may invoke program instructions to implement the method of testing as shown in any of the embodiments of the present application.

Embodiments of the present invention further provide a non-transitory computer storage medium, where the computer storage medium stores computer-executable instructions, and the computer-executable instructions may execute the method of testing in any of the above method embodiments. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid State Drive (SSD), or the like; the storage medium may also comprise a combination of memories of the kind described above.

Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A method of testing, comprising:

2. The method of claim 1, wherein when it is determined that the module under test exists based on the identifier of the module under test, matching a historical test case corresponding to the module under test in a test database based on the identifier of the module under test, further comprising:

3. The method according to claim 1, wherein when the historical test case is not matched, obtaining a target test case to test the module to be tested, and determining a test result comprises:

4. The method according to claim 1, wherein when the historical test case is not matched, obtaining a target test case to test the module to be tested, and determining a test result, further comprises:

judging whether a project daily report needs to be created or not;

and uploading the test result to the database.

5. The method of claim 4, wherein said determining whether a project diary needs to be created further comprises:

and outputting the test result according to a preset daily report template.

6. The method of claim 4, further comprising:

judging whether to send a daily report or not;

7. The method according to claim 6, wherein the generating the daily report in response to the creation operation of the daily report creation interface when the daily report needs to be generated comprises:

filling the risk type into the daily report.

8. An apparatus for testing, comprising:

9. An electronic device, comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the steps of the method of any one of claims 1-7.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1-7.