CN115454828A

CN115454828A - Online case testing method, equipment and storage medium

Info

Publication number: CN115454828A
Application number: CN202211025882.8A
Authority: CN
Inventors: 邱小雨
Original assignee: Shenzhen Woxiang Technology Co ltd
Current assignee: Shenzhen Woxiang Technology Co ltd
Priority date: 2022-08-25
Filing date: 2022-08-25
Publication date: 2022-12-09

Abstract

The invention discloses an online case testing method, online case testing equipment and a storage medium, and belongs to the technical field of software testing. The online use case testing method comprises the following steps: combing a case outline of a product to be tested, and establishing a case library of the product to be tested according to the case outline and a case scene; receiving a test case compiling request initiated by a user side, and displaying an adaptive case compiling interface according to the test case compiling request; receiving compiling information input by a user side based on the use case compiling interface, compiling use case elements in the use case compiling interface according to the compiling information, and generating a primary test use case; and testing and accepting according to the primary test case to generate a final version case, and filing the final version case into the case library. The invention solves the technical problems that the prior art is lack of standardization in the case compiling process, and the problem is difficult to find quickly in the testing process, so that the product delivery efficiency is low.

Description

Online case testing method, equipment and storage medium

Technical Field

The invention relates to the technical field of software testing, in particular to an online use case testing method, online use case testing equipment and an online use case testing storage medium.

Background

With the rapid development of the software industry, various types of software emerge endlessly, software development and testing are required to meet customer requirements and ensure the quality of the software, and the core of the software development and testing is the compiling and testing of use cases. The writing of the use cases mostly depends on the professional level and experience of a writer, the use cases designed by human dimensionality have large difference, the problems and links with the problems are difficult to find quickly in the process of developing self-test, extracting test and testing acceptance, and the product delivery efficiency is low.

The above is only for the purpose of assisting understanding of the technical solution of the present invention, and does not represent an admission that the above is the prior art.

Disclosure of Invention

The invention mainly aims to provide an online case testing method, online case testing equipment and an online case testing storage medium, and aims to solve the technical problem that the existing case testing method is difficult to find problems quickly in case compiling and testing processes, so that the delivery efficiency is low.

In order to achieve the above object, the present invention provides an online use case testing method, which includes:

combing a case outline of a product to be tested, and setting the outline level and the case scene of a test case in a grading manner based on outline items of the case outline;

establishing a case library of the product to be tested according to the outline level and the case scene;

receiving a test case compiling request initiated by a user side, and displaying an adaptive case compiling interface according to the test case compiling request; the use case elements of the use case writing interface comprise: one or more items of case numbers, belonged modules, case titles, version identifiers, test points, input data, operation steps and expected results;

receiving writing information input by a user side based on the use case writing interface, writing use case elements in the use case writing interface according to the writing information, and generating a primary test use case;

and testing and accepting the primary test case to generate a final version case, and filing the final version case into the case library.

Optionally, the step of combing the use case schema of the product to be tested, and based on the schema entries of the use case schema, setting the schema level and the use case scenario of the test use case in a hierarchical manner includes:

combing the use case outline and dividing the use case outline into different business modules according to the business type of the product to be tested;

establishing a first-level outline under each business module according to the function type of the product to be tested;

establishing a secondary outline under each primary outline according to the use case scene type of the product to be tested; the first level outline and the second level outline are used as outline items;

and setting the use case scene of the product to be tested in the adapted secondary outline, and adding a scene summary to the use case scene to be used as a scene test point.

Optionally, the step of establishing a use case library of the product to be tested according to the outline level and the use case scenario includes:

setting a use case library directory according to the outline level of the use case outline, and establishing an association relation between the use case library directory and the use case outline;

adding case test points to the test cases of the products to be tested, and identifying target scene test points of target case scenes consistent with the case test points in the second-level outline according to the incidence relation;

determining the scene position of the target scene test point in the secondary outline, and identifying the position corresponding to the scene position in the use case library directory as a use case position;

and setting the test cases of the products to be tested at the case positions, and establishing a case library of the products to be tested.

Optionally, the use case compiling interface includes a newly added use case compiling interface and an optimized use case compiling interface, the test use case compiling request is packaged with an application scene and a requirement test point, and the step of displaying the adapted use case compiling interface according to the test use case compiling request includes:

if the application scene of the test case compiling request is a pure new test scene, displaying a new case compiling interface;

if the application scene of the test case compiling request is an optimized test scene, extracting and analyzing the required test points in the test case compiling request, screening target case test points consistent with the required test points, copying the test cases corresponding to the target case test points, generating case copies, identifying case element information of the case copies, inputting the case element information to a preset optimized case compiling interface, and displaying the optimized case compiling interface.

Optionally, the step of receiving, based on the use case authoring interface, authoring information input by a user side, and authoring, according to the authoring information, use case elements in the use case authoring interface, and generating a primary test case includes:

if the case compiling interface is the newly added case compiling interface, extracting and analyzing case elements in the compiling information input by the user side for case compiling to generate a primary test case;

if the case compiling interface is the optimized case compiling interface, case elements in compiling information input by a user side are extracted and analyzed for case compiling, a primary test case is generated, and test case graying except the case copy in the case library is carried out.

Optionally, after the step of generating the preliminary test case, the method further includes:

receiving a use case evaluation request initiated by a user side, and displaying an adaptive use case evaluation interface according to the use case evaluation request; the review elements of the use case review interface comprise: reviewing roles, reviewing results, reviewing opinions and necessary scenes;

receiving review information input by a user terminal, inputting the review information into review elements of the use case review interface, updating the use case review interface and displaying the updated use case review interface;

and according to the review opinions in the updated case review interface, the primary test case is perfected, and a necessary test scene in the primary test case is determined.

Optionally, after the step of completing the preliminary test case according to the review information and determining a scenario to be tested in the preliminary test case, the method further includes:

receiving a development self-test request initiated by a user side, and displaying an adaptive development self-test interface; the self-testing elements for developing the self-testing interface comprise: a necessary test scene and a self test result;

carrying out development self-test on a preset product according to the development self-test request and a necessary test scene in the primary test case;

if the product passes the development self-test of the necessary scene, marking the necessary scene as a self-test pass, and outputting the result of the development self-test to the development self-test interface;

if the product does not pass the development self-test of the necessary test scene, marking the necessary test scene that the product does not pass the development self-test, and outputting the result of the development self-test to the development self-test interface; and correcting the product according to the development self-test result to generate a corrected product, and performing the development self-test on the corrected product.

Optionally, the step of performing test acceptance according to the primary test case to generate a final version case, and filing the final version case into the case library includes:

receiving a test acceptance request initiated by a user side, and displaying an adaptive test acceptance interface; the acceptance elements of the test acceptance interface comprise: use case scenes and acceptance results;

testing and accepting the product according to the testing and accepting request and the case scene in the primary test case;

if the product passes the test acceptance of the case scene, marking the case scene that the acceptance passes, and outputting the result of the test acceptance to the test acceptance interface;

if the product does not pass the test acceptance of the case scene, marking the case scene that the acceptance does not pass, and outputting the result of the test acceptance to the test acceptance interface; repairing the product according to the test acceptance result to generate a repaired product, and performing the test acceptance on the repaired product;

and when all the marks of the use case scene pass, generating a final version use case.

The invention also provides an online use case testing device, which comprises: the system comprises a memory, a processor and an online use case testing program which is stored on the memory and can run on the processor, wherein the online use case testing program is configured to realize the steps of the online use case testing method.

The invention further provides a storage medium which is a computer-readable storage medium, wherein the computer-readable storage medium stores an online use case test program, and the online use case test program is executed by a processor to realize the steps of the online use case test method.

The invention discloses an online case testing method, equipment and a storage medium, by combing a case outline of a product to be tested, hierarchically setting outline levels and case scenes of a test case based on outline items of the case outline, the structure level of the use case is clearer, further establishing a case library of the product to be tested according to the outline levels and the case scenes, realizing the visualization of test case compiling and the rapid positioning of the test case by the mutual correlation of the case outline and the case library, further receiving a test case compiling request initiated by a user terminal, displaying an adaptive case compiling interface according to the test case compiling request, and carrying out case compiling according to compiling information received by the case compiling interface and case elements in the case compiling interface, the primary test case is generated, visualization of case compiling is further achieved, improvement of normalization of case compiling is facilitated, case review is conducted on the primary test case, development self-test and test acceptance are conducted according to the primary test case, test contents and test results are displayed in a corresponding interface in real time, visualization of a case test process is achieved, repeated testing caused by the fact that problems are complex in the case test process and difficult to find quickly is avoided, delivery efficiency is further improved, a final version case is generated, the final version case is filed in the case base, case loss caused by frequent version iteration is avoided, and visualization of the case compiling and the test process is further achieved.

Drawings

FIG. 1 is a schematic structural diagram of an online use case testing device of a hardware operating environment according to an embodiment of the present invention;

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

fig. 3 is a schematic diagram of a case outline of an online case testing method according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a use case library of an online use case testing method according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a use case compiling interface of an online use case testing method according to an embodiment of the present invention;

FIG. 6 is a detailed flowchart of an embodiment of step S30 in FIG. 2;

FIG. 7 is a schematic diagram of a use case review interface of an online use case testing method according to an embodiment of the present invention;

fig. 8 is a detailed flowchart of an embodiment of step S50 in fig. 2.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

Referring to fig. 1, fig. 1 is a schematic structural diagram of an online use-case test device of a hardware operating environment according to an embodiment of the present invention.

As shown in fig. 1, the online use case testing device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) Memory, or a Non-Volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.

Those skilled in the art will appreciate that the configuration shown in FIG. 1 does not constitute a limitation of an on-line use case testing device, and may include more or fewer components than shown, or some components in combination, or a different arrangement of components.

As shown in fig. 1, a memory 1005, which is a storage medium, may include an operating system, a data storage module, a network communication module, a user interface module, and an online use case test program therein.

In the online use case testing device shown in fig. 1, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the online use case test device of the present invention may be arranged in the online use case test device, and the online use case test device calls the online use case test program stored in the memory 1005 through the processor 1001 and executes the following operations:

combing a case outline of a product to be tested, and setting the outline level and case scene of a test case in a grading manner based on the outline items of the case outline;

receiving a test case compiling request initiated by a user side, and displaying an adaptive case compiling interface according to the test case compiling request; the use case elements of the use case writing interface comprise: one or more of case number, module, case title, version identification, test point, input data, operation step and expected result;

receiving compiling information input by a user side based on the use case compiling interface, compiling use case elements in the use case compiling interface according to the compiling information, and generating a primary test use case;

and testing and accepting according to the primary test case to generate a final version case, and filing the final version case into the case library.

Further, the step of carding the use case outline of the product to be tested, and setting the outline level and the use case scene of the test use case in a grading way based on the outline item of the use case outline comprises the following steps:

combing and dividing the use case outline into different business modules according to the business type of the product to be tested;

Further, the step of establishing a use case library of the product to be tested according to the outline level and the use case scene comprises the following steps:

setting a use case library catalogue according to the outline level of the use case outline, and establishing an association relation between the use case library catalogue and the use case outline;

and setting the test case of the to-be-tested product at the case position, and establishing a case library of the to-be-tested product.

Further, the use case compiling interface comprises a newly added use case compiling interface and an optimized use case compiling interface, the test use case compiling request is packaged with an application scene and a requirement test point, and the step of displaying the adaptive use case compiling interface according to the test use case compiling request comprises the following steps:

if the application scene of the test case compiling request is an optimized test scene, extracting and analyzing required test points in the test case compiling request, screening target case test points consistent with the required test points, copying test cases corresponding to the target case test points, generating case copies, identifying case element information of the case copies, inputting the case element information to a preset optimized case compiling interface, and displaying the optimized case compiling interface.

Further, the step of receiving the writing information input by the user side based on the use case writing interface, and writing the use case elements in the use case writing interface according to the writing information, and generating the primary test case includes:

and if the case compiling interface is the optimized case compiling interface, extracting and analyzing case elements in compiling information input by a user side to carry out case compiling, generating a primary test case, and carrying out case graying on the test cases except the case copy in the case library.

Further, the processor 1001 may call the online use case test program stored in the memory 1005, and further perform the following operations:

after the step of generating the preliminary test case, the method further comprises the following steps:

Further, the processor 1001 may call an online use case test program stored in the memory 1005, and further perform the following operations:

after the step of completing the primary test case according to the review information and determining a necessary test scenario in the primary test case, the method further comprises the following steps:

receiving a development self-test request initiated by a user side, and displaying an adaptive development self-test interface; the self-test elements for developing the self-test interface comprise: a necessary test scene and a self test result;

if the product passes the development self-test of the necessary test scene, marking the necessary test scene that the self-test passes, and outputting the result of the development self-test to the development self-test interface;

if the product does not pass the development self-test of the necessary test scene, marking the necessary test scene that the development self-test does not pass, and outputting the result of the development self-test to the development self-test interface; and correcting the product according to the development self-test result to generate a corrected product, and performing the development self-test on the corrected product.

Further, the step of performing test acceptance according to the primary test case to generate a final version case, and filing the final version case into the case library includes:

receiving a test acceptance request initiated by a user side, and displaying an adaptive test acceptance interface; the acceptance elements of the test acceptance interface comprise: case scene and acceptance result;

An embodiment of the present invention provides an online use case testing method, and referring to fig. 2, in a first embodiment of the online use case testing method, the online use case testing method includes:

s10, combing the use case outline of the product to be tested, and setting the outline level and the use case scene of the test use case in a grading way on the basis of the outline items of the use case outline.

In this embodiment, it should be noted that an execution main body of the online use case testing method is a network device, and the network device may be connected to a user device through, but not limited to, an internet, a local area network, or a physical connection, receive information input by the user device, write a test case, test the test case, and output a test result and a final version of the test case in real time, thereby implementing visualization of use case writing and testing processes.

The user equipment is a terminal capable of being connected with a network, such as a mobile phone, a notebook computer, a desktop computer and an intelligent bracelet; the user equipment and the network equipment are connected with each other in a manner of but not limited to Internet, local area network and physical connection; users of the user equipment include writers, testers, reviewers, and the like.

The network device may be a conventional server, a cloud server, or the like, and is not limited herein.

In order to assist in understanding the above technical solutions, a specific schematic diagram of a use case outline is used for the following auxiliary description, with reference to fig. 3, one column in fig. 3 is a specific outline entry, and fig. 3 totally contains 5 outline entries, which are an organization architecture entry, a login logout entry, a navigation frame entry, a login reporting logout entry, and a navigation menu top information entry in sequence from left to right; the modules, the first level schema and the second level schema in fig. 3 are 3 different schema levels; the module is a business module, and the organization architecture is a specific business type; the login, logout and navigation frames in the first-level outline are specific function types; and the login, report, logout, navigation menu and top information in the second-level outline are the specific scene types.

Combing the use case outline of the product to be tested, wherein the product to be tested is different software products needing to be tested; the case outline is a content key point of system arrangement which is established according to the service type, the function type, the scene type and the like of the product to be tested and is convenient for the management, the searching and the use of the case. According to the business type of the software product, combing and dividing the use case outline into different business modules; the service type is classified according to different transactions that the software product needs to process, and may be an organization architecture type, a system configuration type, a log record type, and the like, which is not limited herein. On the basis of the business module, a first-level outline is established according to different function types of products to be tested, wherein the function types include but are not limited to login and logout, a navigation frame, an organization, roles and the like. And establishing a secondary outline according to the case scene type of the product to be tested on the basis of the primary outline, wherein the case scene is all test scenes compiled based on the requirement of the product to be tested, and the case scene type comprises but is not limited to login, report, logout and the like. And setting all use case scenes of the product to be tested in the adapted secondary outline so as to finish the combing and establishing of the use case outline.

The case scenarios are all test scenarios written based on the requirements of the product to be tested.

The test cases are descriptions of how the system reacts to external requests in software engineering or system engineering, and are a technology for acquiring requirements by using scenes, and each test case contains one or more case scenes.

In this embodiment, the schema level and schema items of the corresponding use case schema are sorted according to the service type, the function type and the use case scene type of the product to be tested, and all use case scenes of the product to be tested are set in the adapted secondary schema, thereby completing the establishment of the use case schema. By combing and establishing the product use case outline, the hierarchy of the use case structure related to the product is clearer, the subsequent use case compiling and testing process is more visual, and the visualization of the use case compiling and testing process is further realized.

Optionally, the step S10 of combing the use case outline of the product to be tested, and the step of setting the outline level and the use case scene of the test use case hierarchically based on the outline item of the use case outline includes:

and S11, combing and dividing the use case outline into different business modules according to the business type of the product to be tested.

In some embodiments, referring to fig. 3, according to a service type of a product to be tested, a use case schema is combed and divided into different service modules, where the service type is classified according to different transactions that need to be processed by the software product. For example, the service types of the products to be tested include: organizing an architecture class, a system configuration class and a log record class, and correspondingly dividing the service modules of the use case schema into: the system comprises an organization architecture module, a system configuration module and a logging module.

And S12, establishing a primary outline under each business module according to the function type of the product to be tested.

In some embodiments, referring to fig. 3, different business modules are sorted and divided according to the business types of the products to be tested, and on the basis of the business modules, a first-level schema is established according to the function types of the products to be tested, where the function types are all different functions included in the products to be tested. For example, the service type of the product to be tested is an organizational structure type, and the function types include: and (4) a log-in and log-out function, a navigation frame function, an organization function and a role function, and then the use case outline is continuously combed into a log-in and log-out first-level outline, a navigation frame first-level outline, an organization first-level outline and a role first-level outline in the organization architecture module.

S13, establishing a secondary outline under each primary outline according to the case scene type of the product to be tested; the primary schema and the secondary schema are used as schema items.

In some embodiments, referring to fig. 3, different service modules are sorted and divided according to the service types of the products to be tested, a primary schema is established according to the function types of the products to be tested on the basis of the service modules, a secondary schema is established according to the use case scene types of the products to be tested on the basis of the primary schema, and the use case scenes are all test scenes written based on the requirements of the products to be tested. For example, the service type of the product to be tested is an organization architecture type, the function type is login and logout, and the use case scene type of the product to be tested includes: logging in, reporting and logging out, the steps are continuously divided into the following steps under a first-level logging-out outline in the organizational structure module: logging in the second level outline, reporting the second level outline and logging out the second level outline.

And S14, setting the case scene of the product to be tested in the adapted secondary outline, and adding a scene summary to the case scene to be used as a scene test point.

In some embodiments, referring to fig. 3, after the outline level and the outline items of the use case outline of the product to be tested are combed, the use case scene of the product to be tested is set in the adapted secondary outline. For example, if the case scenario of the product to be tested belongs to a login class for startup login, setting the case scenario for startup login under an organization architecture module of a case schema, logging in and logging out a login secondary schema in a primary schema, and adding a scenario summary to the case scenario for startup login, for example, adding a scenario summary: and starting a site initialization progress guide in the cloud dog environment, taking the scene summary as a scene test point, and completing the establishment of the use case outline. The test points are the test key point descriptions with the minimum granularity, namely core test points, after the function decomposition is carried out on the tested scene or use case, and the test points comprise the scene test points, the use case test points, the requirement test points and the like mentioned in the embodiment of the invention.

In this embodiment, the schema level and schema items of the corresponding use case schema are sorted according to the service type, the function type and the use case scene type of the product to be tested, and all use case scenes of the product to be tested are set in the adaptive secondary schema, thereby completing the establishment of the use case schema. By combing and establishing the use case outline of the product, the hierarchy of the use case structure related to the product is clearer, the writing process of the subsequent use case is more visual, and the visualization of the writing process of the use case is further realized.

And S20, establishing a use case library of the product to be tested according to the outline level and the use case scene.

In some embodiments, a corresponding use case library catalogue is set according to the level of the schema in the sorted use case schema, and the use case library catalogue is a name of a use case which is listed according to a certain sequence for examination; and establishing an association relation between the case library directory and the case schema to realize the mutual association of the case library directory entries and the schema entries of the case schema, and quickly positioning the case library to the corresponding test case through the schema. And on the basis of the case library catalogue, arranging the test case of the product to be tested in an adaptive position, thereby establishing a case library of the product to be tested.

In the embodiment, the corresponding case library is established according to the case outline, the association relation between the case outline and the case library catalogue is established, the case outline and the case library are associated with each other, the corresponding test case can be quickly positioned through the case outline, the compiling process of the case is more convenient and visual, and the visualization of the case compiling process is further realized.

Optionally, the step S20 of establishing a use case library of the product to be tested according to the outline level and the use case scenario includes:

and S21, setting a use case library directory according to the outline level of the use case outline, and establishing an association relation between the use case library directory and the use case outline.

In order to assist understanding of the above technical solutions, a specific use case library schematic diagram is used for assisting description, and referring to fig. 4, the organization architecture use cases, the system configuration use cases and the log record use cases in the first column in fig. 4 are first-level directories in the use case library directory, the login logout use cases, the navigation framework use cases, the role use cases, the template use cases and the organization user use cases in the second column are second-level directories in the use case library directory, and the login use cases, the report use cases and the logout use cases in the third column are third-level directories in the use case library directory.

And setting a corresponding use case library catalogue according to the outline level in the combed use case outline, for example, if the module of the use case outline has an organizational structure module, setting an organizational structure use case primary catalogue corresponding to the primary catalogue in the use case library catalogue. The case library directory is a list of cases listed in a certain order for examination. And further establishing an association relationship between the case library catalog and the case schema, establishing an association relationship between a module in the case schema and a first-level catalog in the case library, establishing an association relationship between the first-level schema in the case schema and a second-level catalog in the case library, establishing an association relationship between the second-level schema in the case schema and a third-level catalog in the case library, and realizing the mutual association between the case library and the case schema. For example, the organizational structure module in the case schema and the organizational structure in the case library establish an association relationship with the case primary directory, and the login and logout case primary schema in the case schema and the login and logout case secondary directory in the case library establish an association relationship.

And S22, adding case test points to the test cases of the products to be tested, and identifying target scene test points of target case scenes consistent with the case test points in the second-level outline according to the incidence relation.

In some embodiments, case test points are added to the test case of the product to be tested, target scene test points of a target case scene consistent with the case test points in the second-level outline of the case outline are identified according to the incidence relation, and the position of the test case in the case library is determined according to the positions of the target scene test points, so that the establishment of the case library is completed. For example, the case test points of the test case are: the cloud dog environment starts a site initialization progress guide, identifies an organization architecture module of the case outline according to the incidence relation between the case outline and the case library catalogue, logs in and logs out the first-level outline, and logs in the second-level outline, wherein the scene test points of the log-in case scene are as follows: and starting a site initialization progress guide in a cloud dog environment, wherein the site initialization progress guide is consistent with the use case test point, and the login use case scene is a target use case scene.

And S23, determining the scene position of the target scene test point in the secondary outline, and identifying the position corresponding to the scene position in the use case library catalogue as a use case position.

In some embodiments, according to the incidence relation between the use case outline and the use case library catalogue, identifying a target scene test point of a target use case scene consistent with the use case test point in a secondary outline of the use case outline so as to determine a scene position of the target test point in the secondary outline, wherein the scene position is a position of a certain use case scene in a certain secondary outline of the use case outline; and then identifying the position corresponding to the scene position in the case library directory as a case position, wherein the case position is the position of a certain test case in a certain third-level directory in the case library. For example, the case test points of the test case are: the cloud dog environment starts a site initialization progress guide, identifies an organization architecture module of the use case schema according to the incidence relation between the use case schema and the use case library catalogue, logs in and logs out the first-level schema, and the scene test points of the log-in use case scene in the second-level schema are as follows: and starting a site initialization progress guide in the cloud dog environment, and identifying the login case position in the logged-out case as the case position under the condition that the site initialization progress guide is consistent with the case test point.

And S24, setting the test case of the product to be tested at the case position, and establishing a case library of the product to be tested.

In some embodiments, the case positions of the test cases in the case library directory are identified and determined through the incidence relation between the case schema and the case library directory, all the test cases are arranged in the corresponding case positions according to categories, and then the establishment of the case library for the product to be tested is achieved.

In the embodiment, a case library catalogue is set according to the outline level of a case outline, an association relationship between the case library catalogue and the case outline is established, the case outline and the case library are associated with each other, case test points are added to test cases of a product to be tested, scene test points consistent with the case test points are identified through the association relationship, the positions of the scene test points and the positions in the case library catalogue are determined to be case positions, and all the test cases are set in corresponding case positions according to categories, so that the establishment of the case library of the product to be tested is realized. The corresponding test cases can be quickly positioned through the case schema, the case structure hierarchy is clearer due to the establishment of the case library, the centralized maintenance of case versions is facilitated, the searching and compiling processes of the use cases are more convenient and visual, and the visualization of the case compiling process is further realized.

Step S30, receiving a test case compiling request initiated by a user side, and displaying an adaptive case compiling interface according to the test case compiling request; the use case elements of the use case writing interface comprise: one or more of a use case number, a module to which the use case belongs, a use case title, a version identifier, a test point, input data, an operation step, and an expected result.

In some embodiments, the network device receives a test case compiling request initiated by a user side, and displays an adaptive case compiling interface according to the test case compiling request. The use case compiling interface comprises a newly added use case compiling interface and an optimized use case compiling interface, and the use case compiling request comprises an application scene and a requirement test point. The initiation of the use case writing request can be through but not limited to input in a corresponding input box, single-click selection, double-click selection, checking and the like.

The application scenes are types of case compiling scenes, including pure newly added test scenes and optimized test scenes.

If the application scene in the case compiling request is a pure new test scene, and the case base does not have a corresponding test case with a historical version, displaying a new case compiling interface; if the application scene of the test case compiling request is an optimized test scene, the test cases of the corresponding historical versions exist in the use case library, the test cases can be compiled according to the test cases of the historical versions, and the case compiling process is simplified. The network equipment extracts and analyzes the required test points in the test case compiling request, screens target case test points consistent with the required test points, copies the test cases corresponding to the target case test points to generate case copies, identifies case element information of the case copies, inputs the case element information to a preset optimized case compiling interface, and displays the optimized case compiling interface. The use case elements of the use case writing interface comprise: one or more of a use case number, a module to which the use case belongs, a use case title, a version identifier, a test point, input data, an operation step, and an expected result.

The use case elements of the use case authoring interface are referred to as essential parts constituting a use case.

In order to assist in understanding the above technical solution, a specific use case writing interface schematic diagram is described below, with reference to fig. 5, where a use case number may be a character string composed of characters, or a numeric string composed of numbers, or a character string composed of characters and numbers, or the like; the module can be the test class of the current test case or the tested requirement, the tested module, the tested unit, etc.; the use case title can be the key point or the focus point of the use case described by the summarized language, and the like; the version identification can be a version number composed of numbers or characters or numbers and characters; the test points are core test points of the use case and can be use case test points, scene test points, demand test points and the like; the input data is external data which needs to be input in the execution process of the test case, and the input mode of the input data can be manual input, file import and the like; the operation steps are the operation steps required by executing the current test case, and can comprise entering, inputting, popping and the like; the expected result is an expected output result of the current use case, and may be content of a return value, a response result of an interface, a rule conformity of an output result, and the like.

In the embodiment, the application scene and the required test points in the test case compiling request are identified by receiving the test case compiling request initiated by the user side, the adaptive case compiling interface is analyzed and displayed, the compiling process of the test case is normalized by setting the case compiling interface, the dependence on experience or professional knowledge of a compiler is reduced, the compiling process of the test case is normalized and standardized, the quality of the case is further improved, the display of the case compiling interface is displayed, the use case compiling process is visualized, the conditions that the case compiling is missed and the missed part is difficult to find due to the lack of the technology and experience of the case compiler are avoided, the case compiling efficiency is improved, and the delivery efficiency of the product is further improved.

And S40, receiving the compiling information input by the user side based on the use case compiling interface, compiling the use case elements in the use case compiling interface according to the compiling information, and generating a primary test use case.

In some embodiments, a network device receives a test case compiling request initiated by a user side, displays an adaptive case compiling interface according to the test case compiling request, compiles case elements in the case compiling interface according to compiling information input by the user side received by the case compiling interface, extracts and analyzes the case elements in the compiling information input by the user side to compile cases if the case compiling interface is a newly added case compiling interface and indicates that no corresponding test cases with historical versions exist in a case library, and generates a primary test case; if the case compiling interface is an optimized case compiling interface, and shows that the case base has the corresponding test cases with the historical versions, case elements in compiling information input by a user side are extracted and analyzed to conduct case compiling, a primary test case is generated, and the test cases except the case copy in the case base are grayed, wherein graying means that the selected test cases are forbidden, so that the test of useless cases is avoided, and the test time is wasted.

The writing information is one or more items included in the use case elements of the use case writing interface, and the modes of inputting the writing information by the user side include but are not limited to input in a corresponding input box, single-click selection, double-click selection, check selection and the like.

In this embodiment, the network device extracts and analyzes the use case elements in the writing information by receiving the writing information input by the user side, thereby performing use case writing to generate the primary test use case. The setting of the case compiling interface enables the compiling process of the test case to be standardized and standardized, the technical and experience requirements of case compilers are reduced, the visualization of case compiling is realized through the display of the case compiling interface, the omission in the case compiling process can be reduced, the case compilers can be helped to quickly find the problems in the case compiling process, the non-case copy is grayed, the problem that the test time is long due to the fact that all cases are developed and executed is solved, and the delivery efficiency of products is further improved.

And S50, performing test acceptance according to the primary test case, generating a final version case, and filing the final version case into the case library.

In some embodiments, the generated primary test cases are subjected to case review, development self-test and test acceptance are carried out according to the primary test cases, each step of a case test process and a result of the step are displayed in a corresponding interface, a final version case is generated after all the test acceptance passes, the final version case is filed in the case base, and if an application scene of a writing request for the final version is a pure new test scene which indicates that no test case with a corresponding historical version exists in the case base, the final version case is copied into the case base and a new association relation is added to a case outline.

In an implementable mode, if the application scene of the writing request for the final version is an optimized test scene, which indicates that a corresponding test case of a historical version exists in a case library, adding a corresponding case title and an upgraded version identifier to the final version case according to a case title and a version identifier of a case copy during writing, placing the final version case in a case library position where the case copy is located, and establishing an incidence relation between the final version case and the case schema according to the incidence relation between the case copy and the case schema.

The case review refers to a test process for identifying and perfecting test cases through different review roles, and the review roles of the case review include but are not limited to: PO (Product Owner), principal, SM (scrub Master), architect, etc.

The development self-test refers to a process of testing a product according to a necessary test scene in a test case. The necessary test scene is a scene that the confirmed development must be tested and verified after all the use case scenes are subjected to use case review.

The product refers to software, programs, etc. that need to be tested.

The test acceptance refers to a process of testing the product according to all case scenes in the test case.

In the embodiment, by carrying out case review on the generated primary test case, developing self-test and test acceptance according to the primary test case, and displaying each step and the result of the case test process in the corresponding interface, the visualization of the case test process is realized, which is beneficial for testers to quickly find problems in the case test process, avoids useless test or repeated test of cases, improves the quality and efficiency of the process of review, self-test and acceptance of test cases, and further improves the delivery efficiency of products. And then generating a final version case after the test acceptance passes completely, and filing the final version case into the case library, so that the case loss caused by the iteration ending of the case due to the complicated test iteration process is avoided, and a user can conveniently and quickly know the historical design and the case maintenance of the product.

Further, in another embodiment of the online case testing method according to the present invention, referring to fig. 6, the step of receiving a test case compilation request initiated by a user side, and displaying an adapted case compilation interface according to the test case compilation request includes:

and S31, if the application scene of the test case compiling request is a pure new test scene, displaying a new case compiling interface.

In some embodiments, the network device receives a test case compiling request initiated by a user side, and displays an adaptive case compiling interface according to the test case compiling request. The use case writing request comprises an application scene and a requirement test point. The initiation of the use case writing request can be through but not limited to input in a corresponding input box, single-click selection, double-click selection, checking and the like. And if the application scene in the case compiling request is a pure new test scene, which indicates that no corresponding test case with a historical version exists in the case library, displaying a new case compiling interface. For example, the test case compiling request is initiated by the compiler at the user side, wherein the application scenario compiler of the test case compiling request selects a pure new test scenario by clicking, and then a new additional case compiling interface is displayed at the user side.

Step S32, if the application scene of the test case compiling request is an optimized test scene, extracting and analyzing the required test points in the test case compiling request, screening target case test points consistent with the required test points, copying the test cases corresponding to the target case test points, generating case copies, identifying case element information of the case copies, inputting the case element information to a preset optimized case compiling interface, and displaying the optimized case compiling interface.

In some embodiments, the network device receives a test case compiling request initiated by a user side, and displays an adaptive case compiling interface according to the test case compiling request. If the application scene of the test case compiling request is the optimized test scene, the test case library is indicated to have the corresponding test case with the historical version, the test case can be compiled according to the test case with the historical version, and the case compiling process is simplified. The method comprises the steps that network equipment analyzes a case compiling request input by a user side, extracts required test points in the case compiling request, screens target case test points in a case library, which are consistent with the required test points, copies test cases corresponding to the target case test points to generate case copies, identifies case element information contained in the case copies, inputs the identified case element information to a preset optimized case compiling interface, and displays the optimized case compiling interface.

For example, a writer initiates a test case writing request at a user side, wherein an application scene of the test case writing request is a pure new test scene, a cloud dog environment starting station initialization progress guide is input to a required test point, a network device screens out a case of an organization structure in a case library through analysis, a case test point of a login case logging in and logging out the case is consistent with the required test point, the login case is copied to generate a login case copy, case element information contained in the login case copy is identified, the identified case element information is input to a preset optimized case writing interface, and the optimized case writing interface is displayed.

In the embodiment, the adaptive use case compiling interface is displayed by receiving and analyzing the application scene and the required test point contained in the test use case compiling request initiated by the user side, and the use case compiling process is simplified, the requirements on the technology and experience of use case compiling personnel are reduced and the use case compiling process is standardized by setting the differentiated use case compiling interface. And the case compiling interface is displayed, so that the case compiling process is visualized, and a user can quickly find compiling problems and further improve the case compiling efficiency.

And S33, if the case compiling interface is the newly added case compiling interface, extracting and analyzing case elements in the compiling information input by the user side to compile the cases, and generating a primary test case.

In some embodiments, a newly added use case compiling interface is displayed according to a pure newly added test scene in a use case compiling request input by a user side, a compiler inputs use case elements according to the newly added use case compiling interface, and after the compiler completes all input of the use case elements, the network equipment analyzes and compiles the use case elements so as to generate a primary test use case.

And step S34, if the case compiling interface is the optimized case compiling interface, extracting and analyzing case elements in compiling information input by a user side to compile cases, generating primary test cases, and graying the test cases except the case copies in the case library.

In some embodiments, an optimized case compiling interface is displayed according to an optimized test scenario in a case compiling request input by a user side, a compiler adjusts case elements displayed on the optimized case compiling interface, wherein the adjustment includes but is not limited to deletion, addition, modification sequence and the like, case compiling is performed according to the adjusted case elements of the optimized case compiling interface, a primary test case is generated, and meanwhile, test cases except for case copies in a case library are grayed out, so that no useless test can be performed on irrelevant test cases in a subsequent case testing process, and the delivery efficiency of products is further improved.

In this embodiment, the network device extracts and analyzes the case elements in the compiling information by receiving the compiling information input by the user side, so as to compile the case to generate the primary test case. The method has the advantages that the differentiated use case compiling interface is arranged, the compiling process of the use cases is more convenient and faster, the compiling process of the test cases is more standardized, the occurrence of use case compiling errors caused by the lack of the technology and experience of use case compiling personnel is avoided, the display of the use case compiling interface realizes the visualization of the use case compiling, the omission in the use case compiling process can be reduced, the use case compiling personnel can be helped to quickly find the problem in the use case compiling process, the non-use case copies are grayed, the problem that the time for developing and executing all use cases is long is avoided, and the delivery efficiency of products is further improved.

Step S35, receiving a use case evaluation request initiated by a user side, and displaying an adaptive use case evaluation interface according to the use case evaluation request; the review elements of the use case review interface comprise: the method comprises the following steps of evaluating roles, evaluating results, evaluating opinions and necessary scenes.

In order to assist understanding of the above technical solution, a specific schematic diagram of a use case review interface is used for assisting explanation below, and with reference to fig. 7, a use case review request initiated by a user side is received, and an adaptive use case review interface is displayed according to the use case review request, where review elements of the use case review interface include: the method comprises the following steps of evaluating roles, evaluating results, evaluating opinions and necessary scenes. Referring to fig. 7, the review role, the review result, the review comment and the certain scene in the review elements are respectively in a single column, and the corresponding review result, the review comment and the certain scene obtained after the use case is reviewed by each specific review role are in a same line.

The use case review request comprises but is not limited to selection of a review role, selection of review content and the like, and the initiation mode of the use case review request comprises but is not limited to input in a corresponding input box, single-click selection, double-click selection, check-out and the like.

The review element refers to an essential part forming the use case review, wherein the review role can be as follows: PO, principal, SM, architect, etc.; the evaluation result can be pass, modification, fail, etc.; the review opinions can be specific test case modification methods, contents and the like; the necessary test scenario may be a case scenario included in the test case or other scenarios not written into the test case, and this embodiment only explains some implementable manners for the review elements, and does not limit the explanation of the review elements.

And S36, receiving the review information input by the user terminal, inputting the review information into the review elements of the use case review interface, updating the use case review interface and displaying the updated use case review interface.

In some embodiments, a user selects a review role in the case review interface, inputs a review result, a review opinion and a necessary scene obtained after the review role reviews a case from a professional perspective, and the network device receives the review information, inputs the review information into a corresponding review element of the case review interface, thereby updating the case review interface and displaying the updated case review interface. For example, after the review role PO reviews the case with a delivery perspective, a review result is obtained: modifying; and (4) evaluating the opinions: navigation should take effect when a user logs in next time, performance test needs to verify that all application lists of a production environment are displayed, a module is introduced, whether performance problems exist in attribution is set, and a core scene is added in a case; the necessary measurement scene is as follows: and (5) testing a user scene. After the review information is input, the network device inputs the review information into the corresponding review elements of the case review interface so as to update the case review interface and display the updated case review interface, referring to fig. 7.

And the review information is the review result, the review opinion and the necessary scene obtained after each review role reviews the test case according to the professional visual angle of each review role.

And S37, according to the review opinions in the updated case review interface, the primary test case is perfected, and a necessary test scene in the primary test case is determined.

In some embodiments, the network device receives the review information input by the user terminal, inputs the review information into the corresponding review element column of the case review interface, updates the case review interface, and displays the updated case review interface. And according to the review comments in the updated case review interface, perfecting the primary test case, and determining a necessary test scene in the primary test case, so that the test case can be conveniently subjected to subsequent development self-test, wherein the perfecting of the primary test case comprises but is not limited to addition and deletion of a case scene or exchange of a test sequence and the like.

In the embodiment, a use case review request initiated by a user side is received, an adaptive use case review interface is displayed, so that a tester can develop a use case review conference according to the use case review interface, the visualization of a use case test process is realized, corresponding review opinions are given according to review roles, a primary test use case is perfected, a necessary test scene for developing self-test is determined, the development of a development self-test link is facilitated, the omission of the use case scene or the necessary test scene is avoided, and the delivery efficiency of products is further improved.

Optionally, after the step S37 of completing the primary test case according to the review comment in the updated use case review interface and determining a necessary test scenario in the primary test case, the method includes:

step S371, receive the development self-test request that the user initiates, reveal the adaptive development self-test interface; the self-test elements for developing the self-test interface comprise: and (4) determining a scene and a self-testing result.

In some embodiments, a network device receives a self-test request initiated by a user side, and displays an adaptive development self-test interface according to the self-test request; the self-test elements for developing the self-test interface comprise: and determining a scene and a self-testing result.

The self-test request comprises all necessary test scenes of the development and self-test of the primary test case; the necessary test scene is a scene which is confirmed to be developed and has to be tested and verified after all the use case scenes are subjected to use case review; the self-test result is a result obtained after the product to be tested is tested according to the necessary test scenario in the primary test case, and may be a passing or failing reason or a failing reason, and the present embodiment does not limit this.

And step S372, carrying out development self-test on a preset product according to the development self-test request and the necessary test scene in the primary test case.

In some embodiments, the network device performs development self-test on a preset product according to a development self-test request and a necessary test scene in the development self-test request, and if the product passes through the development self-test of the necessary test scene and indicates that the product is normally executed in the necessary test scene, the network device marks that the self-test passes through the necessary test scene and outputs a development self-test passing result to a development self-test interface; if the product fails the development self-test of the necessary scene, which indicates that the product is abnormal in the execution of the necessary scene, the self-test of the necessary scene is marked to fail, and the result of the failure of the development self-test is output to a development self-test interface for a tester to correct the product.

And S373, if the product passes the development self-test of the must-test scene, marking the must-test scene that the self-test passes, and outputting the result of the development self-test to the development self-test interface.

In some embodiments, the network device performs development self-test on the product according to the development self-test request and a necessary test scenario in the development self-test request, if the product passes through the development self-test of the necessary test scenario and indicates that the product is normally executed in the necessary test scenario, the network device marks that the product passes through the necessary test scenario, outputs a result that the product passes through the development self-test to a development self-test interface, and outputs a corresponding development self-test passing rate after the development self-test of all the necessary test scenarios is completed, so as to provide a data basis for the quality of the product and the use case.

Step S374, if the product does not pass the development self-test of the necessary test scene, marking the necessary test scene that the development self-test does not pass, and outputting the result of the development self-test to the development self-test interface; and correcting the product according to the development self-test result to generate a corrected product, and performing the development self-test on the corrected product.

In some embodiments, the network device performs development self-test on the product according to the development self-test request and a necessary test scenario in the development self-test request, if the product does not pass the development self-test of the necessary test scenario, it indicates that the product is abnormal in execution in the necessary test scenario, the network device marks that the product does not pass the development self-test, and outputs a result that the development self-test does not pass to the development self-test interface, the tester corrects the product according to the result that the development self-test does not pass, generates a corrected product, performs development self-test on the corrected product again, and if the development self-test does not pass, continues to perform step S374.

In this embodiment, an adaptive development self-test interface is displayed according to a development self-test request initiated by a user side, visualization of a case development self-test process is realized, development self-test is further performed on the product primary test case according to the development self-test request and the necessary test scene, if the product passes the development self-test of the necessary test scene, the necessary test scene is marked to pass the self-test, and a result of the development self-test is output to the development self-test interface, if the primary test case passes the development self-test of the necessary test scene, the necessary test scene is marked to pass the self-test, and a result of the development self-test is output to the development self-test interface; if the product primary test case does not pass the development self-test of the necessary test scene, marking the necessary test scene that the development self-test does not pass, and outputting the result of the development self-test to the development self-test interface; and correcting the product primary test case according to the development self-test result to generate a corrected product primary test case, and performing development self-test on the corrected product primary test case again until all necessary test scenes are passed. By outputting and displaying the development self-testing result in real time on the development self-testing interface, the visualization of the case development self-testing process is realized, scene omission caused by a large number of necessary testing scenes is avoided, a tester can find the problem of a case product quickly, the product testing case is corrected and perfected according to the problem pertinence, and the delivery efficiency of the product is further improved.

Further, in another embodiment of the online use case testing method according to the present invention, referring to fig. 8, the step of performing test acceptance according to the primary test case, generating a final use case, and filing the final use case into the use case library includes:

s51, receiving a test acceptance request initiated by a user side, and displaying an adaptive test acceptance interface; the acceptance elements of the test acceptance interface comprise: case scene and acceptance result.

In some embodiments, after passing the development self-test of all necessary test scenarios, the user terminal initiates a test acceptance request, the network device displays an adaptive test acceptance interface according to the test acceptance request, and acceptance elements of the test acceptance interface include: case scene and acceptance result.

The test acceptance request is an execution request of a test acceptance step submitted to the network device by the user side, and can be input, single-click selection, double-click selection, checking and the like in a corresponding input box.

The acceptance elements are necessary parts forming test acceptance, and comprise use case scenes and acceptance results; the case scenarios are all test scenarios compiled based on the requirements of the product to be tested; the acceptance result is obtained after the product is tested in the test scenario, and may be a passing or failing reason or a failing reason, which is not limited in this embodiment.

And S52, testing and accepting the product according to the test and acceptance request and the case scene in the primary test case.

In some embodiments, after a user side initiates a test acceptance request, a network device displays an adaptive test acceptance interface according to the test acceptance request, tests and accepts a product according to a case scene in the test acceptance interface, and marks acceptance of the case scene and outputs a passing result to the test acceptance interface if the initial product passes the test acceptance of the case scene and shows that the product is normally executed in the case scene; if the product fails the test acceptance of the case scene, which indicates that the product is abnormal in the execution of the case scene, marking the case scene that the product fails the acceptance, outputting the result of the failure to a test acceptance interface, repairing the product according to the acceptance result, and testing and accepting the repaired product again.

And S53, if the product passes the test acceptance of the case scene, marking the case scene that the acceptance passes, and outputting the test acceptance result to the test acceptance interface.

In some embodiments, after the user side initiates a test acceptance request, the network device displays an adaptive test acceptance interface according to the test acceptance request, tests and accepts a product according to a case scenario in the test acceptance interface, and marks that the acceptance is passed on the case scenario and outputs a pass result to the test acceptance interface if the product passes the test and acceptance of the case scenario and shows that the product is normally executed in the case scenario. And when all the use case scenes are checked and accepted, outputting the corresponding test acceptance passing rate, and providing data basis for the quality of the product and the use cases.

Step S54, if the product fails the test acceptance of the case scene, marking the case scene that the acceptance fails, and outputting the test acceptance result to the test acceptance interface; and repairing the product according to the test acceptance result to generate a repaired product, and performing the test acceptance on the repaired product.

In some embodiments, after a user side initiates a test acceptance request, a network device displays an adaptive test acceptance interface according to the test acceptance request, tests and accepts a product according to a case scene in the test acceptance interface, if the product fails the test acceptance of the case scene, which indicates that the product is abnormal in execution in the case scene, marks that the product fails the acceptance in the case scene, outputs a result of the test acceptance to the test acceptance interface, repairs the product according to the result of the test acceptance, generates a repaired product, performs the test acceptance on the repaired product again, and if the product fails the test acceptance, continues to perform step S54 until the test acceptance of all the case scenes is passed.

In an implementable manner, if the product requirement changes in the test process, the use case writer can reinitiate the test use case writing request, display an adaptive use case writing interface according to the test use case writing request, modify the use case scene in the use case writing interface, and then revise the test use case, wherein the revision includes addition, deletion, sequence exchange and the like of the use case scene, and the embodiment is not limited.

And step S55, when all the marks of the use case scene pass, generating a final version case.

In some embodiments, after all case scenes of the primary test case are marked to pass, the product passes the test acceptance, the product is qualified and can be delivered, the primary test case is output as a final board case, and the final board case is filed in the case library. If the application scene of the writing request for the final version is a pure new test scene, the final version case is a new case, and the historical version of the case does not exist in the case library, so that the final version case is copied into the case library, and a new association relation is added to the case schema, and the case can be conveniently searched and used later.

In an implementable manner, if the application scenario of the writing request of the final version use case is an optimized test scenario, it is indicated that the final version use case is optimized for an existing use case, and a historical version of the use case exists in a use case library, so that according to a use case title and a version identification of a use case copy during writing, a corresponding use case title and an upgraded version identification are added to the final version use case, the final version use case is placed in a use case library position where the use case copy is located, and according to an association relationship between the use case copy and the use case outline, an association relationship between the final version use case and the use case outline is established.

For example, if the application scenario of the writing request of the final version case is an optimized test scenario, according to the case copy at the time of writing: and (3) logging in a case V1.1, and adding a case title to the final version case: the login case and the upgraded version identification V1.2 are placed in the case library position of the login case V1.1, and the association relationship between the login case V1.2 and the case schema is established according to the association relationship between the login case V1.1 and the case schema.

In this embodiment, after the test acceptance of the primary test case is completed, the adaptive test acceptance interface is displayed according to the test acceptance request of the user side, the visualization of the case test acceptance process is realized, the product is tested and accepted according to the test acceptance request and the case scene, and the corresponding result is output to the test acceptance interface according to the acceptance result, so that the problem can be quickly found by a tester in the test acceptance process, the product is timely modified and optimized, the test acceptance time is shortened, and the delivery efficiency of the product is further improved. And then when the test acceptance of the case scene is completely passed, generating a final version case, and filing the final version case into the case library, so that the case loss caused by the iteration ending due to the complicated test iteration process is avoided, and a user can conveniently and quickly know the historical design of the product and the maintenance of the case.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or system that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. An online use case testing method, wherein the online use case testing method comprises the following steps:

2. The online use case testing method according to claim 1, wherein the step of combing the use case schema of the product to be tested, and setting the schema level and the use case scenario of the test use case in a hierarchical manner based on the schema items of the use case schema comprises:

3. The online use case testing method according to claim 2, wherein the step of establishing the use case library of the product to be tested according to the outline level and the use case scenario includes:

4. The online use case testing method according to claim 3, wherein the use case writing interface includes an additional use case writing interface and an optimized use case writing interface, the test use case writing request encloses an application scenario and a requirement test point, and the step of displaying the adapted use case writing interface according to the test use case writing request includes:

5. The online use case testing method according to claim 4, wherein the step of receiving composition information input from a user side based on the use case composition interface and composing use case elements in the use case composition interface according to the composition information, and generating a primary test case comprises:

if the case compiling interface is the newly-added case compiling interface, extracting and analyzing case elements in compiling information input by the user side to compile the cases, and generating a primary test case;

6. The online use case testing method of claim 5, after the step of generating a preliminary test case, further comprising:

7. The online use-case testing method according to claim 6, wherein after the step of completing the preliminary test case according to the review information and determining the necessary test scenarios in the preliminary test case, the method further comprises:

according to the development self-test request and the necessary test scene in the primary test case, carrying out development self-test on a preset product;

8. The online use case testing method according to claim 7, wherein the step of performing test acceptance according to the primary test case, generating a final use case, and filing the final use case into the use case library comprises:

if the product passes the test acceptance of the case scene, marking the case scene to pass the acceptance, and outputting the test acceptance result to the test acceptance interface;

9. An online use-case test apparatus, the apparatus comprising: a memory, a processor, and an online use case test program stored on the memory and executable on the processor, the online use case test program configured to implement the steps of the online use case test method as recited in any one of claims 1 to 8.

10. A storage medium, wherein the storage medium is a computer-readable storage medium, and the computer-readable storage medium stores thereon an online use case test program, and the online use case test program is executed by a processor to implement the steps of the online use case test method according to any one of claims 1 to 8.