CN114722197A

CN114722197A - Question list generation method and device

Info

Publication number: CN114722197A
Application number: CN202210332843.6A
Authority: CN
Inventors: 王永存
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2022-03-31
Filing date: 2022-03-31
Publication date: 2022-07-08

Abstract

The invention provides a method and a device for generating a question list, which relate to the technical field of artificial intelligence and are used for improving the quality of the generated question list and the efficiency of program test work in the process of testing a program, and the method comprises the following steps: determining a target exception problem existing in a target program; determining a target problem type corresponding to the target abnormal problem according to the selection operation of the target type label in the plurality of type labels; a plurality of category labels for indicating a plurality of issue categories, a target category label for indicating a target issue category; generating a question sheet corresponding to the target abnormal question according to the acquired description content and the target question category; the description content includes specific explanation content of the target abnormal problem, and the question list is used for indicating the abnormal problem existing in the target program. The embodiment of the invention is applied to a scene of generating a question list by a test program.

Description

Question list generation method and device

Technical Field

The invention relates to the technical field of artificial intelligence, in particular to a question list generating method and device.

Background

Before a program (an application program, a webpage or the like) developed by a program developer is put into use, the program needs to be tested through a program testing function by a tester, and the program can be put into use only when the program is determined not to have any problem. In the process that a tester tests a program through a program testing function, when the tester finds that the program has a problem, the tester needs to describe the problem, and the problem is described through a complete, accurate and concise language (or pictures and the like), so that a question sheet is generated to be referred by a developer and the problem is solved.

In actual work, for the same problem in a program, the description modes, language habits, and the like of different people for the problem are different, so that it cannot be guaranteed that the concept expressed by the description of the problem in the question list by the tester is the same as the concept understood by the developer according to the description in the question list (i.e., the understanding of the same description by different people is different). Thereby causing a phenomenon in which developers have differences in understanding of the problems described in the question sheet (or testers have errors in the expression of the problems), causing delays in problem confirmation and problem repair.

Therefore, when a tester generates a problem list for a program, the problem description of the tester is inaccurate, or the understanding of the problem description by a developer is biased, so that the efficiency of the program testing work is low.

Disclosure of Invention

The embodiment of the invention provides a method and a device for generating a question list, which are used for improving the quality of the generated question list and the efficiency of program test work in the process of testing a program.

In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:

in a first aspect, a method for generating a question list is provided, the method comprising: determining a target exception problem existing in a target program; determining a target problem category corresponding to the target abnormal problem according to the selection operation of a target category label in the plurality of category labels; the plurality of category labels are used for indicating a plurality of question categories, and the target category label is used for indicating a target question category; generating a question sheet corresponding to the target abnormal question according to the acquired description content and the target question category; the description content comprises specific explanation content of the target abnormal problem, and the problem ticket is used for indicating the abnormal problem existing in the target program.

In one possible implementation, the plurality of category tags include a plurality of main category tags and a plurality of sub-category tags, one main category tag corresponds to at least one sub-category tag, and the target category tag includes a first tag and a second tag; determining a target problem category corresponding to a target abnormal problem according to the selection operation of a target category label in a plurality of category labels, wherein the method comprises the following steps: receiving a first operation of a user on a first label in the displayed plurality of main category labels; responding to the first operation, and determining a main problem type corresponding to the target abnormal problem; receiving a second operation of the user on a second tag in the displayed at least one sub-category tag; responding to the second operation, and determining a sub-problem type corresponding to the target abnormal problem; at least one sub-category label is a sub-category label corresponding to the first label.

In a possible implementation manner, generating a question list corresponding to the target abnormal question according to the obtained description content and the target question category includes: receiving a third operation of the user; the third operation includes at least one of: text input operation, voice input operation and screenshot triggering operation; responding to the third operation, generating description contents corresponding to the target abnormal problems, and obtaining a problem list corresponding to the target abnormal problems according to the target problem types; the description also includes correct results corresponding to the target exception problem.

In one possible implementation, before determining that the target exception problem exists in the target program, the method further includes: the method comprises the steps of predetermining a plurality of problem categories corresponding to a plurality of abnormal problems included in the process of software testing; the plurality of question categories comprise a plurality of main question categories and a plurality of sub-question categories, and one main question category corresponds to at least one sub-question category; the plurality of main issue categories include at least one of: equivalence class problems, boundary value problems, interface problems, batch problems; and displaying a plurality of category labels corresponding to a plurality of problem categories in an interface of the test management platform.

In a second aspect, there is provided a question ticket generating apparatus comprising: a determination unit and a generation unit; the determining unit is used for determining a target abnormal problem existing in the target program; the determining unit is further used for determining a target problem type corresponding to the target abnormal problem according to the selection operation of the target type label in the plurality of type labels; a plurality of category labels for indicating a plurality of issue categories, a target category label for indicating a target issue category; the generating unit is used for generating a question list corresponding to the target abnormal question according to the acquired description content and the target question category; the description content includes specific explanation content of the target abnormal problem, and the question list is used for indicating the abnormal problem existing in the target program.

In one possible implementation, the plurality of category tags include a plurality of main category tags and a plurality of sub-category tags, one main category tag corresponds to at least one sub-category tag, and the target category tag includes a first tag and a second tag; the question ticket generating apparatus further includes: a receiving unit; the receiving unit is used for receiving a first operation of a user on a first label in the displayed plurality of main category labels; the determining unit is further used for responding to the first operation and determining a main problem type corresponding to the target abnormal problem; the receiving unit is further used for receiving a second operation of the user on a second tag in the displayed at least one sub-category tag; the determining unit is also used for responding to the second operation and determining the sub-problem category corresponding to the target abnormal problem; at least one sub-category label is a sub-category label corresponding to the first label.

In a possible implementation manner, the receiving unit is further configured to receive a third operation of the user; the third operation includes at least one of: text input operation, voice input operation and screenshot triggering operation; the generating unit is specifically used for responding to the third operation, generating description contents corresponding to the target abnormal problems, and obtaining a problem list corresponding to the target abnormal problems according to the target problem types; the description also includes the correct result corresponding to the target exception problem.

In one possible implementation manner, the question ticket generating apparatus further includes: a display unit; the determining unit is also used for determining a plurality of problem categories corresponding to a plurality of abnormal problems included in the software testing process in advance; the plurality of question categories comprise a plurality of main question categories and a plurality of sub-question categories, and one main question category corresponds to at least one sub-question category; the plurality of major issue categories include at least one of: equivalence class problems, boundary value problems, interface problems, batch problems; and the display unit is used for displaying a plurality of category labels corresponding to a plurality of problem categories in an interface of the test management platform.

In a third aspect, there is provided a computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computer, cause the computer to perform a method of problem ticket generation as in the first aspect.

In a fourth aspect, an electronic device includes: a processor and a memory; wherein the memory is used for storing one or more programs, the one or more programs include computer executable instructions, and when the electronic device runs, the processor executes the computer executable instructions stored in the memory, so as to make the electronic device execute the problem ticket generating method according to the first aspect.

In a fifth aspect, a computer program product comprises instructions which, when run on a computer, cause the computer to perform a method of problem ticket generation as in the first aspect.

The embodiment of the invention provides a method and a device for generating a question list, which are applied to a scene of generating the question list by a test program. Further, descriptive contents including specific explanation contents of the target abnormal problem are obtained, and a problem list used for indicating the target abnormal problem existing in the target program is generated according to the obtained descriptive contents and the target problem category. Therefore, when an abnormal problem existing in the program is determined, the problem category of the abnormal problem can be quickly marked through a plurality of category labels for indicating a plurality of target problem categories, and the problem list can be quickly generated by combining the acquired description content. The problem that the problem description of the tester has errors or the understanding of the problem description of the developer has deviation is solved without the need of the tester to subjectively describe the target abnormal problem. Therefore, in the process of testing the program, the quality of the generated problem list can be improved, and the efficiency of program testing work is improved.

Drawings

Fig. 1 is a schematic structural diagram of a question list generating system according to an embodiment of the present invention;

FIG. 2 is a first flowchart illustrating a problem ticket generating method according to an embodiment of the present invention;

FIG. 3 is a schematic flow chart of a problem ticket generating method according to an embodiment of the present invention;

fig. 4 is a schematic flow chart of a problem ticket generating method according to an embodiment of the present invention;

FIG. 5 is a schematic interface diagram of a question sheet generation method according to an embodiment of the present invention;

fig. 6 is a schematic flow chart of a problem ticket generating method according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a problem ticket generating apparatus according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.

In the description of the present invention, "/" means "or" unless otherwise specified, for example, a/B may mean a or B. "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. Further, "at least one" or "a plurality" means two or more. The terms "first", "second", and the like do not necessarily limit the number and execution order, and the terms "first", "second", and the like do not necessarily limit the difference.

Currently, standardization is an important factor in any product production process, and program testing (software testing) belongs to black box testing among software testing. One of the purposes of software testing is to find out BUGs (BUGs) present in the test target system. The current software testing (function) in the industry is usually done as follows: reading relevant documents such as requirements and the like, making a scheme, compiling a case, testing implementation, submitting problems, BUG confirmation, repeated testing and forming a test report, wherein the whole process needs developers, testers and demanders to finish together. The step of submitting the problems is completed by a tester, and the step of submitting the problems mainly comprises the step of submitting a problem form corresponding to the abnormal problems, wherein the problem form comprises the description of the submitted abnormal problems. The description of the submitted abnormal problems in the step of submitting the problems must be complete, accurate and concise.

Then, in the actual work, in the problem submitting link of the software test, the text description of the tester is taken as the main basis. In the face of the same abnormal problem, the description modes, language habits and the like of different testers (or developers) are different, the description of the abnormal problem is different from person to person, and the description (or called problem description) of the same abnormal problem by different testers can not be guaranteed to be completely consistent from the logic structure, language words, mode method and the like. In actual work, due to the abnormal problem submitted, the phenomena of problem confirmation and repair delay caused by the difference in the ideal solution sometimes occur. Therefore, it is very important to clearly describe the abnormal problem in the testing process, which is an important basis for developers to confirm and repair the BUG, is a problem submitting link, and is a key for continuing the software testing. Therefore, in the process of testing the program, it is necessary to ensure that the abnormal problem is clearly described, so that the quality of the problem list corresponding to the generated abnormal problem is improved, and the efficiency of program testing work is further improved.

The problem list generation method provided by the embodiment of the invention can be suitable for a problem list generation system. Fig. 1 shows a schematic configuration of the question sheet generation system. As shown in fig. 1, the question sheet generating system 10 includes an electronic device 11, a server 12, a user 13, a tester 14, and a developer 15. The electronic device 11 is connected to the server 12. The electronic device 11 and the server 12 may be connected by a wired method or a wireless method, which is not limited in the embodiment of the present invention.

The electronic device 11 may be used for the internet of things, and the electronic device 11 may include hardware such as a plurality of Central Processing Units (CPUs), a plurality of memories, and a storage device storing a plurality of operating systems. The specific electronic device 11 may include a plurality of electronic devices, for example, the user 13, the tester 14, and the developer 15 correspond to different electronic devices, and in the illustration of the embodiment of the present invention, an example of including one electronic device (that is, the user 13, the developer 14, and the tester 15 correspond to the same electronic device) is taken as an example for illustration.

The user 13 may be a demanding person, that is, a person using the application program, so that the developer 14 develops and completes the corresponding application program according to the demand of the user 13 through a demand document (used for indicating functions and effects of the application program, and the like) provided by the user 13.

The developer 14 writes a development application program according to the requirement document provided by the user 13, and specifically completes the development of the application program by reading the requirement document, making a scheme and writing a case.

The tester 15 performs a program test on the application program developed by the developer 14, determines whether an abnormal problem exists in the application program, and specifically performs a test implementation and a test submission, determines whether the abnormal problem is a BUG (i.e., BUG determination) by the developer 14, performs a repeated test by the tester 15, and finally forms a test report.

The electronic device 11 may be used for performing instruction or data interaction with the server 12, for example, the electronic device 11 may include a program testing platform, which may be a specific software testing application, for example, and tests the program to be tested through the program testing platform to determine the problem in the program to be tested.

The server 12 may also be used in the internet of things, and is configured to store data information and perform a corresponding task function, for example, to store a test rule, a program to be tested, and the like, or to test the program to be tested according to an instruction of the electronic device 11.

It should be noted that the electronic device 11 and the server 12 may be independent devices or may be integrated in the same device, and the present invention is not limited to this.

When the electronic device 11 and the server 12 are integrated in the same device, the communication mode between the electronic device 11 and the server 12 is the communication between the internal modules of the device. In this case, the communication flow between the two is the same as the "communication flow between the electronic device 11 and the server 12 when they are independent of each other".

In the following embodiments provided by the present invention, the present invention is described by taking the electronic device 11 and the server 12 as an example, which are independent of each other.

A problem ticket generating method provided in an embodiment of the present invention is described below with reference to the accompanying drawings.

As shown in fig. 2, a method for generating a question list provided in an embodiment of the present invention is applied to an electronic device including at least one memory and at least one central processing unit CPU, and includes: S201-S203:

s201, determining a target abnormal problem existing in the target program.

In the embodiment of the present invention, after the program developer completes the development of the target program, the tester needs to perform a functional test on the target program, where the functional test may be understood as a black box test, so that the target program is put into use when it is determined through the test that no abnormal problem (i.e., bug) exists in the target program.

It can be understood that the functional test (black box test) is to verify each function of the developed application product, and perform a test item by item according to a requirement document (for indicating the function and effect that the application should have) proposed by a requirement person, so as to check whether the application product has the function required by the user. Whether each function can be normally used is detected through testing. In the test, the program is treated as a black box which cannot be opened, and in the case of completely not considering the internal structure and internal characteristics of the program, a test is performed at the program interface, which only checks whether the program functions are normally used according to the requirements specification and whether the program can properly receive input data to generate correct output information. The black box test is mainly used for testing a software interface and a software function by focusing on an external structure of a program and not considering an internal logic structure.

As a possible implementation manner, a tester needs to test a target program through a test management platform, and the test management platform is used for testing whether an abnormal problem exists in the program. Specifically, the target program needs to be run (i.e., the target program is tested) on the basis of the test management platform, so that a tester artificially determines whether an abnormal problem (bug) exists in the target program according to the program development requirement. BUGs (BUGs) may be understood as some undetected BUGs or technical problems hidden in an application.

It should be noted that the above program development requirements can be understood as: the function required by the person in need (i.e., the person using the object program) when using the object program. Specifically, when a demander needs an object program with some functions, the program development requirement can be determined first, so that the developer develops the object program according to the program development requirement. And then the tester tests the obtained target program to determine whether the functions included in the target program meet the program development requirements.

The test management platform is an application tool used by a tester when testing a program, and comprises various elements, architectures, flows, standards, mechanisms, tools and the like, and has the functions of creating a safe and reliable software running space, strong isolation capability, simpler management and the like.

The test management platform integrates the characteristics of high efficiency, low cost and the like, greatly shortens the test period of software products, can improve the product quality, can fully exert the advantage of virtualization, reduces the number of physical workstations, reduces the energy consumption of an IT system of a client, and improves the software test working space of the space use efficiency.

Specifically, a tester may start a test management platform in the electronic device, for example, start the test management platform of the electronic device by opening a button, input identification information of a target program to be tested on a test interface corresponding to the test management platform, trigger the test management platform to automatically perform a function test/black box test on the target program, and display a test result (for example, a test result of the target program) obtained by the test on the test interface. The test result of the target program comprises test success or test failure, wherein under the condition of test failure, abnormal problems existing in the target program can be displayed for a tester to refer and confirm whether the target program is a bug or not.

S202, determining a target problem type corresponding to the target abnormal problem according to the selection operation of the target type label in the plurality of type labels.

The plurality of category labels are used for indicating a plurality of question categories, and the target category label is used for indicating a target question category.

As a possible implementation manner, in the process of testing the target program through the test management platform, a plurality of category labels are displayed in the test interface, and when it is determined that a target abnormal problem exists in the target program, a user (tester) may trigger to suspend testing the target program and determine a problem category to which the target abnormal problem belongs, so as to select a target category label corresponding to the problem category to which the target abnormal problem belongs from the displayed plurality of category labels.

Illustratively, when it is determined that the target abnormal problem exists in the target program, the tester judges the problem category to which the target abnormal problem belongs according to the specific form of the target abnormal problem by combining with the experience of the tester, and manually selects the category label corresponding to the problem category corresponding to the target abnormal problem from the displayed plurality of category labels.

As a possible implementation mode, in the test interface, a plurality of category labels can be displayed in a list option (drop-down box) mode, so that a tester can select a target category label through a list item, and the method is more convenient, quicker and more accurate.

It will be appreciated that there is a standardized, normalized understanding between the tester, developer and demander for the multiple category labels displayed, and the problem category indicated by each category label, so that the tester, developer and demander can all understand the same concept for the problem category indicated by each category label without understanding errors.

For example, the tester, the developer and the demander may jointly make a standardized problem classification in advance, that is, the tester, the developer and the demander may obtain abnormal problems occurring during the process of program development or program test, classify the abnormal problems, and determine the problem category (name) of each problem type, so as to obtain a standardized and normalized understanding of the abnormal problems.

And S203, generating a question list corresponding to the target abnormal question according to the acquired description content and the target question category.

Wherein, the description content comprises the specific explanation content of the target abnormal problem, and the question list is used for indicating the abnormal problem existing in the target program.

As a possible implementation manner, after determining the target problem category corresponding to the target abnormal problem, the tester may continue to input the description content of the target abnormal problem to describe the problem existing in the target program in detail.

Specifically, the tester may input text information, voice information, image information, and the like as description contents of the target abnormal problem, and generate a question sheet corresponding to the target abnormal problem. Therefore, when a developer or a demander views the question list, the target abnormal problem can be clearly determined by combining the target problem category, the text information, the voice information and the image information.

It should be noted that, in the whole test flow, the description of the target exception problem does not need to be independently run, and may be run through an existing test management platform. The description of the target abnormal problem is used as an indispensable step for program test (function), so that the quality and the efficiency of the generated problem list containing the description of the target abnormal problem are improved through the standardized processing of the description of the test problem.

For example, in the process of testing the target program, the tester finds a problem, classifies the category of the test problem, classifies and marks the test problem, stores the test problem, confirms the test problem by the developer, and processes the test problem by the developer, and all the steps can be completed through the test management platform.

The embodiment of the invention can accurately, comprehensively and normatively describe the problems found by the testers by standardizing the test problem description and establishing a set of standard modes for submitting the test problem description, thereby being more convenient for the developers to locate, understand and confirm whether the problems existing in the program are bugs or not, and simultaneously, the test problem description conforms to the classification requirements of the current industry on the test problems.

In the embodiment of the present invention, in the process of testing the target program through the test management platform, the target abnormal problem existing in the target program is determined first, and after the target abnormal problem existing in the target program is determined, the target abnormal problem is determined to be the target problem category according to the selection operation of the target category label for indicating the target problem category among the plurality of category labels for indicating the plurality of problem categories. Further, descriptive contents including specific explanation contents of the target abnormal problem are obtained, and a problem list used for indicating the target abnormal problem existing in the target program is generated according to the obtained descriptive contents and the target problem category. Therefore, when an abnormal problem existing in the program is determined, the problem category of the abnormal problem can be quickly marked through a plurality of category labels for indicating a plurality of target problem categories, and the problem list can be quickly generated by combining the acquired description content. The problem that the problem description of the tester has errors or the understanding of the problem description of the developer has deviation is solved without the need of the tester to subjectively describe the target abnormal problem. Therefore, in the process of testing the program, the quality of the generated question list can be improved, and the efficiency of program testing work is improved.

In one design, the plurality of category labels includes a plurality of major category labels and a plurality of subcategory labels, one major category label corresponding to at least one subcategory label, and the target category label includes a first label and a second label; in order to determine the target problem category corresponding to the target abnormal problem, as shown in fig. 3, the method in S202 provided in the embodiment of the present invention may specifically include the following steps S301 to S304.

S301, receiving a first operation of a user on a first label in the displayed plurality of main category labels.

Optionally, when the tester determines that the target abnormal problem exists in the target program, the tester may select and input the displayed multiple main category labels, so that the electronic device determines the main problem category corresponding to the target abnormal problem.

It is to be understood that the plurality of category labels include a plurality of main category labels and a plurality of sub-category labels, wherein one main category label corresponds to one main question category and one sub-category label corresponds to one sub-question category. That is, there is a one-to-one correspondence between the plurality of main category labels and the plurality of main question categories, and there is a one-to-one correspondence between the plurality of sub-category labels and the plurality of sub-question categories.

S302, responding to the first operation, and determining a main problem type corresponding to the target abnormal problem.

It can be understood that the main problem categories corresponding to the target abnormal problem are determined as follows: and determining the main problem category indicated by the first label as the main problem category corresponding to the target abnormal problem.

As a possible implementation manner, the plurality of category labels displayed in the test interface may be labels at a plurality of levels, and the example of the present application is illustrated as including two levels of labels (i.e., a main category label and a sub-category label).

It should be noted that a plurality of main category labels may be displayed in the test interface, before the tester does not perform a selection operation on the main category labels, a plurality of sub-category labels do not need to be displayed, and after the tester performs a selection operation on a certain main category label among the plurality of main category labels, at least one sub-category label corresponding to the certain main category label may be displayed.

It can be understood that at least one subcategory tag corresponding to one main category tag is used for further dividing the main problem category, so as to obtain more detailed category division and obtain a plurality of subcategory problems corresponding to the main problem category.

As a possible implementation manner, a tester may select and input a tag (i.e., a first tag) of a main problem category corresponding to a target abnormal problem, so that the electronic device determines the main problem category corresponding to the target abnormal problem and displays at least one sub-category tag corresponding to the first tag.

S303, receiving a second operation of the user on a second label in the displayed at least one sub-category label.

Further, after the tester performs selection input on the displayed multiple main category labels and determines the main problem category corresponding to the target abnormal problem, the tester may further perform selection input on at least one sub-category label corresponding to the main category label, so that the electronic device determines the sub-problem category corresponding to the target abnormal problem.

And S304, responding to the second operation, and determining the sub-problem type corresponding to the target abnormal problem.

And at least one sub-category label is a sub-category label corresponding to the first label.

It can be understood that the sub-problem categories corresponding to the target abnormal problem are determined as follows: and determining the sub-problem category indicated by the second label as the sub-problem category corresponding to the target abnormal problem.

As a possible implementation manner, after the tester performs a selection operation input on a first tag of the displayed multiple main category tags, the electronic device may be triggered to display at least one sub-category tag corresponding to the first tag in a form of a drop-down box.

Furthermore, the tester determines the sub-problem category corresponding to the target abnormal problem, and performs selection operation on a second tag in the displayed at least one sub-category tag, so that the electronic device determines the sub-problem category corresponding to the target abnormal problem.

For example, the interface problem may include a plurality of sub-problem categories, which may be specifically: text questions, graphics questions, symbolic questions, numeric format questions, and other questions.

In the embodiment of the invention, the problem categories can be divided into multiple stages, so that the specific problem categories corresponding to the target abnormal problems are determined by selecting the multiple stages of problem category labels, and the accuracy of determining the problem categories of the target abnormal problems is improved.

In one design, in order to generate a question list corresponding to a target abnormal question, as shown in fig. 4, the method in S203 provided in the embodiment of the present invention may specifically include the following steps S401 to S402.

S401, receiving a third operation of the user.

S402, responding to the third operation, generating description contents corresponding to the target abnormal problems, and obtaining a problem list corresponding to the target abnormal problems according to the target problem types.

The description content also comprises a correct result corresponding to the target abnormal problem. The third operation includes at least one of: text input operation, voice input operation and screenshot triggering operation.

As a possible implementation manner, the tester may trigger the electronic device to execute a screenshot function through a third operation, so as to capture an image including a target abnormal problem displayed in the screen, store and process the screenshot of the abnormal problem point, and mark a problem category.

As a possible implementation manner, a tester may input text information in a text input area in a test interface to describe, through the text information, a reason for a target abnormal problem considered by the tester and a correct result (an expected result) corresponding to the target abnormal problem considered by the tester; or the tester can perform voice input to describe the target abnormal problem in a voice form.

It should be noted that, for some special situations, in extreme cases, the abnormal problem cannot be described by the above method, and the problem ticket can be generated by maintaining the traditional description mode, that is, the operation and maintenance staff performs subjective cognition.

As a possible implementation manner, after determining a question category (category label) corresponding to the target abnormal question and receiving description content input by the tester, the electronic device may generate a question sheet corresponding to the target abnormal question according to the screenshot, the input text information, and the input voice information, that is, the question sheet may include the screenshot, the text, and the voice content.

Further, the tester can send the problem list corresponding to the target abnormal problem to the developer and the demander, so that the developer and the demander can determine whether the target abnormal problem is a bug or not, whether the target abnormal problem needs to be repaired or not, and the like.

For example, when displaying most monetary amounts in a banking system, such as U.S. dollars, RMB, etc., it is often desirable to display a small number of points, such as "$ 1000.00". But when the amount of the Japanese dollar is displayed, the amount has no decimal point, such as: "1000 yen". If the amount of money of the Japanese yen is found to display the display form of '1000.00 Japanese yen' in the process of testing the program, the test questions belong to the test question classification of one interface according to the classification standard, and specifically belong to the 'digital format' question in a plurality of sub-question categories (characters, graphs, digital formats and other) corresponding to the interface question. As shown in fig. 5, an interface question tag displayed in the test interface may be selected, so that the electronic device displays a plurality of sub-question categories in the form of drop-down boxes, and the tester further selects "digital format" to classify and record the questions. And the error problem displayed in the interface can be obtained through the screenshot form, and a problem list is generated. After a developer opens the question list, the specific situation described by the question list can be basically judged through the test steps, the question classification and the question screenshot, so that the question list can be quickly understood and the questions can be quickly repaired.

In the embodiment of the invention, a user can perform operations such as text input operation, voice input operation, screenshot triggering operation and the like, so that the electronic equipment generates description contents for indicating the target abnormal problem and an expected result corresponding to the target abnormal problem. And generating a question list corresponding to the target abnormal question based on the description content and the target question category. Thereby improving the quality and efficiency of generating the question list.

In one design, in order to obtain multiple problem categories, as shown in fig. 6, before S201 provided in the embodiment of the present invention, the following S501-S502 may be specifically included.

S501, a plurality of problem categories corresponding to a plurality of abnormal problems included in the software testing process are determined in advance.

The plurality of problem categories comprise a plurality of main problem categories and a plurality of sub problem categories, and one main problem category corresponds to at least one sub problem category; the plurality of main issue categories include at least one of: equivalence class problems, boundary value problems, interface problems, batch problems, and other problems.

As a possible implementation manner, the demander, the developer, and the tester may determine a plurality of problem categories corresponding to a plurality of abnormal problems in advance, for example, classify abnormal problems that have occurred (or have a high occurrence probability) in the process of testing the program to obtain a plurality of problem categories.

Specifically, the tester, the developer, and the demander can jointly make a standardized problem classification in advance, that is, the tester, the developer, and the demander can acquire abnormal problems that occur during program development or program test, manually classify the abnormal problems, and determine the problem category (name) of each type of problem, so as to obtain a standardized and normalized understanding of the abnormal problems.

Further, the problem range included in the plurality of problem categories can be further divided into a plurality of stages of problem categories, so that the efficiency of determining the problem category corresponding to the abnormal problem can be improved through the plurality of stages of problem categories.

It should be noted that the equivalence class problem can be understood as follows: the equivalence class partitioning divides all possible input data (valid and invalid) of a program into several equivalence classes. Then representative data is selected from each part and taken as a test case to be reasonably classified, and the test case is composed of representatives of effective equivalence classes and ineffective equivalence classes, so that the completeness and the representativeness of the test case are guaranteed.

The boundary value problem can be understood as: the boundary value analysis method is a black box test method for testing the input or output boundary value. In general, the boundary value analysis is complementary to the equivalence class classification, and in this case, the test case is derived from the boundary of the equivalence class.

The interface problem can be understood as: interface test (UI test for short) tests whether the layout of functional modules of the user interface is reasonable, the overall style is consistent, the placement positions of all controls conform to the use habits of customers, and also tests whether the interface operation is convenient, the navigation is simple and easy to understand, the usability of interface elements, whether the interface Chinese is correct, the name is unified, whether the interface is attractive, whether the combination of characters and pictures is perfect, and the like.

Batch problems can be understood as: for banking systems, bulk is primarily the generation of ledgers, checking of ledgers, and bulk transactions, such as: and (4) bearing, counting, collecting and paying, generating a report, exporting running data and the like.

The above problem description classification is the common division of current software functional testing specialties. Subclasses can be arranged under each class according to actual needs. The subclasses can be set according to the characteristics of the industry and the actual working requirements (for example, a bank pays attention to the accuracy of data and the reasonable and effective setting of digital boundaries, a music professional pays attention to the accuracy of musical notes, and decorative design is focused on the standard of figures, etc.), and the reasonable and effective setting of the subclasses plays a decisive role in describing and positioning problems. For convenience and convenience of description, a pull-down frame mode can be adopted in classification description.

It will be appreciated that the classification of test question descriptions is required to meet the normal practices of the industry and is only to combine test question descriptions with test question classifications to standardize them. The settings for the subclasses can be designed according to industry features and actual needs. Specifically, when the category labels are displayed in the interface, the category labels can be classified in a drop-down frame mode, so that the click is more convenient, quicker and more accurate, and the generated question sheet is easy to understand by developers.

S502, displaying a plurality of category labels corresponding to a plurality of problem categories in an interface of the test management platform.

As a possible implementation manner, when the electronic device runs the test management platform, a plurality of category labels corresponding to a plurality of predetermined problem categories may be displayed in the test interface, so that when an abnormal problem exists in the test program, the problem category corresponding to the abnormal problem may be determined through the plurality of displayed category labels.

Furthermore, the setting of the problem category (including the sub-problem category) of the test problem can be adjusted and modified according to the actual need, and the frame number of the screenshots included in the problem list meets the actual need, so that the developer can conveniently position and understand the test problem.

It can be understood that the implementation of the product functions described above for the test problems can be combined with a test management system to innovate a method for describing the test problems therein. The system comprises three functional modules of test problem description classification, test problem description storage and special scenario processing. The whole process of the test problem description is covered, so that the standardized processing of the test problem description under the general condition is ensured, and the traditional test problem description mode method under the special situation is also reserved.

In the embodiment of the invention, by adopting the method, the problem list generation method is provided, the test problem description is subjected to standardized processing, a set of standard test problem description submitting modes is established, the problems found by the testers can be accurately, comprehensively and normatively described, the positioning, understanding and confirming of the problems by the developers are more convenient, and meanwhile, the testers and the developers jointly approve the processing scheme. The test working quality and the working efficiency can be improved. The test problem description is normalized by the test problem classification method, so that the accuracy of the test problem description is improved, and the problem can be more conveniently understood by developers. The problem of in the actual work, face the same problem, different testers description mode, language custom etc. also differ, because of to submitting the difference in problem understanding to cause the phenomenon that developer's problem confirms and restores and delays. The gist of the invention is to standardize the problem description. The problem description mode approved by three parties, namely a tester, a developer and a demander, is standardized, and the accuracy of problem description and problem understanding is ensured, so that the working efficiency and the software development quality are further improved.

The scheme provided by the embodiment of the invention is mainly introduced from the perspective of a method. To implement the above functions, it includes hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiment of the present invention, a problem ticket generating apparatus may be divided into functional modules according to the above method examples, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. Optionally, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

Fig. 7 is a schematic structural diagram of a problem ticket generating apparatus according to an embodiment of the present invention. As shown in fig. 7, a question list generating apparatus 100 is used to improve the quality of a generated question list and the efficiency of a program test operation in a process of testing a program, for example, to execute a question list generating method shown in fig. 2. The question ticket generating apparatus 100 includes: a determination unit 1001, a generation unit 1002, a reception unit 1003, and a display unit 1004.

A determination unit 1001 configured to determine a target exception problem existing in a target program; for example, as shown in fig. 2, the determination unit 1001 may be configured to execute the step in S201.

A determining unit 1001, further configured to determine, according to a selection operation on a target category tag among the multiple category tags, a target problem category corresponding to the target abnormal problem; a plurality of category labels for indicating a plurality of issue categories, a target category label for indicating a target issue category; for example, as shown in fig. 2, the determination unit 1001 may be configured to execute the step in S202.

A generating unit 1002, configured to generate a question sheet corresponding to the target abnormal question according to the obtained description content and the target question category; the description content includes specific explanation content of the target abnormal problem, and the question list is used for indicating the abnormal problem existing in the target program. For example, as shown in fig. 2, the generating unit 1002 may be configured to execute the step in S203.

Optionally, the plurality of category tags include a plurality of main category tags and a plurality of sub-category tags, one main category tag corresponds to at least one sub-category tag, and the target category tag includes a first tag and a second tag; a receiving unit 1003, configured to receive a first operation performed by a user on a first tab of the displayed plurality of main category tabs; for example, as shown in fig. 3, the receiving unit 1003 may be configured to execute the step in S301.

The determining unit 1001 is further configured to determine, in response to the first operation, a main problem category corresponding to the target abnormal problem; for example, as shown in fig. 3, the determination unit 1001 may be configured to execute the step in S302.

The receiving unit 1003 is further configured to receive a second operation performed by the user on a second tab of the displayed at least one sub-category tab; for example, as shown in fig. 3, the receiving unit 1003 may be configured to execute the step in S303.

The determining unit 1001 is further configured to determine, in response to the second operation, a sub-problem category corresponding to the target abnormal problem; at least one subcategory label is a subcategory label corresponding to the first label. For example, as shown in fig. 3, the determination unit 1001 may be configured to execute the step in S304.

Optionally, the receiving unit 1003 is further configured to receive a third operation of the user; the third operation includes at least one of: text input operation, voice input operation and screenshot triggering operation; for example, as shown in fig. 4, the receiving unit 1003 may be used to execute the step in S401.

The generating unit 1002 is specifically configured to generate, in response to the third operation, description content corresponding to the target abnormal question, and obtain a question list corresponding to the target abnormal question according to the category of the target question; the description also includes correct results corresponding to the target exception problem. For example, as shown in fig. 4, the generating unit 1002 may be configured to execute the step in S402.

Optionally, the determining unit 1001 is further configured to determine in advance a plurality of problem categories corresponding to a plurality of abnormal problems included in the software testing process; the plurality of question categories comprise a plurality of main question categories and a plurality of sub-question categories, and one main question category corresponds to at least one sub-question category; the plurality of main issue categories include at least one of: equivalence class problems, boundary value problems, interface problems, batch problems; for example, as shown in fig. 6, the determination unit 1001 may be configured to execute the step in S501.

The display unit 1004 is configured to display a plurality of category labels corresponding to a plurality of question categories on the interface of the test management platform. For example, as shown in fig. 6, the display unit 1004 may be used to perform the step in S502.

In the case of implementing the functions of the integrated modules in the form of hardware, the embodiment of the present invention provides another possible structural schematic diagram of the electronic device related to the above embodiment. As shown in fig. 8, an electronic device 70 is used for efficiently evaluating a product for iterative update, in which adjustment of product content causes a change in product activity, for example, for executing a problem sheet generation method shown in fig. 2. The electronic device 70 includes a processor 701, a memory 702, and a bus 703. The processor 701 and the memory 702 may be connected by a bus 703.

The processor 701 is a control center of the communication apparatus, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 701 may be a Central Processing Unit (CPU), other general-purpose processors, or the like. Wherein a general purpose processor may be a microprocessor or any conventional processor or the like.

For one embodiment, processor 701 may include one or more CPUs, such as CPU 0 and CPU 1 shown in FIG. 8.

The memory 702 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, 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.

As a possible implementation, the memory 702 may be present separately from the processor 701, and the memory 702 may be connected to the processor 701 via the bus 703 for storing instructions or program code. The processor 701 can implement the problem ticket generating method provided by the embodiment of the present invention when calling and executing the instructions or program codes stored in the memory 702.

In another possible implementation, the memory 702 may also be integrated with the processor 701.

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

It is to be noted that the structure shown in fig. 8 does not constitute a limitation of the electronic apparatus 70. In addition to the components shown in FIG. 8, the electronic device 70 may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.

As an example, in connection with fig. 7, the determining unit 1001 and the generating unit 1002 in the electronic device implement the same functions as the processor 701 in fig. 8.

Optionally, as shown in fig. 8, the electronic device 70 provided in the embodiment of the present invention may further include a communication interface 704.

A communication interface 704 for connecting with other devices through a communication network. The communication network may be an ethernet network, a radio access network, a Wireless Local Area Network (WLAN), etc. The communication interface 704 may include a receiving unit for receiving data, and a transmitting unit for transmitting data.

In one design, in the electronic device provided by the embodiment of the present invention, the communication interface may be further integrated in the processor.

Through the above description of the embodiments, it is clear for a person skilled in the art that, for convenience and simplicity of description, only the division of the above functional units is illustrated. In practical applications, the above function allocation can be performed by different functional units according to needs, that is, the internal structure of the device is divided into different functional units to perform all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

The embodiment of the present invention further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed by a computer, the computer executes each step in the method flow shown in the above method embodiment.

Embodiments of the present invention provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform a method of generating a question list in the above-described method embodiments.

The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, and a hard disk. Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), registers, a hard disk, an optical fiber, a portable Compact disk Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any other form of computer-readable storage medium, in any suitable combination, or as appropriate in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). In embodiments of the invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Since the electronic device, the computer-readable storage medium, and the computer program product in the embodiments of the present invention may be applied to the method described above, for technical effects obtained by the method, reference may also be made to the method embodiments described above, and details of the embodiments of the present invention are not repeated herein.

The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope of the present invention are intended to be covered by the scope of the present invention.

Claims

1. A method for generating a question sheet, the method comprising:

determining a target exception problem existing in a target program;

determining a target problem category corresponding to the target abnormal problem according to the selection operation of a target category label in a plurality of category labels; the plurality of category labels are used for indicating a plurality of question categories, and the target category label is used for indicating the target question category;

generating a question list corresponding to the target abnormal question according to the acquired description content and the target question category; the description content comprises specific explanation content of the target abnormal problem, and the problem ticket is used for indicating the abnormal problem existing in the target program.

2. The method of claim 1, wherein the plurality of category labels comprises a plurality of major category labels and a plurality of minor category labels, one major category label corresponding to at least one minor category label, and wherein the target category label comprises a first label and a second label;

the determining a target problem category corresponding to the target abnormal problem according to the selection operation of the target category label in the plurality of category labels includes:

receiving a first operation of a user on a first label in the plurality of displayed main category labels;

responding to the first operation, and determining a main problem category corresponding to the target abnormal problem;

receiving a second operation of the user on a second tag in the displayed at least one sub-category tag;

responding to the second operation, and determining a sub-problem category corresponding to the target abnormal problem; the at least one subcategory tag is a subcategory tag corresponding to the first tag.

3. The method according to claim 2, wherein the generating a question sheet corresponding to the target abnormal question according to the obtained description content and the target question category includes:

receiving a third operation of the user; the third operation comprises at least one of: text input operation, voice input operation and screenshot triggering operation;

responding to the third operation, generating description content corresponding to the target abnormal problem, and obtaining a problem list corresponding to the target abnormal problem according to the target problem category; the description content also comprises a correct result corresponding to the target abnormal problem.

4. The method of claim 1, wherein prior to determining a target exception problem in the target program, the method further comprises:

predetermining a plurality of problem categories corresponding to a plurality of abnormal problems included in the software testing process; the plurality of question categories comprise a plurality of main question categories and a plurality of sub-question categories, and one main question category corresponds to at least one sub-question category; the plurality of main issue categories include at least one of: equivalence class problems, boundary value problems, interface problems, batch problems;

and displaying a plurality of category labels corresponding to the plurality of problem categories in an interface of the test management platform.

5. A question ticket generating apparatus, characterized by comprising: a determination unit and a generation unit;

the determining unit is used for determining a target abnormal problem existing in a target program;

the determining unit is further configured to determine a target problem category corresponding to the target abnormal problem according to a selection operation on a target category tag of the plurality of category tags; the plurality of category labels are used for indicating a plurality of question categories, and the target category label is used for indicating the target question category;

the generating unit is used for generating a question list corresponding to the target abnormal question according to the acquired description content and the target question category; the description content comprises specific explanation content of the target abnormal problem, and the problem ticket is used for indicating the abnormal problem existing in the target program.

6. The apparatus of claim 5, wherein the plurality of category labels comprises a plurality of main category labels and a plurality of subcategory labels, one main category label corresponding to at least one subcategory label, and the target category label comprises a first label and a second label;

the question sheet generating apparatus further includes: a receiving unit;

the receiving unit is used for receiving a first operation of a user on a first label in the plurality of displayed main category labels;

the determining unit is further configured to determine, in response to the first operation, a main problem category corresponding to the target abnormal problem;

the receiving unit is further used for receiving a second operation of the user on a second tag in the displayed at least one sub-category tag;

the determining unit is further configured to determine, in response to the second operation, a sub-problem category corresponding to the target abnormal problem; the at least one sub-category label is a sub-category label corresponding to the first label.

7. The question sheet generating apparatus according to claim 6, wherein the receiving unit is further configured to receive a third operation by a user; the third operation comprises at least one of: text input operation, voice input operation and screenshot triggering operation;

the generating unit is specifically configured to generate, in response to the third operation, description content corresponding to the target abnormal question, and obtain a question list corresponding to the target abnormal question according to the category of the target question; the description content also comprises a correct result corresponding to the target abnormal problem.

8. The question ticket generating apparatus according to claim 5, characterized in that the question ticket generating apparatus further comprises: a display unit;

the determining unit is further configured to determine in advance the plurality of problem categories corresponding to a plurality of abnormal problems included in the software testing process; the plurality of question categories comprise a plurality of main question categories and a plurality of sub-question categories, and one main question category corresponds to at least one sub-question category; the plurality of major issue categories include at least one of: equivalence class problems, boundary value problems, interface problems, batch problems;

the display unit is used for displaying a plurality of category labels corresponding to the plurality of problem categories in an interface of the test management platform.

9. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computer, cause the computer to perform a method of problem ticket generation as claimed in any one of claims 1-4.

10. An electronic device, comprising: a processor and a memory; wherein the memory is configured to store one or more programs, the one or more programs including computer executable instructions, which when executed by the electronic device, cause the electronic device to perform a method of generating a question list as claimed in any one of claims 1 to 4.