Nothing Special   »   [go: up one dir, main page]

CN115248783B - Software testing method, system, readable storage medium and computer equipment - Google Patents

Software testing method, system, readable storage medium and computer equipment Download PDF

Info

Publication number
CN115248783B
CN115248783B CN202211170103.3A CN202211170103A CN115248783B CN 115248783 B CN115248783 B CN 115248783B CN 202211170103 A CN202211170103 A CN 202211170103A CN 115248783 B CN115248783 B CN 115248783B
Authority
CN
China
Prior art keywords
test
software
test case
data
tested
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
Application number
CN202211170103.3A
Other languages
Chinese (zh)
Other versions
CN115248783A (en
Inventor
田丰
万姜涛
徐晓明
黄伟
祝华锋
丁建中
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nanchang Senmu Technology Co ltd
Original Assignee
Jiangxi Firefly Microelectronics Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Jiangxi Firefly Microelectronics Technology Co ltd filed Critical Jiangxi Firefly Microelectronics Technology Co ltd
Priority to CN202211170103.3A priority Critical patent/CN115248783B/en
Publication of CN115248783A publication Critical patent/CN115248783A/en
Application granted granted Critical
Publication of CN115248783B publication Critical patent/CN115248783B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/3684—Test management for test design, e.g. generating new test cases
    • 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
    • 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

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 invention provides a software testing method, a system, a readable storage medium and computer equipment, wherein the method comprises the following steps: constructing a test scene model based on version data and software types of software to be tested and test environment configuration data; acquiring a test source code according to the software type, and generating a test case basic file in a test scene model based on the test source code; customizing the test nodes, and combining the test nodes and the test case basic files to obtain a plurality of test case files; performing preliminary test on the software to be tested by using each test case file to obtain a preliminary test result; calculating the error correction degree and the reliability of each test case file based on the preliminary test result, and determining the demand degree of each test case file according to the actual test condition of each test case file; and constructing a software test model according to the error correction degree, the reliability and the demand degree, and performing software test on the software to be tested according to the software test model and the priority regulation rule to obtain a final test result.

Description

Software testing method, system, readable storage medium and computer equipment
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a software testing method, a software testing system, a readable storage medium, and a computer device.
Background
With the rapid development of science and technology and the improvement of living standard of people, various software also come up endlessly in life, so the number of software development is gradually increased.
With the increase of the number of software, version iteration is also frequent, and in order to enable a user to use the software normally, the software is usually tested before the software is on line, so as to find out software errors (errors or other defects) and verify whether a software product is suitable for use, so as to ensure the normal operation of the software.
Aiming at software testing, a software developer is generally required to test software by the software developer, so that the software developer is required to develop a testing system aiming at the software and carry out single testing on the software by utilizing the testing system, so that the software testing needs higher professional skill level, the software developer has larger workload and lower working efficiency, and a single testing mode cannot achieve better software testing results; moreover, in the process of software testing, regression testing needs to be performed on the test case to ensure that the newly added code can solve the problems existing in the testing, however, as the development quantity of the testing system increases, the number of times of regression testing is gradually increased, so that the cost of the regression testing is higher and higher, and the error rate is gradually increased.
Disclosure of Invention
In view of the above, it is an object of the present invention to provide a software testing method, system, readable storage medium and computer device to solve at least the above-mentioned deficiencies in the art.
The invention provides a software testing method, which comprises the following steps:
correspondingly constructing a test scene model based on version data and software types of software to be tested and test environment configuration data;
obtaining a test source code of the software to be tested according to the software type, and correspondingly generating a test case basic file in the test scene model based on the test source code;
customizing a test node, and combining the test node and the test case basic file to obtain a plurality of test case files;
performing preliminary test on the software to be tested by using each test case file to obtain a corresponding preliminary test result;
calculating the error correction degree and the reliability degree of each test case file based on the preliminary test result, and determining the demand degree of each test case file according to the actual test condition of each test case file;
and constructing a software testing model according to the error correction degree, the reliability and the demand degree, and performing software testing on the software to be tested according to the software testing model and a priority regulation rule to obtain a final testing result.
Further, before the step of correspondingly constructing the test scenario model based on the version data and the software type of the software to be tested and the test environment configuration data, the method further comprises the following steps:
acquiring corresponding simulated environment data based on the software type of software to be tested, creating an environment editor according to the software type, and editing data of the environment editor by using a data editing mode to obtain a scene editor corresponding to the software to be tested;
and acquiring current environment data, and optimizing the scene editor according to the simulated environment data and the current environment data to obtain test environment configuration data corresponding to the software to be tested.
Further, the step of correspondingly constructing a test scene model based on the version data and the software type of the software to be tested and the test environment configuration data comprises the following steps:
correspondingly creating a modeling editor according to the software type, and acquiring a plurality of minimum modeling data base classes of the software to be tested according to the version data;
and combining each modeling data base class with the testing environment configuration data, and inputting the combined data into the modeling editor to generate the testing scene model.
Further, the step of correspondingly generating a test case base file in the test scenario model based on the test source code includes:
calling the requirement specification of the software to be tested, and correspondingly generating a test basic file according to the test source code;
and selecting a test path according to the requirement specification, and correspondingly generating a test case basic file in the test scene model through the test path and the test basic file.
Further, the step of calculating the error correction degree and the reliability degree of each test case file based on the preliminary test result comprises the following steps:
acquiring the error times of each test case file in the preliminary test result, and calculating the error correction degree of each test case file according to the following formula based on the error times of each test case file:
Figure 910604DEST_PATH_IMAGE001
；
in the formula,
Figure 811564DEST_PATH_IMAGE002
for test case files
Figure 702160DEST_PATH_IMAGE003
To (1) a
Figure 295952DEST_PATH_IMAGE004
The initial value of the error times in the secondary test is 0;
Figure 639209DEST_PATH_IMAGE005
for test case files
Figure 91662DEST_PATH_IMAGE003
To (1)
Figure 836765DEST_PATH_IMAGE004
Error correction degree in the secondary test;
Figure 601458DEST_PATH_IMAGE006
for test case files
Figure 432011DEST_PATH_IMAGE003
To (1)
Figure 940353DEST_PATH_IMAGE007
Error correction degree in the secondary test;
obtaining the operation condition of each test case file in the preliminary test result, and calculating the reliability of each test case file according to the following formula based on the operation condition of each test case file:
Figure 805541DEST_PATH_IMAGE008
；
in the formula,
Figure 741135DEST_PATH_IMAGE009
for test cases
Figure 793405DEST_PATH_IMAGE003
To (1)
Figure 856170DEST_PATH_IMAGE004
The running condition in the secondary test is 1 when the running is abnormal and 0 when the running is normal;
Figure 575864DEST_PATH_IMAGE010
for test case files
Figure 682361DEST_PATH_IMAGE003
To (1)
Figure 221927DEST_PATH_IMAGE004
Reliability in secondary test;
Figure 72071DEST_PATH_IMAGE011
for test case files
Figure 646272DEST_PATH_IMAGE003
To (1) a
Figure 923669DEST_PATH_IMAGE012
Reliability at the time of secondary test.
The invention also provides a software testing system, comprising:
the test scene construction module is used for correspondingly constructing a test scene model based on version data and software types of the software to be tested and test environment configuration data;
the test code processing module is used for acquiring a test source code of the software to be tested according to the software type and correspondingly generating a test case basic file in the test scene model on the basis of the test source code;
the test case generation module is used for customizing test nodes and combining the test nodes and the test case basic files to obtain a plurality of test case files;
the preliminary test module is used for carrying out preliminary test on the software to be tested by utilizing each test case file to obtain a corresponding preliminary test result;
the model data calculation module is used for calculating the error correction degree and the reliability of each test case file based on the preliminary test result and determining the demand degree of each test case file according to the actual test condition of each test case file;
and the test model building module is used for building a software test model according to the error correction degree, the reliability and the demand degree, and performing software test on the software to be tested according to the software test model and a priority regulation rule to obtain a final test result.
Further, the system further comprises:
the scene editing module is used for acquiring corresponding simulated environment data based on the software type of the software to be tested, creating an environment editor according to the software type, and editing data of the environment editor by using a data editing mode to obtain the scene editor corresponding to the software to be tested;
and the test environment configuration module is used for acquiring current environment data and optimizing the scene editor according to the simulation environment data and the current environment data so as to obtain test environment configuration data corresponding to the software to be tested.
Further, the test scenario construction module includes:
the modeling editing unit is used for correspondingly creating a modeling editor according to the software type and acquiring a plurality of minimum modeling data base classes of the software to be tested according to the version data;
and the scene construction unit is used for combining each modeling data base class with the testing environment configuration data and inputting the combined data into the modeling editor to generate the testing scene model.
Further, the test code processing module includes:
the requirement specification acquisition unit is used for calling a requirement specification of the software to be tested and correspondingly generating a test basic file according to the test source code;
and the test case processing unit is used for selecting a test path according to the requirement specification and correspondingly generating a test case basic file in the test scene model through the test path and the test basic file.
The invention also proposes a readable storage medium on which a computer program is stored which, when being executed by a processor, implements the software testing method described above.
The invention also provides a computer device, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the software testing method when executing the computer program.
According to the software testing method, the software testing system, the readable storage medium and the computer device, the testing scene model is correspondingly constructed by acquiring the testing environment configuration data, the version data and the software type, so that the software testing can be carried out in the testing scene model, when different software is required, the testing scene model can be reconstructed according to the version data and the software type of different products, the corresponding development of different testing systems for different software is avoided, the workload is reduced, and the working efficiency is improved; specifically, the test case file is generated through the user-defined node and the test case base file, so that the software test process can be controlled according to the user-defined node of a worker, and the software test accuracy is improved; furthermore, the error checking capability of the regression test is improved through the error correction degree, the reliability and the demand degree of each test case file, and the efficiency of the regression test is further improved.
Drawings
FIG. 1 is a flow chart of a software testing method according to a first embodiment of the present invention;
FIG. 2 is a detailed flowchart of step S101 in FIG. 1;
FIG. 3 is a detailed flowchart of step S102 in FIG. 1;
FIG. 4 is a flowchart of a software testing method according to a second embodiment of the present invention;
FIG. 5 is a block diagram of a software testing system according to a third embodiment of the present invention;
fig. 6 is a block diagram showing a configuration of a computer device according to a fourth embodiment of the present invention.
The following detailed description will further illustrate the invention in conjunction with the above-described figures.
Detailed Description
To facilitate an understanding of the invention, the invention will now be described more fully with reference to the accompanying drawings. Several embodiments of the invention are presented in the drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
It will be understood that when an element is referred to as being "secured to" another element, it can be directly on the other element or intervening elements may also be present. When an element is referred to as being "connected" to another element, it can be directly connected to the other element or intervening elements may also be present. The terms "vertical," "horizontal," "left," "right," and the like as used herein are for illustrative purposes only.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
Example one
Referring to fig. 1, a software testing method according to a first embodiment of the present invention is shown, and the software testing method specifically includes steps S101 to S106:
s101, correspondingly constructing a test scene model based on version data and software types of software to be tested and test environment configuration data;
further, referring to fig. 2, the step S101 specifically includes steps S1011 to S1012:
s1011, correspondingly creating a modeling editor according to the software type, and acquiring a plurality of minimum modeling data base classes of the software to be tested according to the version data;
and S1012, combining each modeling data base class with the testing environment configuration data, and inputting the combined data into the modeling editor to generate the testing scene model.
In this embodiment, a modeling database is pre-constructed, modeling functions and modeling parameters required by each software type are pre-stored in the modeling database, when the software type is obtained, a modeling editor is created by using the corresponding modeling functions and modeling parameters, and a plurality of minimum modeling data base classes are obtained according to the version data of the software to be tested, wherein the minimum modeling data base class is a minimum graphical model element for data modeling.
Furthermore, each minimum graphical model element and the test environment configuration data are combined into attributes and behavior functions of the model elements, and a test scenario model is generated through the attributes and the behavior functions of the model elements.
S102, obtaining a test source code of the software to be tested according to the software type, and correspondingly generating a test case basic file in the test scene model based on the test source code;
further, referring to fig. 3, the step S102 specifically includes steps S1021 to S1022:
s1021, calling the requirement specification of the software to be tested, and correspondingly generating a test basic file according to the test source code;
s1022, selecting a test path according to the requirement specification, and correspondingly generating a test case basic file in the test scene model through the test path and the test basic file.
In specific implementation, the test source code of the software to be tested is searched according to the software type, and by means of constructing a software type and test source code mapping table, when the software type is obtained, the test source code corresponding to the software type can be obtained by means of table lookup.
It should be noted that, in other embodiments, the test source code of the software to be tested can be found by pre-storing the test source code of the software to be tested in the registry of the software to be tested and acquiring the registry.
Further, a requirement specification of the software to be tested is obtained, wherein an execution model of the software to be tested can be constructed through the specification requirement specification, the execution model is composed of a plurality of atomic models, and the atomic models are the minimum units of a test process and comprise a test protocol, a test condition, a test path and result verification. And selecting a corresponding test path by using the test conditions of the test software, and generating a test case basic file by corresponding the test path and the test basic file in a test scene model.
S103, self-defining test nodes, and combining the test nodes and the test case basic files to obtain a plurality of test case files;
in specific implementation, a test scene model comprises a plurality of test node attributes, a user creates a test node according to the test node attributes in a user-defined mode, the test node comprises a node attribute identifier and node configuration data, wherein the node attribute identifier is a unique identifier of the test node attributes, and information of the corresponding test node attributes can be obtained through the identifier; the node attribute data comprises node attributes customized by a user according to requirements, such as: the user requirement is a connectivity test, and the node attribute is a connectivity test node attribute (attribute information such as a connectivity test interface is constructed).
And after the user-defined test nodes are obtained, combining the test nodes with the test case basic file to further obtain the test case file.
S104, performing preliminary test on the software to be tested by using each test case file to obtain a corresponding preliminary test result;
it should be noted that, because the test case file does not have the execution capability, the test case file needs to be converted into an executable test execution file, the test case file needs to be converted into a C language or programming language program file, and the test software to be tested is tested through the test execution file to obtain a corresponding test result.
S105, calculating the error correction degree and the reliability of each test case file based on the preliminary test result, and determining the demand degree of each test case file according to the actual test condition of each test case file;
it should be noted that, in the software testing process, when a tester finds that a test case causes an exception in the testing process, the abnormal part needs to be repaired, however, in order to know whether the repaired code can solve the exception or cause another exception, the test case needs to be retested again, and the testing process is a regression test. Generally, in the process of software development, the proportion of regression testing of software testing is large, and due to rapid iteration of software, the software also needs to be modified for multiple times, each modification means that regression testing needs to be performed.
Specifically, the number of errors of each test case file in the preliminary test result is obtained, and the error correction degree of each test case file is calculated according to the following formula (1) based on the number of errors of each test case file:
formula (1):
Figure 216110DEST_PATH_IMAGE001
；
in the formula,
Figure 355099DEST_PATH_IMAGE002
for test case files
Figure 314964DEST_PATH_IMAGE003
To (1) a
Figure 700946DEST_PATH_IMAGE004
The error times in the secondary test is 0 in an initial value;
Figure 277421DEST_PATH_IMAGE005
for test case files
Figure 407051DEST_PATH_IMAGE003
To (1) a
Figure 18161DEST_PATH_IMAGE004
Error correction degree in the secondary test;
Figure 575045DEST_PATH_IMAGE013
for test case files
Figure 373236DEST_PATH_IMAGE003
To (1) a
Figure 572136DEST_PATH_IMAGE014
Error correction degree in the secondary test;
as can be seen from the above formula (1), the error correction degree of each test is the superposition of the current error frequency and the previous error frequency, so that the error correction degree gradually increases with the progress of the test, and the fact that the error correction degree does not increase means that the code repair has already solved the abnormal problem, the execution sequence of the test case file does not need to be further improved, and the gradually increasing error correction degree means that the code repair has not solved the abnormal problem or still has a problem.
Further, the operation condition of each test case file in the preliminary test result is obtained, and the reliability of each test case file is calculated according to the following formula (2) based on the operation condition of each test case file:
formula (2):
Figure 522906DEST_PATH_IMAGE015
；
in the formula,
Figure 313007DEST_PATH_IMAGE009
for test cases
Figure 67337DEST_PATH_IMAGE003
To (1)
Figure 804349DEST_PATH_IMAGE004
The running condition in the secondary test is 1 when the running is abnormal, and 0 when the running is normal;
Figure 124472DEST_PATH_IMAGE010
for test case files
Figure 23157DEST_PATH_IMAGE003
To (1) a
Figure 61521DEST_PATH_IMAGE004
Reliability in secondary test;
Figure 336644DEST_PATH_IMAGE011
for test case files
Figure 259076DEST_PATH_IMAGE003
To (1)
Figure 594243DEST_PATH_IMAGE014
Reliability in the next test.
It should be noted that, in this embodiment, the reliability is an execution condition of the test case file in the running process, and when the test case file is run, a test cannot run normally due to the test case file or cannot run due to the test case file after being repaired by the code; and if the test case file which cannot be operated is not found, the reliability of the test case file is taken as 0.
As can be seen from the above formula (2), the reliability and the error correction are the same, and will gradually increase according to the number of times that the test case file cannot be run in the test process, and if the test case file is executed for multiple times, the reliability of the test case file continuously increases, which means that the test case file has an exception or the code repair is not a problem.
In this embodiment, the demand degree is the importance degree according to each demand in the system to divide the demand, and the key function used by the user is tested to ensure the maximum benefit of the test, so that the efficiency of the whole test process is higher, in this embodiment, the demand degree is set between 0 and 1, and the demand degree L is set x Defined as 5 levels: among these, the absolutely important demand L x A value of 1, a more important demand L x The value of L is more than or equal to 0.7 x 1 ≦ a slightly important requirement L x The value is equal to or less than 0.4 and less than L x Less than or equal to 0.7, insignificant degree of demand L x The value is not less than 0.2 and not more than L x Less than or equal to 0.4, and no demand L x The value is 0.
And S106, constructing a software testing model according to the error correction degree, the reliability and the demand degree, and performing software testing on the software to be tested according to the software testing model and a priority regulation rule to obtain a final testing result.
It should be noted that, in this embodiment, the above-mentioned error correction degree, reliability degree, and requirement degree are added to the total evaluation index, so as to construct a software test model, and sequence the test cases in the test case file according to the requirement degree, error correction degree, and reliability degree values. Wherein,
Figure 854323DEST_PATH_IMAGE016
to maximize the error correction in the test case file,
Figure 933137DEST_PATH_IMAGE017
for the maximum value of the reliability in the test case file, alpha (alpha is more than or equal to 0 and less than or equal to 1) and beta (beta is more than or equal to 0 and less than or equal to 1) are the weighted values of the factors of the tester, and the software test model is as follows:
formula (3):
Figure 962273DEST_PATH_IMAGE018
in the formula,
Figure 468341DEST_PATH_IMAGE019
the larger the value of the alpha and the beta is, the higher the comprehensive value of the demand degree and the error correction degree is, the higher the priority of the corresponding test case file needs to be, the alpha and the beta are used as the emphasis of testers on the three factors, if the demand degree is considered to be more important, the alpha value is increased, and the proportion of the priority of the demand degree is increased; if the error correction degree is considered to be more important, the α value is adjusted to be smaller, and the reliability and the error correction degree are adjusted by adjusting β.
Further, in the determination process of the test case file, the coverage of many test case files to the requirements is the same or similar, for example: the test cases of regression testing are set
Figure 215717DEST_PATH_IMAGE020
And the demand set is
Figure 832643DEST_PATH_IMAGE021
If the similarity relation between each test case file is required to be expressed, the similarity relation can be establishedm*nAssociation matrix
Figure 732597DEST_PATH_IMAGE022
If in the test case
Figure 409566DEST_PATH_IMAGE023
And
Figure 847501DEST_PATH_IMAGE024
if there is a similarity relationship, then x rows and y columns of elements in the matrix
Figure 330435DEST_PATH_IMAGE025
A value of one, if not similar, the element value is zero:
formula (4):
Figure 68583DEST_PATH_IMAGE026
；
according to the matrix in the above formula (4), which is an incidence matrix of four test case files and four requirements, it can be seen from the matrix,
Figure 916454DEST_PATH_IMAGE027
and
Figure 638422DEST_PATH_IMAGE028
is similar to the prior art,
Figure 597151DEST_PATH_IMAGE027
And
Figure 471697DEST_PATH_IMAGE029
similarly, the information among the test case files is expressed by a matrix, so that the information can be used as the basis of a sequencing algorithm and can be repeatedly used in the regression test, and the calculation amount of the test is reduced.
In this embodiment, the test speed of the test case file is accelerated and the overall efficiency is improved by constructing a priority adjustment rule, wherein each test case file is evaluated according to the software test model in the above formula (3), and if the test case file is not executed for the first time, the evaluation is performed only according to the requirement priority in the test model. Secondly, a priority dynamic adjustment algorithm is used when the test case files are executed according to the sequence, if the test case files are correctly executed, the next test case in the sequence is executed, if an error condition occurs in the operation process, all similar test cases are solved through the incidence matrix, and the priority of all similar test cases is advanced to the previous level.
And finally, continuously executing the rest test cases until the execution is finished, and outputting a final test result.
In summary, in the software testing method in the above embodiment of the present invention, the test scenario model is correspondingly constructed by obtaining the test environment configuration data, the version data, and the software type, so that the software testing can be performed in the test scenario model, and when different software needs to be targeted, the test scenario model can be reconstructed according to the version data and the software type of different products, thereby avoiding the corresponding development of different test systems for different software, reducing the workload, and improving the working efficiency; specifically, the test case file is generated through the user-defined node and the test case base file, so that the software test process can be controlled according to the user-defined node of a worker, and the software test accuracy is improved; furthermore, the error checking capability of the regression test is improved through the error correction degree, the reliability degree and the demand degree of each test case file, and the efficiency of the regression test is further improved.
Example two
Referring to fig. 4, a software testing method according to a second embodiment of the present invention is shown, and the method includes steps S201 to S208:
s201, acquiring corresponding simulated environment data based on the software type of software to be tested, creating an environment editor according to the software type, and editing data of the environment editor by using a data editing mode to obtain a scene editor corresponding to the software to be tested;
s202, acquiring current environment data, and optimizing the scene editor according to the simulated environment data and the current environment data to obtain test environment configuration data corresponding to the software to be tested;
specifically, when a test request transmitted by the software to be tested through the data interface is obtained, the software information of the software to be tested is obtained from a registry of the test software through the data interface, and the software information includes version data and a software type of the software.
The version data can reflect the current version of the software, and the version data can avoid the difference of the software testing accuracy caused by different versions of the software to be tested; the software type can embody the specific role of the software, such as: search software, office software, etc.
In this embodiment, the simulated environment data corresponding to each software type can be stored in the database, and when a software type of a certain software to be tested is obtained, the simulated environment data corresponding to the software type can be obtained through the database.
Specifically, an environment editor is created according to a software type, where the environment editor includes a basic attribute of an environment configuration, and a corresponding editing function and a function, and the basic attribute can be converted into a corresponding basic function through the function, for example: building, opening, closing and other basic functions; adding functions required for constructing a test scene model by using a control dragging mode, and correspondingly converting the functions into element attributes required by the test scene model by using an editing function so as to obtain a scene editor of the software to be tested;
further, acquiring hardware information of the hardware device of the software test this time, simulating an operation amount of the software to be tested, and determining current environment data of the software test this time according to the operation amount and the hardware information of the hardware device, it can be understood that in other embodiments, the current environment data can also be set by a user according to the hardware information, for example: when part of hardware in the hardware information can meet the software test, a user can remove the unnecessary hardware from the current environment data so as to reduce the utilization rate of hardware equipment.
After determining the current environment data, optimizing the scene editor by using the current environment data and the simulated environment data, specifically, analyzing the current environment data and the simulated environment data and the element attribute in the scene editor respectively, and if the current environment data meets the element attribute requirement in the scene editor and the simulated environment data also meets the element attribute requirement in the scene editor, performing data combination on the current environment data and the simulated environment data, and taking the combined environment data as environment configuration data in the scene editor, namely test environment configuration data corresponding to software to be tested;
if the current environment data meets the element attribute requirement in the scene editor and the simulated environment data does not meet the element attribute requirement in the scene editor, performing data combination on the simulated environment data meeting the element attribute requirement in the scene editor and the current environment data in the simulated environment data, and taking the combined environment data as environment configuration data in the scene editor, namely test environment configuration data corresponding to software to be tested;
if the current environment data does not meet the element attribute requirement in the scene editor and the simulated environment data meets the element attribute requirement in the scene editor, taking the simulated environment data as environment configuration data in the scene editor, namely test environment configuration data corresponding to the software to be tested;
and if the current environment data does not meet the element attribute requirement in the scene editor and the simulated environment data does not meet the element attribute requirement in the scene editor, performing data combination on the current environment data and the simulated environment data which meet the element attribute requirement in the scene editor in the simulated environment data, and taking the combined environment data as the environment configuration data in the scene editor, namely the test environment configuration data corresponding to the software to be tested.
S203, correspondingly constructing a test scene model based on the version data and the software type of the software to be tested and the test environment configuration data;
in this embodiment, a modeling database is constructed in advance, modeling functions and modeling parameters required by each software type are prestored in the modeling database, when the software type is obtained, a modeling editor is created by using the corresponding modeling functions and modeling parameters, and a plurality of minimum modeling data base classes are obtained according to the version data of the software to be tested, wherein the minimum modeling data base class is a minimum graphical model element for data modeling.
Furthermore, each minimum graphical model element and the test environment configuration data are combined into attributes and behavior functions of the model elements, and a test scenario model is generated through the attributes and the behavior functions of the model elements.
S204, obtaining a test source code of the software to be tested according to the software type, and correspondingly generating a test case basic file in the test scene model based on the test source code;
in specific implementation, the test source code of the software to be tested is searched according to the software type, and by means of constructing a software type and test source code mapping table, when the software type is obtained, the test source code corresponding to the software type can be obtained by means of table lookup.
It should be noted that, in other embodiments, the test source code of the software to be tested can be found by pre-storing the test source code of the software to be tested in the registry of the software to be tested and acquiring the registry.
Further, a requirement specification of the software to be tested is obtained, wherein an execution model of the software to be tested can be constructed through the specification requirement specification, the execution model is composed of a plurality of atomic models, and the atomic models are the minimum units of a test process and comprise a test protocol, a test condition, a test path and result verification. And selecting a corresponding test path by using the test conditions of the test software, and generating a test case basic file by corresponding the test path and the test basic file in a test scene model.
S205, self-defining test nodes, and combining the test nodes and the test case basic files to obtain a plurality of test case files;
in specific implementation, a test scene model comprises a plurality of test node attributes, a user creates a test node according to the test node attributes in a self-defined manner, the test node comprises a node attribute identifier and node configuration data, wherein the node attribute identifier is a unique identifier of the test node attributes, and information of the corresponding test node attributes can be acquired through the identifier; the node attribute data comprises node attributes customized by a user according to requirements, such as: the user requirement is connectivity test, and the node attribute is connectivity test node attribute (attribute information such as a connectivity test interface is constructed).
And after the test nodes defined by the user are obtained, combining the test nodes with the test case basic file to further obtain the test case file.
S206, performing preliminary test on the software to be tested by using each test case file to obtain a corresponding preliminary test result;
it should be noted that, because the test case file does not have the execution capability, the test case file needs to be converted into an executable test execution file, the test case file is converted into a C language or programming language program file, and the test software to be tested is tested through the test execution file to obtain a corresponding test result.
S207, calculating the error correction degree and the reliability degree of each test case file based on the preliminary test result, and determining the demand degree of each test case file according to the actual test condition of each test case file;
it should be noted that, in the software testing process, when a tester finds that a test case causes an exception in the testing process, the exception part needs to be repaired, but in order to know whether the repaired code can solve the exception or cause another exception, the test case needs to be retested, and the testing process is a regression test. Generally, in the process of software development, the proportion of regression testing of software testing is large, and due to rapid iteration of software, the software also needs to be modified for multiple times, each modification means that the regression testing needs to be performed.
Specifically, the number of errors of each test case file in the preliminary test result is obtained, and the error correction degree of each test case file is calculated according to the following formula (1) based on the number of errors of each test case file:
formula (1):
Figure 224889DEST_PATH_IMAGE001
；
in the formula,
Figure 434154DEST_PATH_IMAGE002
for test case files
Figure 196573DEST_PATH_IMAGE003
To (1)
Figure 378156DEST_PATH_IMAGE004
The initial value of the error times in the secondary test is 0;
Figure 630146DEST_PATH_IMAGE005
for test case files
Figure 998810DEST_PATH_IMAGE003
To (1) a
Figure 361659DEST_PATH_IMAGE004
Error correction degree in the secondary test;
Figure 397748DEST_PATH_IMAGE013
for test case files
Figure 571371DEST_PATH_IMAGE003
To (1) a
Figure 427332DEST_PATH_IMAGE014
Error correction degree in secondary test;
as can be seen from the above formula (1), the error correction degree of each test is the superposition of the current error frequency and the previous error frequency, so that the error correction degree gradually increases with the progress of the test, and the fact that the error correction degree does not increase means that the code repair has already solved the abnormal problem, the execution sequence of the test case file does not need to be further improved, and the gradually increasing error correction degree means that the code repair has not solved the abnormal problem or still has a problem.
Further, the operation condition of each test case file in the preliminary test result is obtained, and the reliability of each test case file is calculated according to the following formula (2) based on the operation condition of each test case file:
formula (2):
Figure 593871DEST_PATH_IMAGE015
；
in the formula,
Figure 484466DEST_PATH_IMAGE009
for test cases
Figure 78259DEST_PATH_IMAGE003
To (1)
Figure 421516DEST_PATH_IMAGE004
The running condition in the secondary test is 1 when the running is abnormal, and 0 when the running is normal;
Figure 126166DEST_PATH_IMAGE010
for test case files
Figure 871268DEST_PATH_IMAGE003
To (1)
Figure 383765DEST_PATH_IMAGE004
Reliability in secondary test;
Figure 214318DEST_PATH_IMAGE011
for test case files
Figure 722659DEST_PATH_IMAGE003
To (1)
Figure 322268DEST_PATH_IMAGE014
Reliability at the time of secondary test.
It should be noted that, in this embodiment, the reliability is an execution condition of the test case file in the operation process, and when the test case file is operated, a test cannot be normally operated due to the test case file or cannot be operated due to the test case file after the code is repaired; and if the test case file which cannot be operated is not found, the reliability of the test case file is taken as 0.
As can be seen from the above formula (2), the reliability and the error correction are the same, and will gradually increase according to the number of times that the test case file cannot be run in the test process, and if the test case file is executed for multiple times, the reliability of the test case file continuously increases, which means that the test case file has an exception or the code repair is not a problem.
In this embodiment, the demand degree is the importance degree according to each demand in the system to divide the demand, and the key function used by the user is tested to ensure the maximum benefit of the test, so that the efficiency of the whole test process is higher, in this embodiment, the demand degree is set between 0 and 1, and the demand degree L is set x Defined as 5 levels: among these, the absolutely important demand L x Value of 1, the more important requirement L x The value is equal to or less than 0.7 and less than L x Less than or equal to 1, a slightly important degree of demand L x The value is equal to or less than 0.4 and less than L x Less than or equal to 0.7, insignificant degree of demand L x The value is not less than 0.2 and not more than L x Less than or equal to 0.4, and no demand L x The value is 0.
And S208, constructing a software testing model according to the error correction degree, the reliability and the demand degree, and performing software testing on the software to be tested according to the software testing model and a priority regulation rule to obtain a final testing result.
It should be noted that, in this embodiment, the above-mentioned error correction degree, reliability degree, and requirement degree are added to the total evaluation index, so as to construct a software test model, and sequence the test cases in the test case file according to the requirement degree, error correction degree, and reliability degree values. Wherein,
Figure 257863DEST_PATH_IMAGE030
to maximize the error correction in the test case file,
Figure 575712DEST_PATH_IMAGE031
for the maximum value of the reliability in the test case file, alpha (alpha is more than or equal to 0 and less than or equal to 1) and beta (beta is more than or equal to 0 and less than or equal to 1) are the weighted values of the factors of the tester, and the software test model is as follows:
formula (3):
Figure 91007DEST_PATH_IMAGE032
in the formula,
Figure 607439DEST_PATH_IMAGE019
the larger the value of the alpha value is, the higher the comprehensive value of the demand degree and the error correction degree is, the higher the priority of the corresponding test case file is required to be, the alpha and the beta are used as the emphasis of the tester on the three factors, if the demand degree is considered to be more important, the alpha value is increased, and the proportion of the priority of the demand degree is increased; if the error correction degree is considered to be more important, the α value is adjusted to be smaller, and the reliability and the error correction degree are adjusted by adjusting β.
Further, in the determination process of the test case file, coverage of many test case files to requirements is the same or similar, for example: the set of test cases for regression testing is
Figure 651618DEST_PATH_IMAGE020
And the demand set is
Figure 269812DEST_PATH_IMAGE033
If the similarity relation between each test case file is required to be expressed, the similarity relation can be establishedm*nAssociation matrix
Figure 57640DEST_PATH_IMAGE034
If in the test case
Figure 694158DEST_PATH_IMAGE023
And
Figure 705976DEST_PATH_IMAGE024
if there is a similarity relation, then x rows and y columns of elements in the matrix
Figure 263996DEST_PATH_IMAGE025
A value of one, if not similar, the element value is zero:
formula (4)：
Figure 589935DEST_PATH_IMAGE035
；
According to the matrix in the above formula (4), which is an incidence matrix of four test case files and four requirements, it can be seen from the matrix,
Figure 80959DEST_PATH_IMAGE027
and
Figure 732521DEST_PATH_IMAGE028
is similar to the prior art,
Figure 59728DEST_PATH_IMAGE027
And
Figure 189358DEST_PATH_IMAGE029
similarly, the information among the test case files is expressed by a matrix, so that the matrix can be used as the basis of a sorting algorithm and can be repeatedly used in the regression test, and the calculation amount of the test is reduced.
In this embodiment, the test speed of the test case file is accelerated and the overall efficiency is improved by constructing a priority adjustment rule, wherein each test case file is evaluated according to the software test model in the above formula (3), and if the test case file is not executed for the first time, the evaluation is performed only according to the requirement priority in the test model. Secondly, a priority dynamic adjustment algorithm is used when the test case files are executed according to the sequence, if the test case files are correctly executed, the next test case in the sequence is executed, and if an error condition occurs in the operation process, all similar test cases are solved through the incidence matrix, and the priority of all similar test cases is advanced by one level.
And finally, continuously executing the rest test cases until the execution is finished, and outputting a final test result.
Compared with the software testing method in the first embodiment, the software testing method in the embodiment optimizes the scene editor by using the simulated environment data and the current environment data, so that the testing environment configuration data of the software to be tested is more accurately obtained, and the software testing accuracy is further ensured.
EXAMPLE III
Referring to fig. 5, a software testing system according to a third embodiment of the present invention is further provided, where the software testing system includes:
the test scene constructing module 11 is used for correspondingly constructing a test scene model based on version data and software types of the software to be tested and test environment configuration data;
further, the test scenario constructing module 11 includes:
the modeling editing unit is used for correspondingly creating a modeling editor according to the software type and acquiring a plurality of minimum modeling data base classes of the software to be tested according to the version data;
and the scene construction unit is used for combining each modeling data base class with the testing environment configuration data and inputting the combined data into the modeling editor to generate the testing scene model.
The test code processing module 12 is configured to obtain a test source code of the software to be tested according to the software type, and generate a test case base file in the test scene model based on the test source code;
further, the test code processing module 12 includes:
the requirement specification acquisition unit is used for calling a requirement specification of the software to be tested and correspondingly generating a test basic file according to the test source code;
and the test case processing unit is used for selecting a test path according to the requirement specification and correspondingly generating a test case basic file in the test scene model through the test path and the test basic file.
The test case generation module 13 is used for customizing a test node and combining the test node and the test case basic file to obtain a plurality of test case files;
the preliminary test module 14 is configured to perform a preliminary test on the software to be tested by using each test case file to obtain a corresponding preliminary test result;
the model data calculation module 15 is configured to calculate an error correction degree and a reliability degree of each test case file based on the preliminary test result, and determine a demand degree of each test case file according to an actual test condition of each test case file;
and the test model building module 16 is configured to build a software test model according to the error correction degree, the reliability degree and the demand degree, and perform software test on the software to be tested according to the software test model and a priority adjustment rule to obtain a final test result.
In some optional embodiments, the system further comprises:
the scene editing module is used for acquiring corresponding simulated environment data based on the software type of the software to be tested, creating an environment editor according to the software type, and editing data of the environment editor by using a data editing mode to obtain the scene editor corresponding to the software to be tested;
and the test environment configuration module is used for acquiring current environment data and optimizing the scene editor according to the simulated environment data and the current environment data so as to obtain test environment configuration data corresponding to the software to be tested.
The functions or operation steps implemented by the modules and units when executed are substantially the same as those of the method embodiments, and are not described herein again.
The software testing system provided by the embodiment of the invention has the same implementation principle and technical effect as the method embodiment, and for the sake of brief description, no part of the system embodiment is mentioned, and reference may be made to the corresponding contents in the method embodiment.
Example four
Referring to fig. 6, a computer device according to a fourth embodiment of the present invention is shown, which includes a memory 10, a processor 20, and a computer program 30 stored in the memory 10 and executable on the processor 20, and when the processor 20 executes the computer program 30, the software testing method is implemented.
The memory 10 includes at least one type of storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, and the like. The memory 10 may in some embodiments be an internal storage unit of the computer device, for example a hard disk of the computer device. The memory 10 may also be an external storage device in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like. Further, the memory 10 may also include both an internal storage unit and an external storage device of the computer apparatus. The memory 10 may be used not only to store application software installed in the computer device and various kinds of data, but also to temporarily store data that has been output or will be output.
In some embodiments, the processor 20 may be an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a controller, a microcontroller, a microprocessor or other data Processing chip, and is configured to run program codes stored in the memory 10 or process data, such as executing an access restriction program.
It should be noted that the configuration shown in fig. 6 does not constitute a limitation of the computer device, and in other embodiments the computer device may include fewer or more components than shown, or some components may be combined, or a different arrangement of components.
Embodiments of the present invention further provide a readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the software testing method as described above.
Those of skill in the art will understand that the logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be viewed as implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Further, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following technologies, which are well known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
All possible combinations of the technical features of the above embodiments may not be described for the sake of brevity, but should be considered as within the scope of the present disclosure as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (9)

1. A software testing method, comprising:
correspondingly constructing a test scene model based on version data and software types of the software to be tested and test environment configuration data;
acquiring a test source code of the software to be tested according to the software type, and correspondingly generating a test case basic file in the test scene model based on the test source code;
customizing a test node, and combining the test node and the test case basic file to obtain a plurality of test case files;
performing preliminary test on the software to be tested by using each test case file to obtain a corresponding preliminary test result;
calculating the error correction degree and the reliability degree of each test case file based on the preliminary test result, and determining the demand degree of each test case file according to the actual test condition of each test case file, wherein the demand degree is obtained by dividing the demand of each test case file according to the importance degree of each demand in the system, and the demand degree L x Set between 0 and 1 and set the demand L x Defined as 5 levels: absolutely important demand L x Value of 1, the more important requirement L x The value of L is more than or equal to 0.7 x 1 ≦ a slightly important requirement L x The value of L is not less than 0.4 x Less than or equal to 0.7, insignificant degree of demand L x The value of L is more than or equal to 0.2 x Less than or equal to 0.4, and no demand L x The value is 0;
the step of calculating the error correction degree and the reliability degree of each test case file based on the preliminary test result comprises the following steps:
acquiring the error times of each test case file in the preliminary test result, and calculating the error correction degree of each test case file according to the following formula based on the error times of each test case file:
Figure 812314DEST_PATH_IMAGE001
；
in the formula,
Figure 4261DEST_PATH_IMAGE002
for test case files
Figure 287475DEST_PATH_IMAGE003
To (1) a
Figure 172254DEST_PATH_IMAGE004
The error times in the secondary test is 0 in an initial value;
Figure 173708DEST_PATH_IMAGE005
for test case files
Figure 903767DEST_PATH_IMAGE003
To (1) a
Figure 307067DEST_PATH_IMAGE004
Error correction degree in the secondary test;
Figure 113480DEST_PATH_IMAGE006
for test case files
Figure 336651DEST_PATH_IMAGE003
To (1)
Figure 135979DEST_PATH_IMAGE007
Error correction degree in the secondary test;
obtaining the operation condition of each test case file in the preliminary test result, and calculating the reliability of each test case file according to the following formula based on the operation condition of each test case file:
Figure 393785DEST_PATH_IMAGE008
；
in the formula,
Figure 354788DEST_PATH_IMAGE009
for test cases
Figure 330834DEST_PATH_IMAGE003
To (1)
Figure 668275DEST_PATH_IMAGE004
The running condition in the secondary test is 1 when the running is abnormal and 0 when the running is normal;
Figure 780587DEST_PATH_IMAGE010
for test case files
Figure 928803DEST_PATH_IMAGE003
To (1)
Figure 126566DEST_PATH_IMAGE004
Reliability in secondary test;
Figure 267698DEST_PATH_IMAGE011
for test case files
Figure 500096DEST_PATH_IMAGE003
To (1)
Figure 802901DEST_PATH_IMAGE007
Reliability in secondary test; and constructing a software testing model according to the error correction degree, the reliability and the demand degree, and performing software testing on the software to be tested according to the software testing model and a priority regulation rule to obtain a final testing result.
2. The software testing method of claim 1, wherein before the step of building the test scenario model based on the version data and the software type of the software to be tested and the test environment configuration data, the method further comprises:
acquiring corresponding simulated environment data based on the software type of software to be tested, creating an environment editor according to the software type, and editing data of the environment editor in a data editing mode to obtain a scene editor corresponding to the software to be tested;
and acquiring current environment data, and optimizing the scene editor according to the simulated environment data and the current environment data to obtain test environment configuration data corresponding to the software to be tested.
3. The software testing method of claim 1, wherein the step of correspondingly constructing the test scenario model based on the version data and the software type of the software to be tested and the testing environment configuration data comprises:
correspondingly creating a modeling editor according to the software type, and acquiring a plurality of minimum modeling data base classes of the software to be tested according to the version data;
and combining each modeling data base class with the testing environment configuration data, and inputting the combined data into the modeling editor to generate the testing scene model.
4. The software testing method according to claim 1, wherein the step of correspondingly generating a test case base file in the test scenario model based on the test source code comprises:
calling the requirement specification of the software to be tested, and correspondingly generating a test basic file according to the test source code;
and selecting a test path according to the requirement specification, and correspondingly generating a test case basic file in the test scene model through the test path and the test basic file.
5. A software testing system, comprising:
the test scene construction module is used for correspondingly constructing a test scene model based on the version data and the software type of the software to be tested and the test environment configuration data;
the test code processing module is used for acquiring a test source code of the software to be tested according to the software type and correspondingly generating a test case basic file in the test scene model based on the test source code;
the test case generation module is used for customizing test nodes and combining the test nodes and the test case basic files to obtain a plurality of test case files;
the preliminary test module is used for carrying out preliminary test on the software to be tested by utilizing each test case file so as to obtain a corresponding preliminary test result;
a model data calculation module for calculating the error correction degree and the reliability of each test case file based on the preliminary test result, and determining the demand degree of each test case file according to the actual test condition of each test case file, wherein the demand degree is the demand division of each test case file according to the importance degree of each demand in the system, and the demand degree L is x Set between 0 and 1 and set the demand L x Defined as 5 levels: absolutely important demand L x Value of 1, the more important requirement L x The value of L is more than or equal to 0.7 x Less than or equal to 1, a slightly important degree of demand L x The value of L is not less than 0.4 x Less than or equal to 0.7, insignificant degree of demand L x The value of L is more than or equal to 0.2 x Less than or equal to 0.4, and no demand L x The value is 0;
wherein the model data calculation module is specifically configured to:
acquiring the error frequency of each test case file in the preliminary test result, and calculating the error correction degree of each test case file according to the following formula based on the error frequency of each test case file:
Figure 753540DEST_PATH_IMAGE001
；
in the formula,
Figure 432783DEST_PATH_IMAGE002
for test case files
Figure 519687DEST_PATH_IMAGE003
To (1)
Figure 196656DEST_PATH_IMAGE004
The initial value of the error times in the secondary test is 0;
Figure 913552DEST_PATH_IMAGE005
for test case files
Figure 396486DEST_PATH_IMAGE003
To (1) a
Figure 337897DEST_PATH_IMAGE004
Error correction degree in the secondary test;
Figure 248084DEST_PATH_IMAGE006
for test case files
Figure 907736DEST_PATH_IMAGE003
To (1) a
Figure 132044DEST_PATH_IMAGE007
Error correction degree in the secondary test;
obtaining the operation condition of each test case file in the preliminary test result, and calculating the reliability of each test case file according to the following formula based on the operation condition of each test case file:
Figure 255858DEST_PATH_IMAGE008
；
in the formula,
Figure 274629DEST_PATH_IMAGE009
for test cases
Figure 969047DEST_PATH_IMAGE003
To (1) a
Figure 731467DEST_PATH_IMAGE004
The running condition in the secondary test is 1 when the running is abnormal, and 0 when the running is normal;
Figure 709787DEST_PATH_IMAGE010
for test case files
Figure 696197DEST_PATH_IMAGE003
To (1)
Figure 596020DEST_PATH_IMAGE004
Reliability in secondary test;
Figure 896552DEST_PATH_IMAGE011
for test case files
Figure 729378DEST_PATH_IMAGE003
To (1) a
Figure 89953DEST_PATH_IMAGE007
Reliability in secondary test;
and the test model building module is used for building a software test model according to the error correction degree, the reliability and the demand degree, and performing software test on the software to be tested according to the software test model and a priority regulation rule to obtain a final test result.
6. The software testing system of claim 5, wherein the system further comprises:
the scene editing module is used for acquiring corresponding simulated environment data based on the software type of the software to be tested, creating an environment editor according to the software type, and editing data of the environment editor by using a data editing mode to obtain the scene editor corresponding to the software to be tested;
and the test environment configuration module is used for acquiring current environment data and optimizing the scene editor according to the simulated environment data and the current environment data so as to obtain test environment configuration data corresponding to the software to be tested.
7. The software testing system of claim 5, wherein the test scenario construction module comprises:
the modeling editing unit is used for correspondingly creating a modeling editor according to the software type and acquiring a plurality of minimum modeling data base classes of the software to be tested according to the version data;
and the scene construction unit is used for combining each modeling data base class with the testing environment configuration data and inputting the combined data into the modeling editor to generate the testing scene model.
8. A readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the software testing method according to any one of claims 1 to 4.
9. 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 software testing method according to any one of claims 1 to 4 when executing the computer program.
CN202211170103.3A 2022-09-26 2022-09-26 Software testing method, system, readable storage medium and computer equipment Active CN115248783B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211170103.3A CN115248783B (en) 2022-09-26 2022-09-26 Software testing method, system, readable storage medium and computer equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211170103.3A CN115248783B (en) 2022-09-26 2022-09-26 Software testing method, system, readable storage medium and computer equipment

Publications (2)

Publication Number Publication Date
CN115248783A CN115248783A (en) 2022-10-28
CN115248783B true CN115248783B (en) 2022-12-23

Family

ID=83699844

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211170103.3A Active CN115248783B (en) 2022-09-26 2022-09-26 Software testing method, system, readable storage medium and computer equipment

Country Status (1)

Country Link
CN (1) CN115248783B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115840711B (en) * 2022-12-29 2023-05-09 江西萤火虫微电子科技有限公司 Software testing method, system, storage medium and computer for graphic user interface

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7137087B1 (en) * 2003-08-20 2006-11-14 Adaptec, Inc. Integrated circuit verification scheme
CN114817015A (en) * 2022-04-14 2022-07-29 芯天下技术股份有限公司 Test case coverage rate statistical method and device, electronic equipment and storage medium

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6601018B1 (en) * 1999-02-04 2003-07-29 International Business Machines Corporation Automatic test framework system and method in software component testing
ATE545224T1 (en) * 2005-06-28 2012-02-15 Tttech Computertechnik Ag SECURELY STARTING UP A NETWORK
WO2008039964A1 (en) * 2006-09-28 2008-04-03 Nec Laboratories America, Inc. Software testing using machine learning
CN102915271A (en) * 2012-10-31 2013-02-06 北京邮电大学 Method for optimizing unit regression test case set based on control flow diagram
CN108153658A (en) * 2016-12-02 2018-06-12 富士通株式会社 The method and apparatus of models of priority training method and determining priorities of test cases
CN109062782B (en) * 2018-06-27 2022-05-31 创新先进技术有限公司 Regression test case selection method, device and equipment
CA3098934C (en) * 2019-11-06 2021-07-06 Alipay (Hangzhou) Information Technology Co., Ltd. Consenus of shared blockchain data storage based on error correction code
US11068387B1 (en) * 2020-04-20 2021-07-20 Webomates Inc. Classifying a test case executed on a software
CN111427802B (en) * 2020-06-09 2021-06-22 南京大学 Test method and system for carrying out test case priority sequencing by utilizing ensemble learning
CN111858371A (en) * 2020-07-28 2020-10-30 北京达佳互联信息技术有限公司 Software testing method, system, storage medium and computer equipment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7137087B1 (en) * 2003-08-20 2006-11-14 Adaptec, Inc. Integrated circuit verification scheme
CN114817015A (en) * 2022-04-14 2022-07-29 芯天下技术股份有限公司 Test case coverage rate statistical method and device, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN115248783A (en) 2022-10-28

Similar Documents

Publication Publication Date Title
US5500941A (en) Optimum functional test method to determine the quality of a software system embedded in a large electronic system
US8745588B2 (en) Method for testing operation of software
CN109063829B (en) Neural network construction method and device, computer equipment and storage medium
US7793271B2 (en) Bi-directional product development process simulation
US11409928B2 (en) Configurable digital twin
CN115248783B (en) Software testing method, system, readable storage medium and computer equipment
KR101334806B1 (en) Method of proudcing input sets of test case in test case generating system
CN103970654B (en) Software reliability virtual test method
CN111309734A (en) Method and system for automatically generating table data
CN111651358B (en) Method for generating test case, software test method, device and server
US10324829B2 (en) Application testing
CN114143235A (en) NFV automatic test method, device, equipment and storage medium
CN105787214A (en) Method and device for model verification
CN115827353A (en) Fault diagnosis method and device
CN112948480B (en) Data extraction method, device, electronic equipment and storage medium
CN112988565B (en) Interface automatic test method, device, computer equipment and storage medium
CN114610648A (en) Test method, device and equipment
CN113973068A (en) Chaos test method and device, chaos test platform and storage medium
JP2022124240A (en) Diagnostic pattern generation method and computer
CN112328281A (en) Server firmware refreshing method and device
CN118132448B (en) Test case processing method, device, computer equipment and storage medium
US7650579B2 (en) Model correspondence method and device
CN116383068B (en) Quick test method, device and storage medium of C++ program interface
CN113448865B (en) Relational test data generation method and device based on formal model
CN114692382B (en) Management method and device for nuclear power simulation model development data and computer equipment

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
TR01 Transfer of patent right

Effective date of registration: 20230410

Address after: Room 3602, Zifeng Building, No. 3333 Ziyang Avenue, Nanchang High tech Industrial Development Zone, Nanchang City, Jiangxi Province, 330224

Patentee after: Nanchang Senmu Technology Co.,Ltd.

Address before: 5th Floor, Building 3, Science and Technology Innovation Center, No. 269 Aixihu North Road, Nanchang High tech Industrial Development Zone, Nanchang City, Jiangxi Province, 330096

Patentee before: Jiangxi Firefly Microelectronics Technology Co.,Ltd.

TR01 Transfer of patent right