CN111352824B - Test method and device and computer equipment - Google Patents
Test method and device and computer equipment Download PDFInfo
- Publication number
- CN111352824B CN111352824B CN201811575302.6A CN201811575302A CN111352824B CN 111352824 B CN111352824 B CN 111352824B CN 201811575302 A CN201811575302 A CN 201811575302A CN 111352824 B CN111352824 B CN 111352824B
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- view
- database
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a testing method, a testing device and computer equipment. The method comprises the following steps: receiving a test request, inquiring a preset database according to test feature information carried in the test request, and acquiring test case data matched with the test feature information; generating a test case view used for representing the current test according to the acquired test case data; and calling a preset test application program, running the test case view to execute the test, acquiring an execution result, writing the acquired execution result into the test case view and storing the acquired execution result.
Description
Technical Field
The present application relates to the field of testing technologies, and in particular, to a testing method, a testing device, and a computer device.
Background
After the development of the application program or the product and other services is completed, the developed service quality needs to be ensured through testing, and when the developed service is tested, each function is tested automatically for example, and test cases need to be written in advance according to each function of the specific application program so as to test and verify each function of the application program. The test case is a set of code segments written for a specific purpose and including data such as test input, execution conditions and expected results, and by running the test case, a certain application path can be tested or whether the tested application meets a certain specific requirement can be verified.
However, the current test cases are written in the codes of the test cases through development languages, and each test case needs to be edited by the corresponding codes, so that the time required for generating the test cases is longer, and the generation efficiency of the test cases is lower; furthermore, the editors are required to master the development language, so that the requirements on the editors for editing the test cases are high, and the updating, the management and the maintenance are inconvenient; moreover, after the test case is tested and operated in a certain tested device, the tested device executing the test records the test case, and when the test case is used for the tested device again for testing, for example, according to different application program conditions, the test case needs to be reused, but because the tested device records and operates the test case, errors can occur, so that the test case cannot be operated in the tested device again, the test case cannot be reused, and the reuse rate of the test case is lower.
Disclosure of Invention
In a first aspect, embodiments of the present application provide a test method, the method including:
receiving a test request, inquiring a preset database according to test feature information carried in the test request, and acquiring test case data matched with the test feature information;
generating a test case view used for representing the current test according to the acquired test case data;
and calling a preset test application program, running the test case view to execute the test, acquiring an execution result, writing the acquired execution result into the test case view and storing the acquired execution result.
With reference to the first aspect, an embodiment of the present application provides a first possible implementation manner, where, before the receiving a test request, the method further includes:
and editing the test case data in a spreadsheet mode, and storing the edited spreadsheet into the database.
With reference to the first aspect, a second possible implementation manner is provided in the embodiments of the present application, where the method further includes:
according to a preset test case classification rule, classifying and storing the test case data in the database;
the test request also carries a classification identifier, and the obtaining of test case data matched with the test feature information includes:
locating a classification database corresponding to the classification identifier from the database;
and inquiring test case data matched with the test characteristic information from the classification database.
With reference to the second possible implementation manner of the first aspect, the embodiment of the present application provides a third possible implementation manner, where the classifying storing, according to a preset test case classification rule, each test case in the database includes:
classifying the test cases according to the application programs or the products; and/or the number of the groups of groups,
classifying the test cases according to the test modules in the application program or the test modules in the product; and/or the number of the groups of groups,
classifying the test cases according to the test items in the test module; and/or the number of the groups of groups,
and classifying the test cases according to the test case attributes.
With reference to the first aspect, or any one of the first to third possible implementation manners of the first aspect, the present application example provides a fourth possible implementation manner, where the method further includes:
generating a test report according to the execution result, and sending the test report to a preset tester.
With reference to the first aspect, or any one of the first to third possible implementation manners of the first aspect, the present application example provides a fifth possible implementation manner, where the method further includes:
counting the total test execution times of each test case and the times of the test success of the test case, and calculating the execution success rate of the test case according to the times of the test success and the total test execution times.
With reference to the first aspect, or any one of the first to third possible implementation manners of the first aspect, the present application example provides a sixth possible implementation manner, where the method further includes:
and displaying the test case view written with the execution result.
With reference to the first aspect or any one of the first to third possible implementation manners of the first aspect, a seventh possible implementation manner is provided by the present application embodiment, where the test feature information includes: test case name, test case category, test case keyword, or one or any combination of test case keywords.
In a second aspect, embodiments of the present application provide a test apparatus, the apparatus comprising:
the query module is used for receiving a test request, querying a preset database according to test characteristic information carried in the test request, and obtaining test case data matched with the test characteristic information;
the view generation module is used for generating a test case view used for representing the current test according to the acquired test case data;
and the test module is used for calling a preset test application program, running the test case view to execute the test, acquiring an execution result, writing the acquired execution result into the test case view and storing the acquired execution result.
In a third aspect, embodiments of the present application provide a computer device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method described above when executing the computer program.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method described above.
Compared with the prior art, the application has the following beneficial effects:
according to the testing method, the testing device and the computer equipment, the testing request is received, the preset database is queried according to the testing characteristic information carried in the testing request, and the testing case data matched with the testing characteristic information is obtained; generating a test case view used for representing the current test according to the acquired test case data; and calling a preset test application program, running the test case view to execute the test, acquiring an execution result, writing the acquired execution result into the test case view and storing the acquired execution result. Therefore, the database is used for storing the test case data, codes do not need to be written through a development language, the time required for generating the test case is short, and the efficiency of generating the test case is high; further, a test case view uniquely identifying the test is generated according to the test case data extracted from the database, so that the tested equipment executing the test is considered as a new test case, thereby running and executing the test, and realizing the multiplexing of the test cases in the database; moreover, the execution result of the obtained test case view does not influence the original test cases in the database, and the execution result of each test case can be effectively obtained.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered limiting the scope, and that other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of a testing method according to an embodiment of the present application;
FIG. 2 is a schematic structural diagram of a testing device according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
In the description of the present application, it should also be noted that, unless explicitly specified and limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the terms in this application will be understood by those of ordinary skill in the art in a specific context.
Fig. 1 is a schematic flow chart of a test method according to an embodiment of the present application. As shown in fig. 1, the process includes:
in this embodiment, as an optional embodiment, before the receiving the test request, the method further includes:
and editing the test case data in a spreadsheet mode, and storing the edited spreadsheet into the database.
In this embodiment, the Database (Database) is a repository for organizing, storing and managing data according to a data structure, each test case corresponds to a row of an electronic table (Excel) in the Database, and the test cases are characterized by the parameter data as described above, for example, the data in the first row and the first column corresponds to the parameter data in a test case. As an alternative embodiment, the test cases exist in a spreadsheet in the format of data. Of course, in practical application, the test case data can be directly input and stored in the database by a manual input mode, and the database stores the test case data.
Because the conventional test can multiplex a large number of original test cases, and edit the original test cases according to the newly added service requirement to obtain the test cases as a new round of test, code segments of each test case, namely test application programs, are run, and most of the code segments can be multiplexed. In this embodiment, test case data (parameter data) and test application programs included in the test cases are separated from each other, and the test case data (parameter data) and the test application programs are extracted. The test case data of the test case is only required to be recorded in the database, code segment editing is not required to be carried out on the running test of the test case data, and in the follow-up test case running process, the test case data in the database can be run by calling a preset test application program edited by the code segment.
In this embodiment, as an alternative embodiment, the test feature information includes, but is not limited to: test case name, test case keyword, test case category, test case keyword, etc., or any combination thereof.
In this embodiment, by extracting a keyword or a test case name in the test feature information, one or more test cases matching the keyword or the test case name are screened from the database.
In this embodiment, as an optional embodiment, the method further includes:
and classifying and storing the test case data in the database according to a preset test case classification rule.
In this embodiment, if the test request further carries a classification identifier, obtaining test case data matched with the test feature information includes:
locating a classification database corresponding to the classification identifier from the database;
and inquiring test case data matched with the test characteristic information from the classification database.
In this embodiment, if the test request does not carry the classification identifier, the test feature information is matched with each test case data in the database, so as to obtain matched test case data.
In this embodiment, the test case data in the database is classified and stored, so that management and maintenance of the test case can be facilitated. As an optional embodiment, classifying and storing each test case data in the database according to a preset test case classification rule includes:
classifying the test cases according to the application programs or the products; and/or the number of the groups of groups,
classifying the test cases according to the test modules in the application program or the test modules in the product; and/or the number of the groups of groups,
classifying the test cases according to the test items in the test module; and/or the number of the groups of groups,
and classifying the test cases according to the test case attributes.
In this embodiment, as an alternative embodiment, the test case attributes include, but are not limited to: data type, execution conditions (e.g., software and hardware environment in which the test case is executed, logic conditions in which the test case is executed, etc.), data size, etc.
In this embodiment, test cases belonging to the same application or the same product may be classified into a first class of classification; under the first class classification, the test cases belonging to the same test module can be classified into a second class classification; under the secondary classification, the test cases belonging to the same test item can be classified into the tertiary classification; or classifying the test cases according to the test case attributes. Therefore, the editing management efficiency of a plurality of test cases can be improved, the query is conveniently performed according to the test characteristic information, and the corresponding test cases are quickly queried for testing.
in this embodiment, the View is a virtual table in the computer database, and the contents of the View may be defined or customized by the query. The virtual table has the same format as the real table, and each row and column contains data with a data identifier, wherein the data identifier can be a data name or a data serial number, and the data identifier is different from the real table in that only the definition of the view is stored in the database, and when the data in the view is operated, the electronic table associated with the view in the database needs to be operated according to the definition of the view. That is, the view is in the database and does not exist in the format of data or data bars, the row and column data is associated with the spreadsheet referenced by the query defining the view, and the associated spreadsheet is dynamically invoked when the view is manipulated.
In this embodiment, as an alternative embodiment, the test case view for the current test may be characterized by information such as a test case view identifier or a test case view version number. Thus, for each test, even if the test cases contained in the test case view are the same, different test case attempts are corresponding to different test case attempt identifications or test case view version numbers, so when the test is input to the tested equipment for testing, the tested equipment considers that the test case attempts to be different from the recorded test case view, and therefore, the current test case view identified by the test case attempt identifications or the test case view version numbers is operated, the test case error report can be effectively avoided, the same test case can be multiplexed for multiple times in a mode of different test case view identifications or version numbers, and the repeated utilization rate of the test case is high.
In this embodiment, the specific flow of generating the view may be referred to related art documents, and detailed description thereof is omitted herein.
In this embodiment, the code segments for running each test case may be multiplexed. According to the embodiment, the test application program for executing the test on the test case is pre-written, so that the workload of editing the test case by an editor can be effectively reduced, the editing efficiency is improved, and the technical requirements on the editor can be reduced.
In this embodiment, by calling a preset automated test application, the test application automatically executes data (test cases) in the generated test case view, and writes back the execution result to the test case view. Each test case corresponds to an execution result, for example, if the test case view contains a plurality of test cases, the execution result obtained by executing each test case is written into the tail of the test case, so that the test is performed by using the test case view, and the execution result of each test case is written into the test case view by a view method, thereby obtaining the test case which successfully passes and the test case which fails in detail. The state of the test case can be tracked after each test case view is executed, so that the test case result of each test can be recorded and stored.
In this embodiment, as an optional embodiment, the execution result includes: success, failure, if failure, the method further comprises: and recording the reason of the test failure.
In this embodiment, after writing the acquired execution result into the test case view, the test case view is stored in the database. Therefore, by storing the execution results of the test case views, a tester can conveniently call the execution results of each test case, and the execution results of the same test case in different test environments can be known.
In this embodiment, according to the test feature information included in the test request, the database is queried to obtain test case data matched with the test feature information, and the matched test case data is organized to generate a test case view with a unique identifier, so that according to the test case view with the unique identifier, a corresponding test application program is invoked to perform a test. Therefore, the database is used for storing the test cases, codes are not required to be written through development languages, the requirements on editors editing the test cases are low, the test cases are convenient to update, manage and maintain, meanwhile, the time required for generating the test cases is short, and the efficiency of generating the test cases is high; further, when testing is performed, inquiring is performed according to a test request, corresponding test case data is extracted from a database, a test case view which uniquely identifies the test is generated according to the extracted test case data, and the test case view identifications generated by each test are different, so that tested equipment for executing the test is considered to be a new test case, the test is operated and executed, the obtained execution result of the test case view does not influence the original test case in the database, the repeated multiplexing of the test cases in the database can be realized, and the repeated utilization rate of the test cases is effectively improved; in addition, the database technology is utilized to manage the test case data, the query can be carried out according to the test characteristic information carried in the test request, the test case can be dynamically configured, and different functional requirements of each test environment can be met.
In this embodiment, the relevant personnel may also be notified of the execution result obtained by the test. Thus, as an alternative embodiment, the method further comprises:
generating a test report according to the execution result, and sending the test report to a preset tester.
In this embodiment, as an optional embodiment, after the automated test application program executes the test case view, a test report is generated according to the execution result, and a mail sending function or a message sending function in the automated test application program is called to send the test report to the relevant tester.
In this embodiment, since the execution result of each test case may be recorded, statistics may be performed on the execution result of each test case in different test environments. As an alternative embodiment, the method further comprises:
counting the total test execution times of each test case and the times of the test success of the test case, and calculating the execution success rate of the test case according to the times of the test success and the total test execution times.
In this embodiment, as an optional embodiment, the method further includes:
and displaying the test case view written with the execution result.
In this embodiment, the execution result is displayed, so that the execution result state and the overall test condition of the test case view can be intuitively obtained.
In this embodiment, the test cases stored in the database may be edited, for example, the test cases may be modified, deleted, added, etc., so that the test cases may be updated.
The following is a partial code segment (java language example) of a test case stored in a database according to the embodiment of the present application:
the following code segments are code segments (java language) that execute test cases (test application and organization generates test case views):
fig. 2 is a schematic structural diagram of a testing device according to an embodiment of the present application. As shown in fig. 2, the apparatus includes:
the query module 21 is configured to receive a test request, query a preset database according to test feature information carried in the test request, and obtain test case data matched with the test feature information;
in this embodiment, as an optional embodiment, the test feature information includes: test case name, test case category, test case keyword, or one or any combination of test case keywords.
In this embodiment, by extracting a keyword or a test case name in the test feature information, one or more test cases matching the keyword or the test case name are screened from the database.
The view generation module 22 is configured to generate a test case view for representing a current test according to the acquired test case data;
in this embodiment, as an alternative embodiment, the test case view for the current test may be characterized by information such as a test case view identifier or a test case view version number.
And the test module 23 is used for calling a preset test application program, running the test case view to execute a test, acquiring an execution result, writing the acquired execution result into the test case view and storing the acquired execution result.
In this embodiment, as an optional embodiment, the execution result includes: success, failure, if failure, the method further comprises: and recording the reason of the test failure.
In this embodiment, as an optional embodiment, the apparatus further includes:
and the test case editing module (not shown in the figure) is used for editing the test case data in a spreadsheet mode and storing the edited spreadsheet into the database.
In this embodiment, as another alternative embodiment, the apparatus further includes:
the test case classification module (not shown in the figure) is used for classifying and storing each test case in the database according to a preset test case classification rule;
the test request also carries a classification identifier, and the obtaining of test case data matched with the test feature information includes:
locating a classification database corresponding to the classification identifier from the database;
and inquiring test case data matched with the test characteristic information from the classification database.
In this embodiment, as an optional embodiment, the test case classification module is specifically configured to:
classifying the test cases according to the application programs or the products; and/or the number of the groups of groups,
classifying the test cases according to the test modules in the application program or the test modules in the product; and/or the number of the groups of groups,
classifying the test cases according to the test items in the test module; and/or the number of the groups of groups,
and classifying the test cases according to the test case attributes.
In this embodiment, as a further alternative embodiment, the apparatus further includes:
and the test report sending module is used for generating a test report according to the execution result and sending the test report to a preset tester.
In this embodiment, as a further alternative embodiment, the apparatus further includes:
the statistics module is used for counting the total test execution times of each test case and the times of the test success of the test case, and calculating the execution success rate of the test case according to the times of the test success and the total test execution times.
In this embodiment, as a further alternative embodiment, the apparatus further includes:
and the display module is used for displaying the test case view written with the execution result.
Fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 3, an embodiment of the present application provides a computer device for performing the test method in fig. 1 to 3, where the device includes a memory 1000, a processor 2000, and a computer program stored in the memory 1000 and capable of running on the processor 2000, where the processor 2000 implements the steps of the test method when executing the computer program.
In particular, the above-described memory 1000 and processor 2000 can be general-purpose memories and processors, and are not particularly limited herein, and the above-described test method can be performed when the processor 2000 runs a computer program stored in the memory 2000.
Corresponding to the test method of fig. 1, the embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, performs the steps of the above-mentioned test method.
In particular, the storage medium can be a general-purpose storage medium, such as a removable disk, a hard disk, or the like, on which a computer program can be executed to perform the above-described test method.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners as well. The apparatus embodiments described above are merely illustrative, for example, flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus 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 apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method of testing, the method comprising:
receiving a test request, inquiring a preset database according to test feature information carried in the test request, and acquiring test case data matched with the test feature information;
generating a test case view for representing the current test according to the acquired test case data, and representing the test case view for the current test through a test case view identifier or a test case view version number; wherein the test case view is a virtual table in the database, and in the database, the test case view does not exist in the format of data or data strips, row and column data is associated with a spreadsheet referenced by a query defining the test case view, and the associated spreadsheet is dynamically invoked when the test case view is operated;
and calling a preset test application program, running the test case view to execute the test, acquiring an execution result, writing the acquired execution result into the test case view and storing the acquired execution result.
2. The method of claim 1, wherein prior to the receiving a test request, the method further comprises:
and editing the test case data in a spreadsheet mode, and storing the edited spreadsheet into the database.
3. The method according to claim 1, wherein the method further comprises:
according to a preset test case classification rule, classifying and storing the test case data in the database;
the test request also carries a classification identifier, and the obtaining of test case data matched with the test feature information includes:
locating a classification database corresponding to the classification identifier from the database;
and inquiring test case data matched with the test characteristic information from the classification database.
4. The method of claim 3, wherein classifying and storing each test case in the database according to a preset test case classification rule comprises:
classifying the test cases according to the application programs or the products; and/or the number of the groups of groups,
classifying the test cases according to the test modules in the application program or the test modules in the product; and/or the number of the groups of groups,
classifying the test cases according to the test items in the test module; and/or the number of the groups of groups,
and classifying the test cases according to the test case attributes.
5. The method according to any one of claims 1 to 4, further comprising:
generating a test report according to the execution result, and sending the test report to a preset tester.
6. The method according to any one of claims 1 to 4, further comprising:
counting the total test execution times of each test case and the times of the test success of the test case, and calculating the execution success rate of the test case according to the times of the test success and the total test execution times.
7. The method according to any one of claims 1 to 4, further comprising:
and displaying the test case view written with the execution result.
8. The method of any one of claims 1 to 4, wherein the test characteristic information comprises: test case name, test case category, test case keyword, or one or any combination of test case keywords.
9. A test apparatus, the apparatus comprising:
the query module is used for receiving a test request, querying a preset database according to test characteristic information carried in the test request, and obtaining test case data matched with the test characteristic information;
the view generation module is used for generating a test case view used for representing the current test according to the acquired test case data, and representing the test case view used for the current test through a test case view identifier or a test case view version number; wherein the test case view is a virtual table in the database, and in the database, the test case view does not exist in the format of data or data strips, row and column data is associated with a spreadsheet referenced by a query defining the test case view, and the associated spreadsheet is dynamically invoked when the test case view is operated;
and the test module is used for calling a preset test application program, running the test case view to execute the test, acquiring an execution result, writing the acquired execution result into the test case view and storing the acquired execution result.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any of the preceding claims 1 to 8 when the computer program is executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811575302.6A CN111352824B (en) | 2018-12-21 | 2018-12-21 | Test method and device and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811575302.6A CN111352824B (en) | 2018-12-21 | 2018-12-21 | Test method and device and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111352824A CN111352824A (en) | 2020-06-30 |
| CN111352824B true CN111352824B (en) | 2023-07-07 |
Family
ID=71196809
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811575302.6A Active CN111352824B (en) | 2018-12-21 | 2018-12-21 | Test method and device and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111352824B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111813679B (en) * | 2020-07-10 | 2023-06-30 | 北京思特奇信息技术股份有限公司 | Method and device for executing test case based on python, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006047741A2 (en) * | 2004-10-27 | 2006-05-04 | Bae Systems Land & Armaments L.P. | Software test environment for regression testing ground combat vehicle software |
| CN103761189A (en) * | 2014-02-17 | 2014-04-30 | 广东欧珀移动通信有限公司 | Test case management method and system |
| US9304893B1 (en) * | 2013-03-08 | 2016-04-05 | Emc Corporation | Integrated software development and test case management system |
| CN107678951A (en) * | 2017-09-21 | 2018-02-09 | 平安科技（深圳）有限公司 | Test exemple automation management method, device, equipment and storage medium |
| CN107704393A (en) * | 2017-09-29 | 2018-02-16 | 武汉斗鱼网络科技有限公司 | Data test method, apparatus and electronic equipment |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101989227A (en) * | 2009-08-04 | 2011-03-23 | 中兴通讯股份有限公司 | Test case generating method and device |
| CN104182335B (en) * | 2014-05-09 | 2017-03-29 | 中国光大银行 | Method for testing software and device |
| US10089217B2 (en) * | 2014-09-23 | 2018-10-02 | Red Hat, Inc. | Identification of software test cases |
| CN104991777B (en) * | 2015-07-14 | 2018-04-13 | 普元信息技术股份有限公司 | Realize that web application automatic test view melts the system and method for hair |
| US10055330B2 (en) * | 2016-11-29 | 2018-08-21 | Bank Of America Corporation | Feature file validation tool |
| CN108874661B (en) * | 2018-05-07 | 2020-12-22 | 未鲲(上海)科技服务有限公司 | Test mapping relation library generation method and device, computer equipment and storage medium |
-
2018
- 2018-12-21 CN CN201811575302.6A patent/CN111352824B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006047741A2 (en) * | 2004-10-27 | 2006-05-04 | Bae Systems Land & Armaments L.P. | Software test environment for regression testing ground combat vehicle software |
| US9304893B1 (en) * | 2013-03-08 | 2016-04-05 | Emc Corporation | Integrated software development and test case management system |
| CN103761189A (en) * | 2014-02-17 | 2014-04-30 | 广东欧珀移动通信有限公司 | Test case management method and system |
| CN107678951A (en) * | 2017-09-21 | 2018-02-09 | 平安科技（深圳）有限公司 | Test exemple automation management method, device, equipment and storage medium |
| CN107704393A (en) * | 2017-09-29 | 2018-02-16 | 武汉斗鱼网络科技有限公司 | Data test method, apparatus and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111352824A (en) | 2020-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107665171B (en) | Automatic regression testing method and device | |
| US8046382B2 (en) | Method and system for software object profile management | |
| CN111639101B (en) | Method, device and system for correlating rule engine system of internet of things and storage medium | |
| CN112925757A (en) | Method, equipment and storage medium for tracking operation log of intelligent equipment | |
| CN113157659A (en) | Log processing method and device | |
| CN111949607B (en) | Method, system and device for monitoring UDT file | |
| CN110674231A (en) | Data lake-oriented user ID integration method and system | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| CN111061733B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| JP4928848B2 (en) | Message converter in computer system integrated management environment. | |
| CN111352824B (en) | Test method and device and computer equipment | |
| US7765188B2 (en) | Taxonomy editor | |
| CN110704699A (en) | Data image construction method and device, computer equipment and storage medium | |
| CN114385551A (en) | Log time-sharing management method, device, equipment and storage medium | |
| CN113010208A (en) | Version information generation method, version information generation device, version information generation equipment and storage medium | |
| CN117194255A (en) | Test data maintenance method, device, equipment and storage medium | |
| CN112068981A (en) | Knowledge base-based fault scanning recovery method and system in Linux operating system | |
| CN116204540A (en) | Operation log recording method, device, equipment and storage medium | |
| CN111259082B (en) | Method for realizing full data synchronization in big data environment | |
| CN110597572B (en) | Service call relation analysis method and computer system | |
| CN110020348B (en) | Early warning method and device for circled events | |
| CN112051987B (en) | Service data processing method, device and equipment, program generating method and device | |
| US11934800B2 (en) | Generating metadata to facilitate code generation | |
| CN113495753A (en) | Project label acquisition method and device, electronic equipment and storage medium | |
| US8352959B2 (en) | Apparatus, system, and method for non-intrusive monitoring of business events |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |