CN110674047A - Software testing method and device and electronic equipment - Google Patents
Software testing method and device and electronic equipment Download PDFInfo
- Publication number
- CN110674047A CN110674047A CN201910917827.1A CN201910917827A CN110674047A CN 110674047 A CN110674047 A CN 110674047A CN 201910917827 A CN201910917827 A CN 201910917827A CN 110674047 A CN110674047 A CN 110674047A
- Authority
- CN
- China
- Prior art keywords
- test
- rule
- module
- software
- target
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
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 embodiment of the disclosure provides a software testing method, a software testing device and electronic equipment, belonging to the technical field of data processing, wherein the method comprises the following steps: setting one or more software test rules through a test rule module, wherein the one or more test rules in the test rule module are sent to a test engine through a first communication interface; selecting a target test rule from the one or more test rules based on configuration parameters for the target software object sent by the configuration center module to the test engine through the second communication interface; aiming at the target test rule, acquiring a measurement parameter quantifying the target test rule from a test measurement module, and sending the measurement parameter to a test engine through a third communication interface; and displaying the test state and the test result of the target software object in a tracking tool module by using a fourth communication interface connected with the test engine. By the scheme, the quality of the software can be tested flexibly and efficiently.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a software testing method and apparatus, and an electronic device.
Background
Software Testing (Software Testing) describes a process used to facilitate the identification of the correctness, integrity, security, and quality of Software. In other words, software testing is a process of auditing or comparing between actual output and expected output. The definition of the software test is: the process of operating a program under specified conditions to discover program errors, to measure software quality, and to evaluate whether it meets design requirements.
Software testing is generated in connection with the generation of software. The software scale in the early software development process is very small and low in complexity, the software development process is disordered and quite random, the test meaning is narrow, a developer is equal to 'debugging' in testing, the purpose is to correct known faults in the software, and the developer usually completes the part of work. The testing is done with little investment and late testing intervention, often until the code is formed and the product is substantially complete. By the beginning of the 80 s of the last century, software and IT industries are greatly developed, software tends to be large-sized and high in complexity, and the quality of the software is more and more important. At this time, some basic theories and practical technologies of software testing are formed, and people begin to design various processes and management methods for software development, and the software development mode gradually transits from a chaotic and disordered development process to a structured development process, and is characterized by structured analysis and design, structured review, structured programming and structured testing. People also integrate the concept of "quality" into which software test definitions are changed, testing is not simply a process of finding errors, and testing is taken as a main role of Software Quality Assurance (SQA), including the content of software quality evaluation.
Disclosure of Invention
In view of this, embodiments of the present disclosure provide a software testing method, an apparatus, and an electronic device, which at least partially solve the problems in the prior art.
In a first aspect, an embodiment of the present disclosure provides a software testing method, including:
setting one or more software test rules through a test rule module, wherein the one or more test rules in the test rule module are sent to a test engine through a first communication interface;
selecting a target test rule from the one or more test rules based on configuration parameters for the target software object sent by the configuration center module to the test engine through the second communication interface;
aiming at the target test rule, acquiring a measurement parameter quantifying the target test rule from a test measurement module, and sending the measurement parameter to a test engine through a third communication interface;
and displaying the test state and the test result of the target software object in a tracking tool module by using a fourth communication interface connected with the test engine.
According to a specific implementation manner of the embodiment of the present disclosure, after the one or more software test rules are set by the test rule module, the method further includes:
acquiring one or more test rules existing in the test engine through a rule group management module;
setting an expected value for one or more acquired test rules existing in the test engine.
According to a specific implementation manner of the embodiment of the present disclosure, the setting of one or more software test rules by the test rule module includes:
a scalar or a plurality of test scalars, the type, the priority and the weight of the test rule are set for each software test rule.
According to a specific implementation manner of the embodiment of the present disclosure, the setting of one or more software test rules by the test rule module includes:
and constructing a rule group consisting of a plurality of test rules aiming at the encoding stage, the construction stage and the release stage of the target test software to form an association rule set.
According to a specific implementation manner of the embodiment of the present disclosure, before selecting a target test rule from the one or more test rules based on the configuration parameters for the target software object sent by the configuration center module to the test engine through the second communication interface, the method further includes:
binding a rule set and a project extension attribute for the target test software in the configuration center module;
and generating configuration parameters aiming at the target software object based on the rule group bound for the target test software and the project extension attribute.
According to a specific implementation manner of the embodiment of the present disclosure, the obtaining, from a test metric module, a metric parameter that quantifies the target test rule for the target test rule includes:
obtaining, in the test metrics module, a test rule describing a type, a classification, and a usage scalar of a test metric.
According to a specific implementation manner of the embodiment of the present disclosure, before displaying the test state and the test result of the target software object in the trace tool module by using the fourth communication interface connected to the test engine, the method further includes:
compiling the target test rule of the target test software into a test workflow by using a rule compiler, wherein the test workflow has a globally unique number;
executing the test workflow with the test engine.
According to a specific implementation manner of the embodiment of the present disclosure, the executing the test workflow by using the test engine includes:
and performing parameter verification and test rule verification on the test workflow by using a rule verifier, wherein the parameter verification verifies the condition that a selection rule is not configured so as to further determine whether a default value is used, the test rule verification verifies one rule, and information of a workflow source is measured according to the global unique number of the test workflow.
According to a specific implementation manner of the embodiment of the present disclosure, the executing the test workflow by using the test engine includes:
and carrying out flow control on the compiling result of the rule compiler by using a testing state preset by a testing engine, wherein the testing state comprises one or more of ready, execution, pause, end, rule matching, rule mismatching, abnormal interruption and manual interruption.
According to a specific implementation manner of the embodiment of the present disclosure, the displaying the test state and the test result of the target software object in a tracing tool module by using a fourth communication interface connected to the test engine includes:
generating a test report based on the results of the test engine, the test report including one or more of a workflow number, an expected result, an actual metric result, a configuration center number, and a rule set number.
In a second aspect, an embodiment of the present disclosure provides a software testing apparatus, including:
the device comprises a setting module, a test engine and a test rule module, wherein the setting module is used for setting one or more software test rules through the test rule module, and the one or more test rules in the test rule module are sent to the test engine through a first communication interface;
the selection module is used for selecting a target test rule from the one or more test rules based on the configuration parameters aiming at the target software object, which are sent to the test engine by the configuration center module through the second communication interface;
the acquisition module is used for acquiring a measurement parameter quantifying the target test rule from the test measurement module aiming at the target test rule, and the measurement parameter is sent to a test engine through a third communication interface;
and the execution module is used for displaying the test state and the test result of the target software object in the tracking tool module by utilizing a fourth communication interface connected with the test engine. .
In a third aspect, an embodiment of the present disclosure further provides an electronic device, where the electronic device includes:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the software testing method of any one of the first aspects or any implementation manner of the first aspect.
In a fourth aspect, the disclosed embodiments also provide a non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the software testing method in the first aspect or any implementation manner of the first aspect.
In a fifth aspect, the disclosed embodiments also provide a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions that, when executed by a computer, cause the computer to perform the software testing method of the first aspect or any implementation manner of the first aspect.
The software testing scheme in the embodiment of the disclosure comprises the steps of setting one or more software testing rules through a testing rule module, wherein the one or more testing rules in the testing rule module are sent to a testing engine through a first communication interface; selecting a target test rule from the one or more test rules based on configuration parameters for the target software object sent by the configuration center module to the test engine through the second communication interface; aiming at the target test rule, acquiring a measurement parameter quantifying the target test rule from a test measurement module, and sending the measurement parameter to a test engine through a third communication interface; and displaying the test state and the test result of the target software object in a tracking tool module by using a fourth communication interface connected with the test engine. By the scheme, the quality of the target test software can be flexibly and efficiently tested and evaluated.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings needed to be used in the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of a software testing process provided in an embodiment of the present disclosure;
fig. 2 is a schematic diagram of a software testing structure provided in the embodiment of the present disclosure;
FIG. 3 is a schematic diagram of another software testing structure provided in the embodiments of the present disclosure;
FIG. 4 is a schematic diagram of another software testing process provided by the embodiments of the present disclosure;
fig. 5 is a schematic structural diagram of a software testing apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic diagram of an electronic device provided in an embodiment of the present disclosure.
Detailed Description
The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.
The embodiments of the present disclosure are described below with specific examples, and other advantages and effects of the present disclosure will be readily apparent to those skilled in the art from the disclosure in the specification. It is to be understood that the described embodiments are merely illustrative of some, and not restrictive, of the embodiments of the disclosure. The disclosure may be embodied or carried out in various other specific embodiments, and various modifications and changes may be made in the details within the description without departing from the spirit of the disclosure. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It is noted that various aspects of the embodiments are described below within the scope of the appended claims. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the disclosure, one skilled in the art should appreciate that one aspect described herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. Additionally, such an apparatus may be implemented and/or such a method may be practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.
It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present disclosure, and the drawings only show the components related to the present disclosure rather than the number, shape and size of the components in actual implementation, and the type, amount and ratio of the components in actual implementation may be changed arbitrarily, and the layout of the components may be more complicated.
In addition, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects may be practiced without these specific details.
The embodiment of the disclosure provides a software testing method. The software testing method provided by the embodiment can be executed by a computing device, the computing device can be implemented as software, or implemented as a combination of software and hardware, and the computing device can be integrated in a server, a terminal device and the like.
Referring to fig. 1 and fig. 2, a software testing method provided in the embodiment of the present disclosure includes the following steps:
s101, one or more software test rules are set through a test rule module, and the one or more test rules in the test rule module are sent to a test engine through a first communication interface.
One purpose of testing software is to evaluate the quality of the software, which may be throughout all stages of software development, including but not limited to the source code stage, the build stage, the release stage, etc.
In order to effectively test the software, different test rules can be set based on different indexes. As a case may be, the specific rule may be set by setting a quality scalar. For example, a quality scalar may be defined as: the window period (formed by the combination of the week and the time range) is 14-18 tuesday, and the corresponding software testing rule can be: the number of times of release in the window period cannot be more than 2, namely, the same item and product at 14-18 points on Tuesday can be effectively released only once.
In order to effectively quantize the test rules, each test rule may correspond to a scalar or multiple scalars, and the type, priority, weight, and the like of the test rule may also be set.
The setting of the test rule may be done in the test rule module. The test rule module is an independently arranged module, and sends one or more test rules to the test engine through the first communication interface. The test rule module may be implemented in software or hardware.
When a plurality of rules exist, a rule group can be set, the rule group is composed of a plurality of test rules, and the rule group can represent a class of association rule sets, such as an encoding stage rule group, a construction stage rule group and a release stage rule group. Or may be an independent rule set, such as a single quality measurement rule set.
S102, selecting a target test rule from the one or more test rules based on the configuration parameters aiming at the target software object, which are sent to the test engine by the configuration center module through the second communication interface.
The target software object is software to be tested, and different target software objects have different testing strategies and testing rules, so that different testing rules need to be set for different target software objects.
The configuration center module can configure different test rules for different target software objects by setting different parameters. For example, an encoding stage rule set may be set for the target software object in the encoding stage, and at this time, the configuration center module may extract the feature parameters of the encoding stage rule set and send the feature parameters to the test engine through the second communication interface. Thereby selecting a target test rule from the one or more test rules based on the characteristic parameters.
The configuration center module can set a configuration center for the target software object or the item of the target software object, and bind the rule set and the item extension property of the target software or the target software object to be tested based on the configuration center, wherein the item extension property can be, for example, a collected data source and the like.
S103, aiming at the target test rule, obtaining a measurement parameter quantifying the target test rule from a test measurement module, and sending the measurement parameter to a test engine through a third communication interface.
For flexible target test rule configuration, metric parameters may be configured for the target test rule. The metrology parameters may be generated by the test metrology module and then transmitted to the test engine via the third communication interface.
The metric parameters may be described by means of scalar descriptors, which may detail the quality scalar, the type of scalar (time, percentage, etc.), the classification (source code phase, build phase, publish phase, etc.), the quality rules using the scalar, etc.
And S104, displaying the test state and the test result of the target software object in a tracking tool module by using a fourth communication interface connected with the test engine.
Once the target test rule and the measurement parameter corresponding to the target test rule are set, the target test rule can be compiled by using a rule compiler to form an executable code. As an example, referring to fig. 3, a plurality of rules are set in the rule pool, and these rules form a rule group by combination, and after the rules in the rule group are encoded, constructed and released, relevant configuration parameters and values can be automatically formed at the configuration center, and these parameters or values can also be modified by the configuration center.
Once released, the rule set is run in a workflow manner, and during the running of the workflow, a plurality of rule validators can be arranged in the workflow for checking the rules in the workflow. And finally, displaying the result of the workflow rule check in a report form. The results presented may be: "rule 1 correct", "rule 2 false", etc.
Referring to fig. 4, in the process of operating the workflow, multiple message passing is required between the workflow and the workflow manager, and by this scheme, a static rule set and a configuration center can be compiled into the workflow, and the workflow includes an executor, an execution parameter, an execution rule, and the like. So that the test engine can execute the test engine, and the test engine does not depend on any static resource in the execution process. A globally unique number (flowid) is generated and saved.
In the process of executing the engine, a rule verifier can be further arranged, the rule verifier can comprise two parts of parameter verification and quality rule verification, and the parameter verification verifies the condition that the rule is not configured but selected for judging whether a default value is used or not. The quality rule verification is specifically a verification process for a rule, and measurement is carried out according to information of a flowid acquisition source.
And the test engine is used for performing flow control on the compiling result of the rule compiler and can set different states, for example, the states can comprise ready, execution, pause, end, rule matching, rule mismatching, abnormal interruption, manual interruption and the like.
After the test engine execution is completed, the quality engine results may be reported and the generated reports may be presented by the trace tool module. The report may include flowid, expected outcome (threshold for rule passing), actual metric outcome, configuration center number, rule group number, etc.
By the scheme in the embodiment, the software quality can be flexibly abstracted into a scalar, the scalar is described, a quality engine is constructed for measurement, and a process of fragmenting quality data reduction measurement is formed through rule verification. The quality rule has high reuse rate and can form a passing standard. The threshold of the measurement is only required to be finely adjusted according to the conditions of the products and the projects, and the test engine and the rule verifier are not required to be modified, so that the products and the projects can be quickly enabled.
According to a specific implementation manner of the embodiment of the present disclosure, after the one or more software test rules are set by the test rule module, the method further includes: acquiring one or more test rules existing in the test engine through a rule group management module; setting an expected value for one or more acquired test rules existing in the test engine.
According to a specific implementation manner of the embodiment of the present disclosure, the setting of one or more software test rules by the test rule module includes: a scalar or a plurality of test scalars, the type, the priority and the weight of the test rule are set for each software test rule.
According to a specific implementation manner of the embodiment of the present disclosure, the setting of one or more software test rules by the test rule module includes: and constructing a rule group consisting of a plurality of test rules aiming at the encoding stage, the construction stage and the release stage of the target test software to form an association rule set.
According to a specific implementation manner of the embodiment of the present disclosure, before selecting a target test rule from the one or more test rules based on the configuration parameters for the target software object sent by the configuration center module to the test engine through the second communication interface, the method further includes: binding a rule set and a project extension attribute for the target test software in the configuration center module; and generating configuration parameters aiming at the target software object based on the rule group bound for the target test software and the project extension attribute.
According to a specific implementation manner of the embodiment of the present disclosure, the obtaining, from a test metric module, a metric parameter that quantifies the target test rule for the target test rule includes: obtaining, in the test metrics module, a test rule describing a type, a classification, and a usage scalar of a test metric.
According to a specific implementation manner of the embodiment of the present disclosure, before displaying the test state and the test result of the target software object in the trace tool module by using the fourth communication interface connected to the test engine, the method further includes: compiling the target test rule of the target test software into a test workflow by using a rule compiler, wherein the test workflow has a globally unique number; executing the test workflow with the test engine.
According to a specific implementation manner of the embodiment of the present disclosure, the executing the test workflow by using the test engine includes: and performing parameter verification and test rule verification on the test workflow by using a rule verifier, wherein the parameter verification verifies the conditions that the rule is not configured but selected so as to further determine whether a default value is used, the test rule verification verifies one rule, and information of a workflow source is measured according to the global unique number of the test workflow.
According to a specific implementation manner of the embodiment of the present disclosure, the executing the test workflow by using the test engine includes: and carrying out flow control on the compiling result of the rule compiler by using a testing state preset by a testing engine, wherein the testing state comprises one or more of ready, execution, pause, end, rule matching, rule mismatching, abnormal interruption and manual interruption.
According to a specific implementation manner of the embodiment of the present disclosure, the displaying the test state and the test result of the target software object in a tracing tool module by using a fourth communication interface connected to the test engine includes: generating a test report based on the results of the test engine, the test report including one or more of a workflow number, an expected result, an actual metric result, a configuration center number, and a rule set number.
Corresponding to the above method embodiment, referring to fig. 5, the embodiment of the present disclosure further provides a software testing apparatus 50, including:
a setting module 501, configured to set one or more software test rules through a test rule module, where the one or more test rules in the test rule module are sent to a test engine through a first communication interface;
a selecting module 502, configured to select a target test rule among the one or more test rules based on the configuration parameters for the target software object sent by the configuration center module to the test engine through the second communication interface;
an obtaining module 503, configured to obtain, for the target test rule, a metric parameter that quantifies the target test rule from a test metric module, where the metric parameter is sent to a test engine through a third communication interface;
the execution module 504 is configured to display the test state and the test result of the target software object in the trace tool module by using a fourth communication interface connected to the test engine.
The apparatus shown in fig. 5 may correspondingly execute the content in the above method embodiment, and details of the part not described in detail in this embodiment refer to the content described in the above method embodiment, which is not described again here.
Referring to fig. 6, an embodiment of the present disclosure also provides an electronic device 60, including:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the software testing method of the method embodiments described above.
The disclosed embodiments also provide a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the foregoing method embodiments.
The disclosed embodiments also provide a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform the software testing method in the aforementioned method embodiments.
Referring now to FIG. 6, a schematic diagram of an electronic device 60 suitable for use in implementing embodiments of the present disclosure is shown. The electronic devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., car navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 6, the electronic device 60 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 60 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 60 to communicate with other devices wirelessly or by wire to exchange data. While the figures illustrate an electronic device 60 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring at least two internet protocol addresses; sending a node evaluation request comprising the at least two internet protocol addresses to node evaluation equipment, wherein the node evaluation equipment selects the internet protocol addresses from the at least two internet protocol addresses and returns the internet protocol addresses; receiving an internet protocol address returned by the node evaluation equipment; wherein the obtained internet protocol address indicates an edge node in the content distribution network.
Alternatively, the computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a node evaluation request comprising at least two internet protocol addresses; selecting an internet protocol address from the at least two internet protocol addresses; returning the selected internet protocol address; wherein the received internet protocol address indicates an edge node in the content distribution network.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".
It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof.
The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present disclosure should be covered within the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.
Claims (13)
1. A software testing method, comprising:
setting one or more software test rules through a test rule module, wherein the one or more test rules in the test rule module are sent to a test engine through a first communication interface;
selecting a target test rule from the one or more test rules based on configuration parameters for the target software object sent by the configuration center module to the test engine through the second communication interface;
aiming at the target test rule, acquiring a measurement parameter quantifying the target test rule from a test measurement module, and sending the measurement parameter to a test engine through a third communication interface;
and displaying the test state and the test result of the target software object in a tracking tool module by using a fourth communication interface connected with the test engine.
2. The method of claim 1, wherein after the setting of the one or more software test rules by the test rules module, the method further comprises:
acquiring one or more test rules existing in the test engine through a rule group management module;
setting an expected value for one or more acquired test rules existing in the test engine.
3. The method of claim 1, wherein the setting one or more software test rules by the test rules module comprises:
a scalar or a plurality of test scalars, the type, the priority and the weight of the test rule are set for each software test rule.
4. The method of claim 1, wherein the setting one or more software test rules by the test rules module comprises:
and constructing a rule group consisting of a plurality of test rules aiming at the encoding stage, the construction stage and the release stage of the target test software to form an association rule set.
5. The method of claim 1, wherein prior to selecting a target test rule among the one or more test rules based on the configuration parameters for the target software object sent by the configuration hub module to the test engine via the second communication interface, the method further comprises:
binding a rule set and a project extension attribute for the target test software in the configuration center module;
and generating configuration parameters aiming at the target software object based on the rule group bound for the target test software and the project extension attribute.
6. The method of claim 1, wherein obtaining, for the target test rule, a metric parameter from a test metric module that quantifies the target test rule comprises:
obtaining, in the test metrics module, a test rule describing a type, a classification, and a usage scalar of a test metric.
7. The method of claim 1, wherein prior to presenting the test status and test results of the target software object in a trace tool module using a fourth communication interface coupled to the test engine, the method further comprises:
compiling the target test rule of the target test software into a test workflow by using a rule compiler, wherein the test workflow has a globally unique number;
executing the test workflow with the test engine.
8. The method of claim 7, wherein said executing the test workflow with the test engine comprises:
and performing parameter verification and test rule verification on the test workflow by using a rule verifier, wherein the parameter verification verifies the condition that a selection rule is not configured so as to further determine whether a default value is used, the test rule verification verifies one rule, and information of a workflow source is measured according to the global unique number of the test workflow.
9. The method of claim 7, wherein said executing the test workflow with the test engine comprises:
and carrying out flow control on the compiling result of the rule compiler by using a testing state preset by a testing engine, wherein the testing state comprises one or more of ready, execution, pause, end, rule matching, rule mismatching, abnormal interruption and manual interruption.
10. The method of claim 1, wherein exposing the test status and the test result of the target software object in a trace tool module using a fourth communication interface connected to the test engine comprises:
generating a test report based on the results of the test engine, the test report including one or more of a workflow number, an expected result, an actual metric result, a configuration center number, and a rule set number.
11. A software testing apparatus, comprising:
the device comprises a setting module, a test engine and a test rule module, wherein the setting module is used for setting one or more software test rules through the test rule module, and the one or more test rules in the test rule module are sent to the test engine through a first communication interface;
the selection module is used for selecting a target test rule from the one or more test rules based on the configuration parameters aiming at the target software object, which are sent to the test engine by the configuration center module through the second communication interface;
the acquisition module is used for acquiring a measurement parameter quantifying the target test rule from the test measurement module aiming at the target test rule, and the measurement parameter is sent to a test engine through a third communication interface;
and the execution module is used for displaying the test state and the test result of the target software object in the tracking tool module by utilizing a fourth communication interface connected with the test engine.
12. An electronic device, characterized in that the electronic device comprises:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the software testing method of any one of claims 1-10.
13. A non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the software testing method of any one of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910917827.1A CN110674047B (en) | 2019-09-26 | 2019-09-26 | Software testing method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910917827.1A CN110674047B (en) | 2019-09-26 | 2019-09-26 | Software testing method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110674047A true CN110674047A (en) | 2020-01-10 |
| CN110674047B CN110674047B (en) | 2023-06-27 |
Family
ID=69079398
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910917827.1A Active CN110674047B (en) | 2019-09-26 | 2019-09-26 | Software testing method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110674047B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111239523A (en) * | 2020-02-21 | 2020-06-05 | 江西三晶电气有限公司 | Frequency converter testing system, method and device and storage medium |
| CN111258917A (en) * | 2020-04-08 | 2020-06-09 | 北京字节跳动网络技术有限公司 | Software testing system, method and device, computer readable storage medium |
| CN111352844A (en) * | 2020-03-04 | 2020-06-30 | 腾讯科技（深圳）有限公司 | Test method and related device |
| CN112286826A (en) * | 2020-11-25 | 2021-01-29 | 惠州Tcl移动通信有限公司 | VTS testing method, VTS testing device, storage medium and computer equipment |
| CN112905475A (en) * | 2021-03-11 | 2021-06-04 | 湖南化工职业技术学院（湖南工业高级技工学校） | Software testing platform based on computer |
| CN113836014A (en) * | 2021-09-18 | 2021-12-24 | 青岛中科曙光科技服务有限公司 | Interface testing method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090271426A1 (en) * | 2008-04-29 | 2009-10-29 | Affiliated Computer Services, Inc. | Converting between software objects |
| CN102789401A (en) * | 2012-07-12 | 2012-11-21 | 北京泛华恒兴科技有限公司 | Test process control method and device on basis of flexible testing technology |
| WO2017181591A1 (en) * | 2016-04-20 | 2017-10-26 | 乐视控股（北京）有限公司 | Testing method and system |
| CN107783893A (en) * | 2016-08-26 | 2018-03-09 | 上海计算机软件技术开发中心 | A kind of Auto-Test System and its implementation based on scene description |
| CN109032923A (en) * | 2018-06-21 | 2018-12-18 | 深圳壹账通智能科技有限公司 | Method for testing software, device based on call chain, terminal |
| CN109542410A (en) * | 2018-11-29 | 2019-03-29 | 江苏满运软件科技有限公司 | Rule engine system, method, equipment and storage medium |
-
2019
- 2019-09-26 CN CN201910917827.1A patent/CN110674047B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090271426A1 (en) * | 2008-04-29 | 2009-10-29 | Affiliated Computer Services, Inc. | Converting between software objects |
| CN102789401A (en) * | 2012-07-12 | 2012-11-21 | 北京泛华恒兴科技有限公司 | Test process control method and device on basis of flexible testing technology |
| WO2017181591A1 (en) * | 2016-04-20 | 2017-10-26 | 乐视控股（北京）有限公司 | Testing method and system |
| CN107783893A (en) * | 2016-08-26 | 2018-03-09 | 上海计算机软件技术开发中心 | A kind of Auto-Test System and its implementation based on scene description |
| CN109032923A (en) * | 2018-06-21 | 2018-12-18 | 深圳壹账通智能科技有限公司 | Method for testing software, device based on call chain, terminal |
| CN109542410A (en) * | 2018-11-29 | 2019-03-29 | 江苏满运软件科技有限公司 | Rule engine system, method, equipment and storage medium |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111239523A (en) * | 2020-02-21 | 2020-06-05 | 江西三晶电气有限公司 | Frequency converter testing system, method and device and storage medium |
| CN111352844A (en) * | 2020-03-04 | 2020-06-30 | 腾讯科技（深圳）有限公司 | Test method and related device |
| CN111258917A (en) * | 2020-04-08 | 2020-06-09 | 北京字节跳动网络技术有限公司 | Software testing system, method and device, computer readable storage medium |
| CN112286826A (en) * | 2020-11-25 | 2021-01-29 | 惠州Tcl移动通信有限公司 | VTS testing method, VTS testing device, storage medium and computer equipment |
| CN112286826B (en) * | 2020-11-25 | 2024-04-09 | 惠州Tcl移动通信有限公司 | VTS test method and device, storage medium and computer equipment |
| CN112905475A (en) * | 2021-03-11 | 2021-06-04 | 湖南化工职业技术学院（湖南工业高级技工学校） | Software testing platform based on computer |
| CN113836014A (en) * | 2021-09-18 | 2021-12-24 | 青岛中科曙光科技服务有限公司 | Interface testing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110674047B (en) | 2023-06-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110674047B (en) | Software testing method and device and electronic equipment | |
| US10459828B2 (en) | Method and system for software application testing recommendations | |
| US20150026664A1 (en) | Method and system for automated test case selection | |
| US10031841B2 (en) | Method and system for incrementally updating a test suite utilizing run-time application executions | |
| US20150007148A1 (en) | Identifying Test Cases Based on Changed Test Code | |
| CN109976998B (en) | Software defect prediction method and device and electronic equipment | |
| CN110765596B (en) | Modeling method and device for auditing process simulation model and electronic equipment | |
| CN112597047A (en) | Test method, test device, electronic equipment and computer readable medium | |
| CN112395188B (en) | Test-oriented software project development method and device, electronic equipment and storage medium | |
| CN116225886A (en) | Test case generation method, device, equipment, storage medium and program product | |
| US8782626B2 (en) | Search suggestions for static code analysis | |
| CN112817869A (en) | Test method, test device, test medium, and electronic apparatus | |
| CN111625291A (en) | Automatic iteration method and device of data processing model and electronic equipment | |
| CN106034150B (en) | Application program dynamic pushing method, device and system | |
| CN116450511A (en) | Information updating method, device, electronic equipment and computer readable medium | |
| CN110609786A (en) | Software testing method and device, computer equipment and storage medium | |
| CN109471787B (en) | Software quality evaluation method and device, storage medium and electronic equipment | |
| CN116149978A (en) | Service interface testing method and device, electronic equipment and storage medium | |
| CN115048107A (en) | Code compiling method, system, electronic device and storage medium | |
| CN112379967B (en) | Simulator detection method, device, equipment and medium | |
| CN114185805A (en) | Embedded point verification method, device, equipment and storage medium | |
| CN114116480A (en) | Method, device, medium and equipment for determining application program test coverage rate | |
| CN111367791B (en) | Method, device, medium and electronic equipment for generating test case | |
| CN113760768A (en) | Test method, monitoring platform, electronic equipment and storage medium | |
| CN113806231A (en) | Code coverage rate analysis method, device, equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |