CN114238134A - Test result display method, device, equipment and storage medium - Google Patents
Test result display method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114238134A CN114238134A CN202111580320.5A CN202111580320A CN114238134A CN 114238134 A CN114238134 A CN 114238134A CN 202111580320 A CN202111580320 A CN 202111580320A CN 114238134 A CN114238134 A CN 114238134A
- Authority
- CN
- China
- Prior art keywords
- tested
- test
- cases
- induction
- statistical result
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
-
- 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
Abstract
The application provides a test result display method, a test result display device, test result display equipment and a storage medium, and relates to the technical field of data visualization. In the method, a plurality of cases to be tested can be tested based on the Allure plug-in installed on the Jenkins continuous integration platform to obtain the test results of the cases to be tested, and then the test results can be summarized and counted according to a preset summarizing mode to obtain a summarizing statistical result, and the summarizing statistical result is visually output on a display interface according to a preset display mode. Therefore, the test results are summarized and counted according to the preset summarizing mode, so that the user can compare and analyze the test results from different angles, and the summarizing and counting results are visually output on the display interface according to the preset display mode, so that the test results of the to-be-tested cases become more detailed and intuitive, and the user can understand the test results more easily.
Description
Technical Field
The application relates to the technical field of data visualization, and provides a test result display method, a test result display device, test result display equipment and a storage medium.
Background
At present, although the software testing industry has been developed for a while, manual testing is still a common testing means in software testing, however, with the iteration of software development, there are more and more cases requiring regression testing, so that manual testing is very time-consuming, there may not be enough time to execute after a new version is released, and the execution result needs to be manually recorded case by case. Moreover, to match the efficiency of testing with the sustained delivery, it is difficult to keep up with manual efficiency. Based on this, automatic testing gradually appears, but in the existing automatic testing, after the running of the to-be-tested case is finished, the testing result is often not visual, concise and detailed, so that the problem that the user cannot understand the testing result conveniently and the testing failure cannot be positioned quickly is caused.
Disclosure of Invention
The embodiment of the application provides a test result display method, a test result display device, test result display equipment and a storage medium, and the test result display method, the test result display device, the test result display equipment and the storage medium are used for visually outputting the test result, so that the test result is visual and concise, and a user can conveniently understand the test result.
In one aspect, a test result display method is provided, and the method includes:
testing a plurality of cases to be tested based on an Allure plug-in installed on a Jenkins continuous integration platform;
obtaining respective test results of the plurality of cases to be tested;
carrying out induction statistics on the test results of the multiple test cases to be tested according to a preset induction mode to obtain induction statistical results; the inductive statistical result comprises at least one sub inductive statistical result, and each sub inductive statistical result corresponds to a type of cases to be tested;
and visually outputting the induction statistical result on a display interface according to a preset display mode.
It can be seen that in the embodiment of the application, the test results of the to-be-tested cases are summarized and counted according to the preset summarizing mode, so that a user can compare and analyze the test results from different angles, and in addition, the summarizing and counting results are visually output on the display interface according to the preset display mode, so that the test results of the to-be-tested cases become more detailed and intuitive, and the user can understand the test results more easily.
In a possible implementation manner, the performing inductive statistics on the test result of each of the multiple test cases according to a preset inductive manner includes:
carrying out induction statistics on the test results of the multiple test cases to be tested according to the test types; alternatively, the first and second electrodes may be,
carrying out induction statistics on the test results of the multiple cases to be tested according to the test suite; alternatively, the first and second electrodes may be,
and carrying out induction statistics on the test results of the plurality of cases to be tested according to the test function.
In a possible embodiment, the visually outputting the induction statistical result on a display interface according to a preset display mode includes:
visually outputting the induction statistical result on a display interface according to a mode of a ring diagram; wherein each subinduction statistical result corresponds to a segment of ring length in the ring diagram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a histogram mode; wherein each subinduction statistical result corresponds to a cylinder in the histogram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a line graph mode; wherein each sub-induction statistical result corresponds to a section of broken line in the broken line graph.
In one possible implementation, after obtaining the test result of each of the plurality of test cases to be tested, the method includes:
for each case to be tested, performing:
determining whether the test result of the current case to be tested is failure;
if the test result of the current case to be tested is determined to be failure, acquiring a screenshot of the current case to be tested;
and visually outputting the screenshot of the current use case to be tested on a display interface.
In one aspect, a test result display apparatus is provided, the apparatus comprising:
the case testing unit is used for testing a plurality of cases to be tested based on the Allure plug-in mounted on the Jenkins continuous integration platform;
the result acquisition unit is used for acquiring the respective test results of the multiple test cases to be tested;
the induction statistical unit is used for inducing and counting the test results of the multiple test cases to be tested according to a preset induction mode to obtain induction statistical results; the inductive statistical result comprises at least one sub inductive statistical result, and each sub inductive statistical result corresponds to a type of cases to be tested;
and the visual output unit is used for visually outputting the induction statistical result on a display interface according to a preset display mode.
In a possible implementation, the inductive statistics unit is specifically configured to:
carrying out induction statistics on the test results of the multiple test cases to be tested according to the test types; alternatively, the first and second electrodes may be,
carrying out induction statistics on the test results of the multiple cases to be tested according to the test suite; alternatively, the first and second electrodes may be,
and carrying out induction statistics on the test results of the plurality of cases to be tested according to the test function.
In a possible implementation, the visual output unit is specifically configured to:
visually outputting the induction statistical result on a display interface according to a mode of a ring diagram; wherein each subinduction statistical result corresponds to a segment of ring length in the ring diagram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a histogram mode; wherein each subinduction statistical result corresponds to a cylinder in the histogram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a line graph mode; wherein each sub-induction statistical result corresponds to a section of broken line in the broken line graph.
In a possible implementation manner, the apparatus further includes a screenshot unit, where the screenshot unit is configured to:
for each case to be tested, performing:
determining whether the test result of the current case to be tested is failure;
if the test result of the current case to be tested is determined to be failure, acquiring a screenshot of the current case to be tested;
and visually outputting the screenshot of the current use case to be tested on a display interface.
In one aspect, a computer device is provided, comprising 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 of the above aspect when executing the computer program.
In one aspect, a computer storage medium is provided having computer program instructions stored thereon that, when executed by a processor, implement the steps of the method of the above aspect.
In one aspect, a computer program product is provided, having computer program code stored thereon, for performing the steps of the method of the above aspect when the computer program code runs on a computer.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments or related technologies, the drawings needed to be used in the description of the embodiments or related technologies are briefly introduced below, it is obvious that the drawings in the following description are only the embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of a test result displaying method according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of several display modes provided by an embodiment of the present application;
fig. 4 is a schematic structural diagram of a test result display apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. In the present application, the embodiments and features of the embodiments may be arbitrarily combined with each other without conflict. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here. In addition, in the technical scheme of the application, the data acquisition, transmission, use and the like all meet the requirements of relevant national laws and regulations.
First, some terms in the present application will be explained.
(1) Jenkins is a continuous integration tool developed based on Java and used for monitoring continuous and repeated work. While Continuous Integration (CI) refers to the frequent (multiple times a day) integration of code into the backbone. The goal of continuous integration is to allow for fast iteration of the product while maintaining high quality. The core measure of the method is that before the code is integrated into the backbone, the code must pass automatic test. If only one test case fails, the integration cannot be performed. In the embodiment of the application, the Jenkins continuous integration platform is a platform for continuously integrating the test result of the test case.
(2) The Allure plug-in is a plug-in for generating a test report, supports common languages such as python and Java, and can generate an attractive test report.
At present, in the existing automatic test, after the running of a to-be-tested case is finished, a test result is often not visual, concise and detailed enough, so that the problem that a user cannot understand the test result conveniently and the test failure cannot be positioned quickly is caused.
Based on this, in the embodiment of the application, a test result display method is designed, in the method, a plurality of cases to be tested can be tested based on an alure plug-in installed on a Jenkins continuous integration platform, then, after respective test results of the plurality of cases to be tested are obtained, the respective test results of the plurality of cases to be tested can be summarized and counted according to a preset summarizing mode to obtain a summarizing statistical result, and finally, the summarizing statistical result is visually output on a display interface according to a preset display mode. It can be seen that in the embodiment of the application, the test results of the to-be-tested cases are summarized and counted according to the preset summarizing mode, so that a user can compare and analyze the test results from different angles, and in addition, the summarizing and counting results are visually output on the display interface according to the preset display mode, so that the test results of the to-be-tested cases become more detailed and intuitive, and the user can understand the test results more easily.
The technical scheme of the embodiment of the application can be applied to any possible test result display scene. Fig. 1 is a schematic view of an application scenario provided in the embodiment of the present application. The application scenario of the test result presentation may include the user terminal 10 and the test result presentation device 11.
The user terminal 10 may be a device capable of visually outputting a test result, and may be, for example, a Personal Computer (PC), a notebook computer, or the like.
The test result display device 11 may be a server that provides data storage and data computation for the test result display process, may be an independent physical server, may also be a database cluster or a distributed system formed by a plurality of physical servers, and may also be a cloud server that provides basic cloud computing services such as cloud service, cloud database, cloud computing, cloud function, cloud storage, web service, cloud communication, middleware service, domain name service, security service, CDN, and big data and artificial intelligence platform, but is not limited thereto. The test result presentation apparatus 11 may include one or more processors 101, memory 102, and I/O interfaces 103 to interact with other devices, and the like. In addition, the test result displaying apparatus 11 may further configure a database 104, and the database 104 may be configured to store the test results and data corresponding to the summary statistical results involved in the scheme provided in the embodiment of the present application. The memory 102 of the test result displaying apparatus 11 may store program instructions of the test result displaying method provided in the embodiment of the present application, and when the program instructions are executed by the processor 101, the program instructions can be used to implement the steps of the test result displaying method provided in the embodiment of the present application.
In a possible embodiment, it may be assumed that the user terminal 10 is a notebook computer, and the test result displaying device 11 is a server, then, when the automatic testing device 11 detects that the user performs a testing operation on the user terminal 10 through the I/O interface 103, for example, when a "start testing" button is clicked after a test configuration file is selected to be opened and a corresponding serial port is selected, the processor 101 of the test result displaying device 11 runs a program instruction of the test result displaying method stored in the memory 102 to perform an automatic test on a trial example to be tested, and outputs a test result visually, so that the test result is intuitive and concise, and is convenient for the user to understand. And the corresponding data, such as test results, summary statistics, etc., generated during the execution of the program instructions are stored in the database 104.
Of course, the method provided in the embodiment of the present application is not limited to be used in the application scenario shown in fig. 1, and may also be used in other possible application scenarios, and the embodiment of the present application is not limited. The functions that can be implemented by each device in the application scenario shown in fig. 1 will be described in the following method embodiments, and will not be described in detail herein. Hereinafter, the method of the embodiment of the present application will be described with reference to the drawings.
As shown in fig. 2, a schematic flow chart of a test result displaying method provided in the embodiment of the present application is provided, where the method may be executed by the test result displaying apparatus 11 in fig. 1, which is not limited in this embodiment of the present application, and the flow of the method is described as follows.
Step 201: and testing a plurality of cases to be tested based on the Allure plug-in installed on the Jenkins continuous integration platform.
In order to generate the test result in multiple language environments as much as possible, therefore, in the embodiment of the present application, the alure plug-in may be used to generate the test result, and in addition, in order to facilitate rapid testing of multiple cases to be tested, in the embodiment of the present application, the alure plug-in may be installed on a Jenkins continuous integration platform, so as to rapidly generate the test result.
Step 202: and obtaining respective test results of a plurality of test cases to be tested.
In the embodiment of the application, after a plurality of cases to be tested are input to a Jenkins-based continuous integration platform, the cases to be tested are tested through an Allure plug-in on the platform, and then respective test results of the cases to be tested can be obtained.
Step 203: and carrying out induction statistics on the test results of the multiple test cases to be tested according to a preset induction mode to obtain induction statistical results.
In the embodiment of the application, the induction statistical result may include at least one sub-induction statistical result, and each sub-induction statistical result may correspond to a class of cases to be tested.
Specifically, in order to enable a user to compare and analyze test results from different angles, in the embodiment of the present application, after respective test results of a plurality of test cases to be tested are obtained, the test results may be summarized and counted according to a preset summarizing manner, so that a situation that the user needs to manually process the test results when performing comparison and analysis on the test results is avoided, not only is time of the user greatly saved, but also a situation that the statistics is mistaken due to carelessness during manual processing is avoided.
Step 204: and visually outputting the induction statistical result on a display interface according to a preset display mode.
In the embodiment of the application, in order to meet the personalized requirements of the user, when the summary statistical result is displayed, the user can select a favorite display mode from preset display modes to visually output the summary statistical result on the display interface.
Specifically, the induction statistical result may be visually output according to the following display modes, as shown in fig. 3, which are schematic diagrams of the display modes provided in the embodiments of the present application.
The first method comprises the following steps: and visually outputting the induction statistical result on a display interface according to a mode of a ring diagram.
In the embodiment of the present application, as shown in fig. 3(a), each sub-summary statistic result may correspond to a segment of the ring length in the ring graph, where the specific length of the ring length is related to the ratio of the number of the cases to be tested in the sub-summary statistic result to the number of the total cases to be tested, for example, the sub-summary statistic result 1 contains 25 cases to be tested, and the current total cases to be tested is 100, so that the ring length corresponding to the sub-summary statistic result 1 in the ring graph shown in fig. 3(a) occupies 1/4 of the total ring.
And the second method comprises the following steps: and visually outputting the induction statistical result on a display interface according to a histogram mode.
In the embodiment of the present application, as shown in fig. 3(b), each sub-summary statistic result may correspond to a column in the histogram, where the height of the column is related to the number of cases to be tested in the sub-summary statistic result, for example, sub-summary statistic result 1 contains 25 cases to be tested, and then the corresponding column height of the sub-summary statistic result 1 in the histogram shown in fig. 3(b) should be 25. Of course, the subject height may also be represented not by a number, but by a ratio of the number of the cases to be tested to the total number of the cases to be tested in the sub-summary statistical result, or by any other manner satisfactory to the user.
And the third is that: and visually outputting the induction statistical result on a display interface according to a line graph mode.
In the embodiment of the present application, as shown in fig. 3(c), each sub-summary statistic result may correspond to a segment of a broken line in a broken line graph, wherein, similar to fig. 3(b), the height of each turning point of the broken line graph is also related to the number of cases to be tested in the sub-summary statistic result, for example, 25 cases to be tested are contained in sub-summary statistic result 1, and then the height of the corresponding turning point of the sub-summary statistic result 1 in the broken line graph shown in fig. 3(c) should be 25. Of course, the turning point height can also be expressed by the ratio of the number of the cases to be tested to the total number of the cases to be tested in the sub-induction statistical result, or any other satisfactory manner.
Of course, in the embodiment of the present application, the summary statistical result may also be visually output on the display interface according to other display manners, for example, visually output according to a sector graph, a radar graph, a graph, and the like.
In a possible embodiment, in order to enable the user to perform the comparison analysis on the test results from different angles, the test results may be subjected to inductive statistics specifically according to the following inductive manners.
The first method comprises the following steps: and carrying out induction statistics on the test results of the multiple test cases to be tested according to the test types.
In the embodiment of the present application, the test types may be specifically classified into a "black box test" and a "white box test", and based on this, the number statistics may be performed on the test results of the to-be-tested cases that are tested by the "black box test" and the "white box test", respectively.
And the second method comprises the following steps: and carrying out induction statistics on the test results of the multiple cases to be tested according to the test suite.
In the embodiment of the present application, for example, the test suite may be a test suite including only "smoke test" test cases, or a test suite for a specific function of the system. Based on this, the test results of the to-be-tested cases tested by the smoking test can be subjected to quantity statistics, or the test results of the to-be-tested cases tested by the system specific function can be subjected to quantity statistics.
And the third is that: and carrying out induction statistics on the test results of the multiple test cases to be tested according to the test functions.
In the embodiment of the present application, for example, when a newly developed mobile phone is tested, the test functions of the newly developed mobile phone can be roughly divided into a communication function, a display function, a touch function, and the like, and based on this, a plurality of examples to be tested corresponding to the newly developed mobile phone can be specifically divided into: further, for the test results of a plurality of to-be-tested cases corresponding to the newly developed mobile phone, the quantity statistics can be performed according to the communication function, the display function, the touch function and the like. Of course, the test results may not be subjected to inductive statistics, but the test cases to be tested are directly shown through the overview chart.
In a possible implementation manner, in order to facilitate a user to quickly locate a defect position, in an embodiment of the present application, the defect position may be quickly located by obtaining a screenshot of a failed case, where, because a process of determining whether each to-be-tested case is the failed case is the same, a specific description is given here by taking the to-be-tested case 1 as an example, as shown in fig. 4, a flow diagram for obtaining a screenshot of a failed case provided in an embodiment of the present application may be implemented by the test result display device 11 in fig. 1, which is not limited in the embodiment of the present application, and a specific flow is described as follows.
Step 401: it is determined whether the test result of the case 1 to be tested is a failure.
Step 402: and if the test result of the case 1 to be tested is determined to be failure, acquiring the screenshot of the case 1 to be tested.
In the embodiment of the present application, whether the test of the to-be-tested case 1 fails may be determined according to the content indicated in the test result of the to-be-tested case 1, for example, the test result indicates that "the operating system path has a fault", so that the test condition of the to-be-tested case 1 is not a condition expected by the user, and then the to-be-tested case 1 may be subjected to this time.
Step 403: and visually outputting the screenshot of the case 1 to be tested on a display interface.
In the embodiment of the application, after the screenshot of the test result of the to-be-tested case 1 is obtained, the screenshot can be directly visually output on a display interface, so that a user can check the failed case in real time, the screenshot can be stored in a local database, and when the user needs to position the tested defect position, the screenshot can be directly obtained from the local database, so that the defect position can be quickly positioned.
In a possible implementation manner, the screenshot of the failed use case can be obtained through an implanted hook function, so that the corresponding failed use case is screenshot each time the failed use case occurs.
In a possible implementation, before testing the sample to be tested, the configuration-related test software and the test result generation software are installed. Specifically, only the 'dependency' needs to be configured for the automatic test configuration under the java + maven language environment. For example, in order to ensure the uniqueness of a maven item, the coordinates of the maven item may be configured in "dependency", that is, the group id (groupId) and the item name (artifactId) are configured, for example, groupId is configured as "io.
For the automatic test configuration under the python language environment, the plug-in is installed only through the pip install all-lost. For example, for Jenkins under the python language environment, the specific steps for installing the Allure plug-in on the continuous integration platform are as follows: finding an instruction menu in a plug Manager of a Jenkins continuous integration platform, and then installing an Allue Jenkins plug-in the instruction menu.
In one possible implementation, the test results may also be presented in multiple languages, such as chinese, english, japanese, and french, for example, in the present application. In addition, various development languages and frameworks can be adopted for programming development, such as Java, Python, JavaScript, Ruby, Groovy, PHP,. Net, and Scala languages.
In summary, in the embodiment of the present application, the test results of the to-be-tested cases are summarized and counted according to the preset summarizing manner, so that the user can compare and analyze the test results from different angles, and in addition, the summarizing and counting results are visually output on the display interface according to the preset display manner, so that the test results of the to-be-tested cases become more detailed and intuitive, and the user can understand the test results more easily. In addition, the positions of the defects can be quickly positioned by screenshot of the failed use case.
As shown in fig. 4, based on the same inventive concept, an embodiment of the present application provides a test result displaying apparatus, where the apparatus 40 includes:
the case testing unit 401 is used for testing a plurality of cases to be tested based on an Allure plug-in installed on the Jenkins continuous integration platform;
a result obtaining unit 402, configured to obtain a test result of each of the multiple test cases to be tested;
the induction statistical unit 403 is configured to perform induction statistics on the test results of the multiple test cases to be tested according to a preset induction mode to obtain induction statistical results; wherein, the inductive statistical result comprises at least one sub-inductive statistical result, and each sub-inductive statistical result corresponds to a class of cases to be tested;
and the visual output unit 404 is configured to perform visual output on the induction statistical result on the display interface according to a preset display mode.
In a possible implementation, the summary statistics unit 403 is specifically configured to:
carrying out induction statistics on the test results of the multiple test cases to be tested according to the test types; alternatively, the first and second electrodes may be,
carrying out induction statistics on the test results of the multiple cases to be tested according to the test suite; alternatively, the first and second electrodes may be,
and carrying out induction statistics on the test results of the multiple test cases to be tested according to the test functions.
In a possible implementation, the visual output unit 404 is specifically configured to:
visually outputting the induction statistical result on a display interface according to a mode of a ring diagram; wherein, each sub-induction statistical result corresponds to a section of ring length in the ring graph; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a histogram mode; wherein each subinduction statistical result corresponds to a cylinder in the histogram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a line graph mode; wherein each sub-induction statistical result corresponds to a section of broken line in the broken line graph.
In a possible implementation manner, the apparatus further includes a screenshot unit 405, where the screenshot unit 405 is configured to:
for each case to be tested, performing:
determining whether the test result of the current case to be tested is failure;
if the test result of the current case to be tested is determined to be failure, acquiring a screenshot of the current case to be tested;
and visually outputting the screenshot of the current use case to be tested on a display interface.
The apparatus may be configured to execute the method in the embodiment shown in fig. 2 to fig. 3, and therefore, for functions and the like that can be realized by each functional unit of the apparatus, reference may be made to the description of the embodiment shown in fig. 2 to fig. 3, which is not repeated here. It should be noted that the functional units shown by the dashed boxes in fig. 4 are unnecessary functional units of the apparatus.
Referring to fig. 5, based on the same technical concept, the embodiment of the present application further provides a computer device 50, which may include a memory 501 and a processor 502.
The memory 501 is used for storing computer programs executed by the processor 502. The memory 501 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to use of the computer device, and the like. The processor 502 may be a Central Processing Unit (CPU), a digital processing unit, or the like. The specific connection medium between the memory 501 and the processor 502 is not limited in the embodiments of the present application. In the embodiment of the present application, the memory 501 and the processor 502 are connected by the bus 503 in fig. 5, the bus 503 is represented by a thick line in fig. 5, and the connection manner between other components is merely for illustrative purposes and is not limited thereto. The bus 503 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.
The memory 501 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 501 may also be a non-volatile memory (non-volatile memory) such as, but not limited to, a read-only memory (rom), a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD), or any other medium which can be used to carry or store desired program code in the form of instructions or data structures and which can be accessed by a computer. The memory 501 may be a combination of the above memories.
A processor 502 for executing the method performed by the apparatus in the embodiments shown in fig. 2-3 when calling the computer program stored in the memory 501.
In some possible embodiments, various aspects of the methods provided herein may also be implemented in the form of a program product including program code for causing a computer device to perform the steps of the methods according to various exemplary embodiments of the present application described above in this specification when the program product is run on the computer device, for example, the computer device may perform the methods as described in the embodiments shown in fig. 2-3.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. Alternatively, the integrated unit of the present invention may be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a separate product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media that can store program code.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (11)
1. A test result display method is characterized by comprising the following steps:
testing a plurality of cases to be tested based on an Allure plug-in installed on a Jenkins continuous integration platform;
obtaining respective test results of the plurality of cases to be tested;
carrying out induction statistics on the test results of the multiple test cases to be tested according to a preset induction mode to obtain induction statistical results; the inductive statistical result comprises at least one sub inductive statistical result, and each sub inductive statistical result corresponds to a type of cases to be tested;
and visually outputting the induction statistical result on a display interface according to a preset display mode.
2. The method of claim 1, wherein the performing inductive statistics on the test results of each of the plurality of test cases according to a preset inductive manner includes:
carrying out induction statistics on the test results of the multiple test cases to be tested according to the test types; alternatively, the first and second electrodes may be,
carrying out induction statistics on the test results of the multiple cases to be tested according to the test suite; alternatively, the first and second electrodes may be,
and carrying out induction statistics on the test results of the plurality of cases to be tested according to the test function.
3. The method of claim 1, wherein visually outputting the induction statistical result on a display interface according to a preset display mode comprises:
visually outputting the induction statistical result on a display interface according to a mode of a ring diagram; wherein each subinduction statistical result corresponds to a segment of ring length in the ring diagram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a histogram mode; wherein each subinduction statistical result corresponds to a cylinder in the histogram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a line graph mode; wherein each sub-induction statistical result corresponds to a section of broken line in the broken line graph.
4. The method of claim 1, wherein after obtaining test results for each of the plurality of use cases to be tested, the method comprises:
for each case to be tested, performing:
determining whether the test result of the current case to be tested is failure;
if the test result of the current case to be tested is determined to be failure, acquiring a screenshot of the current case to be tested;
and visually outputting the screenshot of the current use case to be tested on a display interface.
5. A test result presentation apparatus, the apparatus comprising:
the case testing unit is used for testing a plurality of cases to be tested based on the Allure plug-in mounted on the Jenkins continuous integration platform;
the result acquisition unit is used for acquiring the respective test results of the multiple test cases to be tested;
the induction statistical unit is used for inducing and counting the test results of the multiple test cases to be tested according to a preset induction mode to obtain induction statistical results; the inductive statistical result comprises at least one sub inductive statistical result, and each sub inductive statistical result corresponds to a type of cases to be tested;
and the visual output unit is used for visually outputting the induction statistical result on a display interface according to a preset display mode.
6. The apparatus of claim 5, wherein the inductive statistics unit is specifically configured to:
carrying out induction statistics on the test results of the multiple test cases to be tested according to the test types; alternatively, the first and second electrodes may be,
carrying out induction statistics on the test results of the multiple cases to be tested according to the test suite; alternatively, the first and second electrodes may be,
and carrying out induction statistics on the test results of the plurality of cases to be tested according to the test function.
7. The apparatus of claim 5, wherein the visual output unit is specifically configured to:
visually outputting the induction statistical result on a display interface according to a mode of a ring diagram; wherein each subinduction statistical result corresponds to a segment of ring length in the ring diagram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a histogram mode; wherein each subinduction statistical result corresponds to a cylinder in the histogram; alternatively, the first and second electrodes may be,
visually outputting the induction statistical result on a display interface according to a line graph mode; wherein each sub-induction statistical result corresponds to a section of broken line in the broken line graph.
8. The apparatus of claim 5, further comprising a screenshot unit, wherein the screenshot unit is to:
for each case to be tested, performing:
determining whether the test result of the current case to be tested is failure;
if the test result of the current case to be tested is determined to be failure, acquiring a screenshot of the current case to be tested;
and visually outputting the screenshot of the current use case to be tested on a display interface.
9. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor,
the processor, when executing the computer program, realizes the steps of the method of any of claims 1-4.
10. A computer storage medium having computer program instructions stored thereon, wherein,
the computer program instructions, when executed by a processor, implement the steps of the method of any one of claims 1 to 4.
11. A computer program product comprising, in a computer readable medium,
the computer program product comprises: computer program code which, when run on a computer, causes the computer to perform the method according to any of the preceding claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111580320.5A CN114238134A (en) | 2021-12-22 | 2021-12-22 | Test result display method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111580320.5A CN114238134A (en) | 2021-12-22 | 2021-12-22 | Test result display method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114238134A true CN114238134A (en) | 2022-03-25 |
Family
ID=80761211
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111580320.5A Pending CN114238134A (en) | 2021-12-22 | 2021-12-22 | Test result display method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114238134A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115080572A (en) * | 2022-07-20 | 2022-09-20 | 四川长虹电器股份有限公司 | Automatic regression testing method for media resource retrieval interface |
| CN116401175A (en) * | 2023-05-29 | 2023-07-07 | 云筑信息科技(成都)有限公司 | Processing method for additionally writing pictures based on json file |
| CN116738020A (en) * | 2023-04-17 | 2023-09-12 | 深圳市晶存科技有限公司 | Method, system, device and storage medium for displaying chip test result |
-
2021
- 2021-12-22 CN CN202111580320.5A patent/CN114238134A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115080572A (en) * | 2022-07-20 | 2022-09-20 | 四川长虹电器股份有限公司 | Automatic regression testing method for media resource retrieval interface |
| CN116738020A (en) * | 2023-04-17 | 2023-09-12 | 深圳市晶存科技有限公司 | Method, system, device and storage medium for displaying chip test result |
| CN116401175A (en) * | 2023-05-29 | 2023-07-07 | 云筑信息科技(成都)有限公司 | Processing method for additionally writing pictures based on json file |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114238134A (en) | Test result display method, device, equipment and storage medium | |
| CN107506300B (en) | User interface testing method, device, server and storage medium | |
| CN108459964B (en) | Test case selection method, device, equipment and computer readable storage medium | |
| CN109800258B (en) | Data file deployment method, device, computer equipment and storage medium | |
| CN108459954B (en) | Application program vulnerability detection method and device | |
| CN111258913A (en) | Automatic algorithm testing method and device, computer system and readable storage medium | |
| CN112882930B (en) | Automatic test method and device, storage medium and electronic equipment | |
| CN109966742B (en) | Method and device for acquiring rendering performance data in game running | |
| CN111475411A (en) | Server problem detection method, system, terminal and storage medium | |
| CN112732587A (en) | Method and device for acquiring automatic test log, electronic equipment and storage medium | |
| CN114490375A (en) | Method, device and equipment for testing performance of application program and storage medium | |
| CN114546738A (en) | Server general test method, system, terminal and storage medium | |
| CN117407312A (en) | Application testing method, device, computer equipment and storage medium | |
| CN115237441A (en) | Upgrade test method, device and medium based on cloud platform | |
| CN115712571A (en) | Interactive service test device, interactive service test device, computer equipment and storage medium | |
| CN115757014A (en) | Power consumption testing method and device | |
| CN114676066A (en) | Security testing method and device for target application, electronic equipment and storage medium | |
| CN113918373A (en) | Memory leak monitoring method, memory leak detection method and corresponding devices | |
| CN108563578B (en) | SDK compatibility detection method, device, equipment and readable storage medium | |
| CN112965910A (en) | Automatic regression testing method and device, electronic equipment and storage medium | |
| CN110716855B (en) | Processor instruction set testing method and device | |
| CN116594914B (en) | Method, device, equipment and storage medium for generating test data | |
| CN116383095B (en) | Smoking test method and system based on RPA robot and readable storage medium | |
| CN110427935B (en) | Webpage element identification method and server | |
| CN116974940A (en) | Interface testing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |