CN107423214A - Software regression testing use-case acquisition methods, device and storage medium and electronic equipment - Google Patents
Software regression testing use-case acquisition methods, device and storage medium and electronic equipment Download PDFInfo
- Publication number
- CN107423214A CN107423214A CN201710252931.4A CN201710252931A CN107423214A CN 107423214 A CN107423214 A CN 107423214A CN 201710252931 A CN201710252931 A CN 201710252931A CN 107423214 A CN107423214 A CN 107423214A
- Authority
- CN
- China
- Prior art keywords
- code
- source code
- test case
- executable statement
- case
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
Abstract
The disclosure is directed to a kind of software regression testing use-case acquisition methods and device.This method includes：Establish in source code the position relationship table of often row executable statement and the corresponding unique identification information of association；The unique identification information corresponding to the executable statement covered when being performed according to test case, and determine with reference to the position relationship table incidence relation table of each test case executable statement corresponding with the source code；The test case corresponding to renewal part after determining the source code renewal according to the incidence relation table back mapping.The test case that the disclosure can be returned automatically and accurately for renewal Code location needed for, improves testing efficiency, reduces manpower and expends and shorten the testing time.
Description
Technical field
This disclosure relates to software testing technology field, more particularly to a kind of software regression testing use-case acquisition methods, software
Regression test case acquisition device and realize the software regression testing use-case acquisition methods computer-readable recording medium and
Electronic equipment.
Background technology
After the completion of software test is software development, link that correctness, reliability and stability to software are verified.
Software test uses this usually according to the specification in software development each stage and the internal structure design test case of program
A little test cases go to drive tested program, the implementing result of procedures of observation, checking the actual running results and expected result whether one
Cause.Therefore the core and key that test case is software test are chosen with holding water.
In correlation technique, regression test is often carried out in software test, and after software product submits test, due to product
Complicated, iterative development, developer are each responsible for the reasons such as individual module, and developer is very after causing software version update
Difficult changed with regard to software code is partly supplied to a accurate regression test case of tester.It is to use in presently relevant technology
Artificial or full code scans mode finds out code variations part, afterwards by manual evaluation or from static code use-case mapping table
Find out the test case corresponding to code variations part.But inventor studies and found, the accuracy of which is poor, can cause
Deviation occurs in measurement direction, and either tester must not change to prevent from omitting without full dose or beyond code variations
The test job of scope.It is low that Efficiency of Software Testing can be also further resulted in addition, wasted substantial amounts of manpower and time, also extended
Testing time of product, and the problems such as error rate is high, maintenance cost is high be present.
Therefore, it is necessary to providing a kind of new technical scheme improves one or more problem present in such scheme.
It should be noted that information is only used for strengthening the reason to the background of the disclosure disclosed in above-mentioned background section
Solution, therefore can include not forming the information to prior art known to persons of ordinary skill in the art.
The content of the invention
The purpose of the disclosure is to provide a kind of software regression testing use-case acquisition methods, the acquisition of software regression testing use-case
Device and the computer-readable recording medium and electronic equipment for realizing the software regression testing use-case acquisition methods, and then at least
One or more problem caused by the limitation of correlation technique and defect is overcome to a certain extent.
Other characteristics and advantage of the disclosure will be apparent from by following detailed description, or partially by the disclosure
Practice and acquistion.
According to the first aspect of the embodiment of the present disclosure, there is provided a kind of software regression testing use-case acquisition methods, methods described
Including：
Establish in source code the position relationship table of often row executable statement and the corresponding unique identification information of association；
The unique identification information corresponding to the executable statement covered when being performed according to test case, and with reference to described
Position relationship table determines the incidence relation table of each test case executable statement corresponding with the source code；
The test corresponding to renewal part after determining the source code renewal according to the incidence relation table back mapping
Use-case.
In a kind of exemplary embodiment of the disclosure, the unique identification information includes code stake；It is described to establish source code
In often row executable statement include with the position relationship table of the corresponding unique identification information of association：
In the source code implementation procedure, the often code stake output corresponding to row executable statement in the source code
Stake hit information；The stake hit information goes to current line executable statement for characterizing the source code；
After the source code is finished, it is corresponding with association in the source code that information is hit according to each stake
Executable statement establishes the position relationship table.
In a kind of exemplary embodiment of the disclosure, the executable statement pair covered when being performed according to test case
The unique identification information answered, and determine that each test case is corresponding with the source code with reference to the position relationship table
The incidence relation table of executable statement includes：
When a test case is performed, the test case is recorded until the covered executable statement that is finished
All stake hit information of the corresponding code stake output；
According to all stake hit information for belonging to the test case, searched in the position relationship table and determine institute
Have the stake hit information associate in the source code corresponding to executable statement, and then each test case of determination with it is described
The incidence relation table of corresponding executable statement in source code.
In a kind of exemplary embodiment of the disclosure, methods described also includes：
Using the institute that unique mark is added after code pitching pile the technology in advance often row executable statement in the source code
State code stake.
In a kind of exemplary embodiment of the disclosure, methods described also includes：
The source code is pre-processed to remove the invalid code in the source code and be not called upon in code
It is at least one.
It is described the source code to be pre-processed to remove the source code in a kind of exemplary embodiment of the disclosure
In invalid code and be not called upon in code it is at least one including：
The source code is filtered by default code filters rule to remove the invalid generation in the source code
Code and be not called upon it is at least one in code.
In a kind of exemplary embodiment of the disclosure, methods described also includes：
Path analysis is carried out to the source code and determines that the difference belonging to the source code deposits paths, to establish positioned at not
Part of original code with storage path deposits the first path list associated between path with corresponding；
According to the mapping relations between default software level and storage path, the first path list is layered
Handle and be located at the different part of original code for depositing paths and the second path column associated between corresponding software level to generate
Table；
It is the default one or more software layer in second path list according to default layered filtration rule
Level sets an identification information, so that part of original code corresponding to the one or more software level does not perform regression test.
It is described that the source generation is determined according to the incidence relation table back mapping in a kind of exemplary embodiment of the disclosure
The test case corresponding to renewal part after code renewal includes：
Obtain the executable statement of the default line number belonging to the renewal part in the source code after renewal；
Retrieved and determined corresponding to the executable statement of the default line number in the incidence relation table by back mapping
Test case is with to the source code progress regression test after renewal；
When test case corresponding to the executable statement for not retrieving the default line number, after supplementing new test case
The incidence relation table is redefined, and then determines test case corresponding to the renewal part.
According to the second aspect of the embodiment of the present disclosure, there is provided a kind of software regression testing use-case acquisition device, described device
Including：
Code relation establishes module, and for establishing, often row executable statement unique mark corresponding with association is believed in source code
The position relationship table of breath；
Use case relationship establishes module, corresponding to the executable statement covered during for being performed according to test case it is described only
One identification information, and determine each test case executable statement corresponding with the source code with reference to the position relationship table
Incidence relation table；And
Use-case acquisition module is returned, after determining the source code renewal according to the incidence relation table back mapping
Update the test case corresponding to part.
According to the third aspect of the embodiment of the present disclosure, there is provided a kind of computer-readable recording medium, be stored thereon with calculating
Machine program, the program realize software regression testing use-case acquisition methods described in any of the above-described embodiment when being executed by processor
Step.
According to the fourth aspect of the embodiment of the present disclosure, there is provided a kind of electronic equipment, the electronic equipment can include：
Processor；And
Memory, for storing the executable instruction of the processor；
Wherein, the processor is configured to perform described in any of the above-described embodiment via the executable instruction is performed
The step of software regression testing use-case acquisition methods.
The technical scheme provided by this disclosed embodiment can include the following benefits：
In a kind of embodiment of the disclosure, by above-mentioned software regression testing use-case acquisition methods and device, pass through foundation
The every incidence relation of row executable statement and the corresponding unique identification information of association in source code, it is true further according to the incidence relation
The incidence relation table of fixed each test case executable statement corresponding with the source code, finally according to the incidence relation
Table back mapping determines the test case corresponding to the renewal part after the source code renewal.Thus it is possible, on the one hand, in test
Automatically the test case that renewal Code location returns needed for can be accurately directed to, so as to avoid test deviation or nothing
Meaning ground expanded scope, improves testing efficiency；On the other hand, reduce manpower to expend and shorten the testing time, difference during test
Error rate is low and reduces maintenance cost etc..
It should be appreciated that the general description and following detailed description of the above are only exemplary and explanatory, not
The disclosure can be limited.
Brief description of the drawings
Accompanying drawing herein is merged in specification and forms the part of this specification, shows the implementation for meeting the disclosure
Example, and be used to together with specification to explain the principle of the disclosure.It should be evident that drawings in the following description are only the disclosure
Some embodiments, for those of ordinary skill in the art, on the premise of not paying creative work, can also basis
These accompanying drawings obtain other accompanying drawings.
Fig. 1 schematically shows software regression testing use-case acquisition methods flow chart in disclosure exemplary embodiment；
Fig. 2 schematically shows software regression testing use-case acquisition methods flow chart in disclosure exemplary embodiment；
Fig. 3 schematically shows the incidence relation table generated in disclosure exemplary embodiment between test case and source code
Flow chart；
Fig. 4 schematically shows regression test case in disclosure exemplary embodiment and obtains flow chart；
Fig. 5 schematically shows source code pretreatment process figure in disclosure exemplary embodiment；
Fig. 6 schematically shows another pretreatment process figure of source code in disclosure exemplary embodiment；
Fig. 7 schematically shows a software regression testing use-case acquisition device schematic diagram in disclosure exemplary embodiment；
Fig. 8 schematically shows another software regression testing use-case acquisition device schematic diagram in disclosure exemplary embodiment.
Embodiment
Example embodiment is described more fully with referring now to accompanying drawing.However, example embodiment can be with a variety of shapes
Formula is implemented, and is not understood as limited to example set forth herein；On the contrary, these embodiments are provided so that the disclosure will more
Fully and completely, and by the design of example embodiment comprehensively it is communicated to those skilled in the art.Described feature, knot
Structure or characteristic can be incorporated in one or more embodiments in any suitable manner.
In addition, accompanying drawing is only the schematic illustrations of the disclosure, it is not necessarily drawn to scale.Identical accompanying drawing mark in figure
Note represents same or similar part, thus will omit repetition thereof.Some block diagrams shown in accompanying drawing are work(
Can entity, not necessarily must be corresponding with physically or logically independent entity.These work(can be realized using software form
Energy entity, or these functional entitys are realized in one or more hardware modules or integrated circuit, or at heterogeneous networks and/or place
These functional entitys are realized in reason device device and/or microcontroller device.
A kind of software regression testing use-case acquisition methods are provide firstly in this example embodiment.With reference to shown in figure 1,
This method may comprise steps of：
Step S101：Establish in source code the position relationship of often row executable statement and the corresponding unique identification information of association
Table.
Step S102：The unique identification information corresponding to the executable statement covered when being performed according to test case,
And the incidence relation of each test case executable statement corresponding with the source code is determined with reference to the position relationship table
Table.
Step S103：Determine that the renewal part institute after the source code renewal is right according to the incidence relation table back mapping
The test case answered.
Pass through above-mentioned software regression testing use-case acquisition methods, on the one hand, can accurately be directed to automatically in test
The test case that Code location returns needed for is updated, so as to avoid test deviation or unnecessarily expanded scope, improves and surveys
Try efficiency；On the other hand, reduce manpower to expend and shorten the testing time, error rate during test it is low and reduce maintenance into
This etc..
Below, each step of the above method in this example embodiment will be carried out referring to figs. 1 to Fig. 6 more detailed
Explanation.
In step S101, the position of often row executable statement and the corresponding unique identification information of association is established in source code
Relation table.Such as can in software source code implementation procedure, establish in the source code often row executable statement with associating pair
The position relationship table for the unique identification information answered.Wherein, in the source code often row executable statement can be preset with it is described only
One identification information.
In this example embodiment, the software source code for example can be complete applications source code or
One or more of one application program source code of funtion part etc., is not particularly limited to this.The position relationship
The corresponding pass of association between often row executable statement in table in source code described in stored record and often capable unique identification information
System.
Exemplary, the unique identification information can include code stake, naturally it is also possible to be other mark letters such as probe
Breath, is not particularly limited to this.In a kind of exemplary embodiment, methods described can also include：Using code pitching pile technology
The code stake of unique mark is added after the often row executable statement in the source code in advance.The code pitching pile technology category
In existing mature technology, repeat no more.After the source code pitching pile, the code stake of unique mark is added, is performed in source code
During the code stake of every row executable statement can export stake in real time and hit information into a file, and then stake hit can be produced
The incidence relation of information and the executable statement in the corresponding source code, i.e., described position relationship table.
It is described to establish in source code often row executable statement and the corresponding unique identification information of association with reference to shown in figure 2
Position relationship table may comprise steps of：
Step S201：It is often described corresponding to row executable statement in the source code in the source code implementation procedure
Code stake exports a hit information.The stake hit information goes to the executable language of current line for characterizing the source code
Sentence.
It is exemplary, such as 26 row executable statements in source code are corresponding inserted with code stake A~Z, due to source code
Code stake can export stake hit information in real time in the process of implementation, that is, represent that current source code has gone to which of source code
OK, therefore stake hit information such as A ', C ' can be recorded corresponding to the 3 row executable statements as corresponding to A, C and E having been carried out
And E '.
Step S202：After the source code is finished, hit according to each stake in information and the source code
Executable statement corresponding to association establishes the position relationship table.
Exemplary, such as stake hit information A ', C ' and E ' can be based on including code in the corresponding source code
The mapping relations of stake A, C and E 3 row executable statements establish the position relationship table.
In step s 102, the unique mark letter corresponding to the executable statement covered when being performed according to test case
Breath, and determine that the association of each test case executable statement corresponding with the source code is closed with reference to the position relationship table
It is table.Such as the source code can be tested using default basic test use-case, then used according to a test
The unique identification information corresponding to the executable statement that example is covered, the test is found in the position relationship table and is used
Executable statement corresponding to example, so that it is determined that the association of each test case executable statement corresponding with the source code is closed
It is table.
Here, it is necessary to should be mentioned that, during coverage test is realized, generally require to know certain category information, such as program
Middle executable statement is performed the situation, path, the reference of variable or definition that program performs etc. of (i.e. capped).Want to obtain
This category information is taken, it is necessary to track the implementation procedure of tested program code, or performed by computer in tested program code
During record automatically.The former needs manually to carry out, and efficiency is low and dry as dust.And the latter is then needed in tested program code
The code of relevant work is completed in middle insertion, and foregoing code pitching pile technology insertion code stake is used in this example embodiment.Institute
The executable statement stated does not include the content such as C++ header file statement, code annotation, null.Therefore only statistics can be held
Capable code has been performed how many row.It should be noted that individually the brace " { } " of a line is also usually entered by statistics.
In addition, sentence covering (Statement Coverage), also known as row covering (Line Coverage), this is the most frequently used and most
A kind of common coverage mode, exactly measures whether each executable statement in tested code is performed to.Code coverage is also
Section covering (Segment Coverage) and basic block covering (Basic Block Coverage) etc. can be included.This example is real
Apply in mode and illustrate so that row covers as an example, be not used in and limit this example embodiment.
In one exemplary embodiment, in the step S102, the executable language that is covered when being performed according to test case
Sentence corresponding to the unique identification information, and with reference to the position relationship table determine each test case with it is right in the source code
The incidence relation table for the executable statement answered may comprise steps of：
Step 1021：When a test case is performed, the test case is recorded until being finished what is covered
All stake hit information of the code stake output corresponding to executable statement；
Exemplary, it is assumed that there are multiple numbered test cases of tool, can remember when such as test case 1 is performed
It is recorded until all piles hit letter that the code stake corresponding to for example above-mentioned 3 row executable statement covered that is finished exports
Breath.This 3 row executable statement in the process of implementation, often go corresponding to code stake such as stake A, C and E can export stake hit information such as
A ', C ' and E ', then can record and belong to stake hit information such as A ', C ' and E ' corresponding to test case 1.
Step 1022：According to all stake hit information for belonging to the test case, in the position relationship table
Search determine all stakes hit information associate in the source code corresponding to executable statement, and then determine each to test
The incidence relation table of use-case executable statement corresponding with the source code.
Exemplary, it can be closed according to above-mentioned stake hit the information such as A ', C ' and E ' for belonging to test case 1 in the position
It is to be searched in table, to determine that all piles hit information A ', C ' and E ' can perform language in the source code corresponding to relationship maps
Sentence, the i.e. 3 row executable statements including code stake A, C and E.Then it is assured that in test case 1 and the source code
The relationship maps relation of executable statement (i.e. the 3 row executable statements including code stake A, C and E), and then can obtain each
The incidence relation table of test case executable statement corresponding with source code.So, test case and institute are just established
State the mapping relations between the executable statement of corresponding line in source code.
With reference to shown in figure 3, in an exemplary embodiment, in step s 102, what test case was covered can
Coverage device 302 can be performed to handle by code by performing the coverage condition of sentence, such as can be based on code stake corresponding source
The position relationship table of code, handled for the file comprising stake hit information of output, finally obtain code execution
Source file coverage condition corresponding to process.And test case can be performed instrument 301 when being performed real by automation use-case
It is existing, may finally be by code use-case mapping tool 303 by test case and the executable language with corresponding line in the source code
Sentence mapping association is so as to establish the incidence relation table, i.e., the code use-case mapping table shown in Fig. 3.It should be noted that institute
It is existing skill to state automation use-case and perform instrument 301, code execution coverage device 302 and code use-case mapping tool 303
Art, repeat no more.
Exemplary, the automation use-case performs instrument 301 after each test case is finished, can be by use-case
Numbering is sent to the code use-case mapping tool 303.The code use-case mapping tool 303 calls the code to perform covering
The result of calculator 302, closed so as to establish the mapping between current test case executable statement corresponding with source code
System.The incidence relation table between basic test use-case and source code has just been obtained after all test cases are finished.
As shown in table 1, it is an exemplary incidence relation table.
Table 1
| Use-case is numbered | Use-case is summarized | Source file | Source file line number |
| 1103 | xxxx | /src/app/a | 1~80 |
| /src/app/b | 1~100 | ||
| /src/app/c | 1~50 | ||
| 1105 | xxxx | /src/app/d | 50~80 |
| /src/app/e | 90~120 |
In step s 103, the renewal part after the source code renewal is determined according to the incidence relation table back mapping
Corresponding test case.
Here, it is necessary to which explanation, regression test refer to after have modified old code, test is re-started to confirm the modification
Do not introduce new mistake or cause other codes to produce mistake.Automatic regression test will be greatly reduced system testing, safeguard liter
The cost in the stages such as level.A part of the regression test as software life-cycle, is accounted in whole software test procedure
There is very big workload proportion, each stage of software development can all carry out multiple regression test.Opened in progressive and iteratively faster
In hair, the continuous issue of redaction makes the more frequent of regression test progress, and in Extreme Programming method, even more require daily
All carry out regression test several times.Therefore, improve the efficiency of regression test by selecting correct regression testing policy and have
Effect property is significant.For a development project, test group meeting during implementing to test of project
The test case developed is saved in test case library, and is maintained and manages.When obtaining the base of a software
During line version, all test cases for baseline version test are formed baseline test case library.Test case (Test
Case) it is one group of test input, execution condition and the expected results worked out for some special objective, to test some journey
Whether sequence path or verification meet some particular demands.
The test case being stored in the baseline test case library is probably automatic test script, it is also possible to is test
The manual implementation process of use-case.Regression test needs time, funds and manpower planning, implementing and managing.In order to given
Under budget and progress, regression test is carried out as efficiently as possible, it is necessary to be safeguarded to test case library and according to certain plan
Slightly select corresponding regression test bag.When tester has enough confidence to the part of code revision, dependence can be passed through
The modification situation for analyzing identification software code simultaneously analyzes the influence of modification, by regression test be confined to the module that is changed and it
On interface.Generally, a recurrence mistake is certain is related to new, modification or deletion a code segment.Under conditions of permission,
Regression test needs to cover affected part as far as possible.
When needing to carry out regression test, it can be tested according to selected regression testing policy from the baseline
Suitable test case composition regression test bag is extracted in use-case storehouse, regression test is realized by running regression test bag.
Exemplary, after determining the source code renewal according to the incidence relation table back mapping described in step S103
Renewal part corresponding to test case may comprise steps of：
Step 1031：Obtain the executable language of the default line number belonging to the renewal part in the source code after renewal
Sentence.
It is exemplary, such as developer have updated the generation of the code, i.e. the 5th~6 row of original 5th~6 row in source code
Code is renewal part, and code administration server can produce the code update inventory on updating part, and code update inventory is used for
Show developer is modified renewal to which row in source code.Therefore the renewal can be determined according to the code update inventory
Default line number executable statement belonging to part, such as the executable statement in the code of the 5th~6 row.
Step 1032：The executable language for determining the default line number is retrieved in the incidence relation table by back mapping
Test case corresponding to sentence.When test case corresponding to the executable statement for not retrieving the default line number, supplement new
The incidence relation table is redefined after test case, and then determines test case corresponding to the renewal part.
With reference to shown in figure 4, it can be utilized in an exemplary code tester application scenarios, after source code renewal anti-
Produced to reflection method to test case corresponding to the code update part in requisition for regression test, can specifically include following step
Suddenly：
Step 401：Developer submits the source code after renewal to code administration server.
Step 402：Code update inventory as shown in table 2 is sent to use-case after code administration server process and retrieves work
Tool.
Table 2
| Filename | Update line number | Newly-increased line number |
| /src/app/a | 5~6 | 90~160 |
Step 403：Use-case gopher is (i.e. above-mentioned such as the institute of table 1 from code use-case mapping table according to the code update inventory
The incidence relation table between the basic test use-case and source code that show) in retrieve corresponding regression test case.Order
Use-case numbering 1103 corresponding to line number 5~6 is updated in middle file/src/app/a, as shown in table 3.Can is based on use-case afterwards
Test case corresponding to numbering 1103 carries out regression test to the source code after renewal.By retrieving test case and source generation
The mode of code use-case mapping table between code, automatically obtains corresponding regression test case, has saved the testing time, improve
Testing efficiency.
Table 3
| Filename | Update line number | Use-case is numbered |
| /src/app/a | 5~6 | 1103 |
But for increasing the code of line number 90~160 in file/src/app/a as shown in table 2 newly, do not retrieve
As a result, as shown in table 4.In this case, it can supplement and repeat after new code tester use-case such as the illustrated embodiment of Fig. 1~2
In above method step, update the incidence relation table between test case and source code, the code use after being updated
Example mapping table, and then follow-up test can be realized.
Table 4
| Filename | Newly-increased line number | Perform use-case |
| /src/app/a | 90~160 |
Above is the mode of regression test case is obtained in the case of two kinds：The first is to retrieve above-mentioned generation after code update
Code use-case mapping table obtains regression test case.Second is according to the regression test case obtained in above-mentioned table 3, along with this
Secondary newly-increased test case is as regression test case, wherein the code use-case mapping table after being updated is desirable.
In this exemplary code tester application scenarios, automatically update/supplement due to code use-case mapping table can be based on
Retrieval is so that it is determined that arrive regression test case so that tester can more accurately obtain this modification or code update
The test case that should be returned, so as to avoid test deviation or unnecessarily expanded scope, when reduction manpower expends and shortens test
Between, so as to improve testing efficiency.
With reference to shown in figure 5, in order to further improve the treatment effeciency to source code, in one exemplary embodiment, institute
The method of stating can also include：The source code is pre-processed to remove the invalid code in the source code and be not called upon
It is at least one in code.For example, the code of unique mark is added after often row executable statement in the source code
Before stake, the pretreatment can be carried out, is certainly not limited to this.
It is exemplary, it is described the source code is pre-processed with remove invalid code in the source code and not by
Call at least one can include in code：The source code is filtered to remove by default code filters rule
Invalid code in the source code and it is not called upon at least one in code.
For example, code filter 503 as shown in Figure 5 can be according to default as illustrated in table 5
The code filters rule of invalid code is rejected, filters out the annotation in source code and the code without concern.
Table 5
| Rise | Only |
| /* | */ |
| // | |
| # |
The code filter 503 can also reject the zombie code being not called upon, such as can pass through code traversal pair
The method being not called upon is identified, so as to reject the zombie code that these are not called upon.
In the present exemplary embodiment, source file (i.e. source code) is pre-processed, can with automatic rejection invalid code and
It is not called upon code.Thus, can reduce pre-inserted during the above-mentioned incidence relation table between test case and source code is produced
Stake treating capacity, so as to improve calculation process efficiency and test case execution efficiency.
With reference to reference to shown in figure 5~6, in one exemplary embodiment, methods described can also comprise the following steps：
Step S601：Path analysis is carried out to the source code and determines that the difference belonging to the source code deposits paths, with
Establish the part of original code positioned at different storage paths and deposit the first path list associated between path with corresponding.
Exemplary, usual source code can be stored in different catalogue (corresponding different storage paths) by its function and attribute
Below, the source code of different directories belongs to different software levels, such as inner nuclear layer, resource layer, bottom, application layer and ccf layer
Deng, and the code of different software layer levels covers to test case and requires different.Such as resource layer, inner nuclear layer and bottom etc.
Code, because test case covering has little significance, follow-up test can not be carried out to it.
When it is implemented, for example source code can be inputted into a path analyzer 501, the path analysis device 501 is to institute
State source code and carry out path analysis to determine the first path list.
Step S602：According to the mapping relations between default software level and storage path, the first path is arranged
Table carries out layered shaping and is located at the different part of original code for depositing paths to generate and is associated between corresponding software level
Second path list.
Exemplary, above-mentioned first path list can be input to a hierarchical processor by the path analysis device 501
502.The hierarchical processor 502 is according to the floor title (corresponding software level) and pathname (corresponding storage road prestored
Footpath) between mapping table as shown in table 6, layered shaping is carried out to the first path list, generation carries hierarchical information
The second path list as shown in table 7.Wherein, it is exemplary, path is entitled/src/app storage path namely the storage
The code of the application layer in source code is stored under catalogue, other storage paths are similar therewith.
Table 6
| Pathname | Layer title |
| kernel | Inner nuclear layer |
| jpg | Resource layer |
| lib | Bottom |
| app | Application layer |
| framwork | Ccf layer |
Table 7
Step S603：It is default one or more institutes in second path list according to default layered filtration rule
State software level and one identification information is set, so that part of original code corresponding to the one or more software level does not perform back
Return test.
Exemplary, second path list can be inputed to the code filter by the hierarchical processor 502
503.The code filter 503 sets mark according to the layered filtration rule pre-set to such as resource layer, inner nuclear layer, bottom
Information is known so that the code of those layers is verified without returning, as shown in table 8.The layer title that rest layers can be obtained afterwards is i.e. corresponding
A software level corresponding to code tested.
Table 8
| Layer title | It is whether effective |
| Inner nuclear layer | It is no |
| Resource layer | It is no |
| Bottom | It is no |
| Application layer | It is |
| Ccf layer | It is |
Above-mentioned steps S601~S603 can filtered off except the invalid code in the source code and be not called upon code
Implement before, be certainly not limited to this.The code filter 503 can be obtained by above-mentioned processing procedure as shown in Figure 5
The final code not filtered, i.e., the source code after effectively being identified.It is possible thereby to further reducing needs pretreatment filtration
The scope of invalid code, treating capacity is reduced, improves treatment effeciency.It should be noted that the path analysis device 501, layering
Processor 502 and code filter 503 are existing mature technology, are repeated no more.
In summary, the above method in this illustrative embodiments, source file can be pre-processed, produced first
The valid code inventory for needing test case to cover.By being pre-processed to source file, reduce pre- pitching pile treating capacity, improve
Calculation process efficiency and test case execution efficiency.Secondly, dynamic auto generation is surveyed in test exemple automation implementation procedure
The incidence relation table on probation between example and source code, testing efficiency can be improved.Finally according to institute after source code renewal
Incidence relation table is stated, is produced using back mapping method to the use-case inventory in requisition for regression test so that can be compared with test
The test case of required recurrence is automatically positioned for more fresh code exactly, so as to avoid test from deviateing or unnecessarily expand
On a large scale, further improve testing efficiency, while also reduce manpower and expend and shorten the testing time, error rate during test it is low and
Reduce maintenance cost.
It should be noted that although describing each step of method in the disclosure with particular order in the accompanying drawings, still,
This, which does not require that or implied, to perform these steps according to the particular order, or has to carry out the step shown in whole
Desired result could be realized.It is additional or alternative, it is convenient to omit some steps, multiple steps to be merged into a step and held
OK, and/or by a step execution of multiple steps etc. are decomposed into.In addition, being also easy to understand, these steps can be
Such as either synchronously or asynchronously performed in multiple module/process/threads.
Further, in this example embodiment, a kind of software regression testing use-case acquisition device is additionally provided.Reference chart
Shown in 7, device 700 can establish module 701 including code relation, use case relationship establishes module 702 and return use-case obtains
Module 703.Wherein：
The code relation establishes module 701, and for establishing, often row executable statement is corresponding with association only in source code
The position relationship table of one identification information.
The use case relationship establishes module 702, and the executable statement covered during for being performed according to test case is corresponding
The unique identification information, and determine that each test case is corresponding with the source code with reference to the position relationship table can
Perform the incidence relation table of sentence.
The recurrence use-case acquisition module 703, for determining the source code according to the incidence relation table back mapping
The test case corresponding to renewal part after renewal.
In a kind of exemplary embodiment of the disclosure, the unique identification information can include code stake.Accordingly, institute
State code relation and establish module 701, in the source code implementation procedure, every row executable statement pair in the source code
The code stake output stake hit information answered；Stake hit information, which is used to characterizing the source code, to be gone to current line and can hold
Line statement；After the source code is finished, it is corresponding with association in the source code that information is hit according to each stake
The position relationship table is established in the position of executable statement.
In a kind of exemplary embodiment of the disclosure, the use case relationship establishes module 702, for when a test
When use-case is performed, the test case is recorded until the code stake output corresponding to covered executable statement that is finished
All stakes hit information；According to all stake hit information for belonging to the test case, in the position relationship
Searched in table determine all stakes hit information associate in the source code corresponding to executable statement, and then determine each
The incidence relation table of test case executable statement corresponding with the source code.
In a kind of exemplary embodiment of the disclosure, described device 700 can also include code pitching pile module, and (figure is not
Show), for using the institute that unique mark is added after code pitching pile the technology in advance often row executable statement in the source code
State code stake.
In a kind of exemplary embodiment of the disclosure, described device 700 can also include code filters module, and (figure is not
Show), the invalid code in the source code and it is not called upon for being pre-processed to the source code with removing in code
It is at least one.
In a kind of exemplary embodiment, the code filters module, for by default code filters rule to institute
Source code is stated to be filtered to remove the invalid code in the source code and be not called upon at least one in code.
In a kind of exemplary embodiment of the disclosure, described device 700 can also include code tester setup module (figure
Do not show), determine that the difference belonging to the source code deposits paths for carrying out path analysis to the source code, be located at establishing
The first path list associated between the part of original code in difference storage path and corresponding storage path；Then, according to default
Mapping relations between software level and storage path, layered shaping is carried out to the first path list to generate positioned at described
The part of original code in difference storage path and the second path list associated between corresponding software level；Finally, according to default
Layered filtration rule is that the default one or more software level sets an identification information in second path list, with
Part of original code corresponding to the one or more software level is set not perform regression test.
In a kind of exemplary embodiment of the disclosure, the recurrence use-case acquisition module 703, after obtaining renewal
The executable statement of the default line number belonging to renewal part in the source code；Again by back mapping in the incidence relation
Retrieval determines test case corresponding to the executable statement of the default line number in table.
On the device in above-described embodiment, wherein modules perform the concrete mode of operation in relevant this method
Embodiment in be described in detail, explanation will be not set forth in detail herein.
It should be noted that although some modules or list of the equipment for action executing are referred in above-detailed
Member, but this division is not enforceable.In fact, according to embodiment of the present disclosure, it is above-described two or more
Either the feature of unit and function can embody module in a module or unit.A conversely, above-described mould
Either the feature of unit and function can be further divided into being embodied by multiple modules or unit block.As module or list
The part of member display can be or may not be physical location, you can with positioned at a place, or can also be distributed to
On multiple NEs.Some or all of module therein can be selected according to the actual needs to realize the open scheme of wood
Purpose.Those of ordinary skill in the art are without creative efforts, you can to understand and implement.
In this example embodiment, a kind of computer-readable recording medium is additionally provided, is stored thereon with computer program,
The program realizes the step of software regression testing use-case acquisition methods described in any of the above-described embodiment when being executed by processor.Institute
The specific steps for stating software regression testing use-case acquisition methods refer to use on above-mentioned software regression testing in previous embodiment
The detailed description of example each step of acquisition methods, here is omitted.The computer-readable recording medium can be ROM, random
Access memory (RAM), CD-ROM, tape, floppy disk and optical data storage devices etc..
In this example embodiment, a kind of electronic equipment is also provided, the electronic equipment can include processor and be used for
Store the memory of the executable instruction of the processor.Wherein, the processor is configured to via the execution executable finger
The step of order is to perform software regression testing use-case acquisition methods described in any of the above-described embodiment.The software regression testing use-case
The step of acquisition methods, refers to the detailed description in preceding method embodiment, and here is omitted.
Through the above description of the embodiments, those skilled in the art is it can be readily appreciated that example described herein is implemented
Mode can be realized by software, can also be realized by way of software combines necessary hardware.Therefore, according to the disclosure
The technical scheme of embodiment can be embodied in the form of software product, the software product can be stored in one it is non-volatile
Property storage medium (can be CD-ROM, USB flash disk, mobile hard disk etc.) in or network on, including some instructions are to cause a calculating
Equipment (can be personal computer, server, touch control terminal or network equipment etc.) is performed according to disclosure embodiment
Method.
Fig. 8 is shown according to a kind of signal of software regression testing use-case acquisition device 800 in disclosure example embodiment
Figure.For example, device 800 may be provided in a server.Reference picture 8, device 800 include processing component 422, and it is further wrapped
One or more processors are included, and as the memory resource representated by memory 432, can be by processing component 422 for storing
The instruction of execution, such as application program.The application program stored in memory 432 can include one or more each
The individual module for corresponding to one group of instruction.In addition, processing component 422 is configured as execute instruction, to perform the above method.
Device 800 can also include the power management that a power supply module 426 is configured as performs device 400, and one has
Line or radio network interface 450 are configured as device 400 being connected to network, and input and output (I/O) interface 458.Dress
Putting 800 can operate based on the operating system for being stored in memory 432, such as Windows ServerTM, Mac OS XTM,
UnixTM, LinuxTM, FreeBSDTM or similar.
Those skilled in the art will readily occur to the disclosure its after considering specification and putting into practice invention disclosed herein
Its embodiment.The application is intended to any modification, purposes or the adaptations of the disclosure, these modifications, purposes or
Person's adaptations follow the general principle of the disclosure and including the undocumented common knowledges in the art of the disclosure
Or conventional techniques.Description and embodiments are considered only as exemplary, and the true scope of the disclosure and spirit are by appended
Claim is pointed out.
Claims (11)
1. a kind of software regression testing use-case acquisition methods, it is characterised in that methods described includes：
Establish in source code the position relationship table of often row executable statement and the corresponding unique identification information of association；
The unique identification information corresponding to the executable statement covered when being performed according to test case, and with reference to the position
Relation table determines the incidence relation table of each test case executable statement corresponding with the source code；
The test case corresponding to renewal part after determining the source code renewal according to the incidence relation table back mapping.
2. method according to claim 1, it is characterised in that the unique identification information includes code stake；It is described to establish source
Often row executable statement includes with the position relationship table of the corresponding unique identification information of association in code：
In the source code implementation procedure, often the code stake output stake corresponding to row executable statement is ordered in the source code
Middle information；The stake hit information goes to current line executable statement for characterizing the source code；
After the source code is finished, information is hit according to each stake and association is corresponding in the source code holds
Line statement establishes the position relationship table.
3. method according to claim 2, it is characterised in that the executable language covered when being performed according to test case
Sentence corresponding to the unique identification information, and with reference to the position relationship table determine each test case with it is right in the source code
The incidence relation table for the executable statement answered includes：
When a test case is performed, the test case is recorded until the executable statement for being finished covered is corresponding
Code stake output all stakes hit information；
According to all stake hit information for belonging to the test case, searched in the position relationship table and determine all institutes
State stake hit information associate in the source code corresponding to executable statement, and then determine each test case and the source generation
The incidence relation table of corresponding executable statement in code.
4. method according to claim 2, it is characterised in that methods described also includes：
Using the generation that unique mark is added after code pitching pile the technology in advance often row executable statement in the source code
Code stake.
5. according to any one of Claims 1 to 4 methods described, it is characterised in that methods described also includes：
The source code is pre-processed to remove the invalid code in the source code and be not called upon in code at least
One.
6. method according to claim 5, it is characterised in that described to be pre-processed to the source code to remove the source
Invalid code in code and be not called upon in code it is at least one including：
The source code is filtered by default code filters rule with remove the invalid code in the source code and
It is not called upon at least one in code.
7. method according to claim 5, it is characterised in that methods described also includes：
Path analysis is carried out to the source code and determines that the difference belonging to the source code deposits paths, is deposited with establishing positioned at difference
Put the part of original code in path and the first path list associated between corresponding storage path；
According to the mapping relations between default software level and storage path, layered shaping is carried out to the first path list
To generate the part of original code in paths and the second path list associated between corresponding software level are deposited positioned at the difference；
It is that the default one or more software level is set in second path list according to default layered filtration rule
An identification information is put, so that part of original code corresponding to the one or more software level does not perform regression test.
8. method according to claim 5, it is characterised in that described according to determining the incidence relation table back mapping
The test case corresponding to renewal part after source code renewal includes：
Obtain the executable statement of the default line number belonging to the renewal part in the source code after renewal；
Retrieved by back mapping in the incidence relation table and determine test corresponding to the executable statement of the default line number
Use-case；
When test case corresponding to the executable statement for not retrieving the default line number, supplement after new test case again
The incidence relation table is determined, and then determines test case corresponding to the renewal part.
9. a kind of software regression testing use-case acquisition device, it is characterised in that described device includes：
Code relation establishes module, for establishing in source code often row executable statement and the corresponding unique identification information of association
Position relationship table；
Use case relationship establishes module, unique mark corresponding to the executable statement covered during for being performed according to test case
Know information, and the pass of each test case executable statement corresponding with the source code is determined with reference to the position relationship table
Join relation table；And
Use-case acquisition module is returned, for determining the renewal after the source code renewal according to the incidence relation table back mapping
Test case corresponding to part.
10. a kind of computer-readable recording medium, is stored thereon with computer program, it is characterised in that the program is by processor
The step of any one of the claim 1~8 software regression testing use-case acquisition methods are realized during execution.
11. a kind of electronic equipment, it is characterised in that including：
Processor；And
Memory, for storing the executable instruction of the processor；
Wherein, the processor is configured to that to carry out any one of perform claim requirement 1~8 described soft via the executable instruction is performed
The step of part regression test case acquisition methods.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710252931.4A CN107423214A (en) | 2017-04-18 | 2017-04-18 | Software regression testing use-case acquisition methods, device and storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710252931.4A CN107423214A (en) | 2017-04-18 | 2017-04-18 | Software regression testing use-case acquisition methods, device and storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107423214A true CN107423214A (en) | 2017-12-01 |
Family
ID=60424233
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710252931.4A Pending CN107423214A (en) | 2017-04-18 | 2017-04-18 | Software regression testing use-case acquisition methods, device and storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107423214A (en) |
Cited By (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108427637A (en) * | 2018-01-18 | 2018-08-21 | 平安科技（深圳）有限公司 | Test cases recommends method, electronic device and readable storage medium storing program for executing |
| CN108763091A (en) * | 2018-05-31 | 2018-11-06 | 恒生电子股份有限公司 | Method, apparatus and system for regression test |
| CN109240911A (en) * | 2018-08-13 | 2019-01-18 | 腾讯科技（北京）有限公司 | Accurate test method, device and computer equipment |
| CN109240700A (en) * | 2018-07-06 | 2019-01-18 | 北京大学 | Key code localization method and system |
| CN109388568A (en) * | 2018-09-29 | 2019-02-26 | 百度在线网络技术（北京）有限公司 | Code test method and device |
| CN109726132A (en) * | 2019-01-03 | 2019-05-07 | 京东方科技集团股份有限公司 | A kind of method for testing software and software test automation management system |
| CN109783382A (en) * | 2019-01-07 | 2019-05-21 | 郑州云海信息技术有限公司 | A kind of test method and system based on accurate test platform |
| CN109828911A (en) * | 2018-12-26 | 2019-05-31 | 北京仁科互动网络技术有限公司 | A kind of test method and device |
| CN110245081A (en) * | 2019-05-31 | 2019-09-17 | 厦门美柚信息科技有限公司 | Generate the method and device of minimum test scope |
| CN110347576A (en) * | 2018-04-04 | 2019-10-18 | 阿里巴巴集团控股有限公司 | Pseudocode adjustment method and device |
| CN110489321A (en) * | 2019-07-08 | 2019-11-22 | 平安科技（深圳）有限公司 | Test case screening technique, device, computer equipment and storage medium |
| CN110727597A (en) * | 2019-10-15 | 2020-01-24 | 杭州安恒信息技术股份有限公司 | Method for completing use case based on log troubleshooting invalid codes |
| CN110928770A (en) * | 2019-10-29 | 2020-03-27 | 航天信息股份有限公司 | Software testing method, device, system, storage medium and electronic equipment |
| CN110941555A (en) * | 2019-11-26 | 2020-03-31 | 广州品唯软件有限公司 | Test case recommendation method and device, computer equipment and storage medium |
| CN111045944A (en) * | 2019-12-11 | 2020-04-21 | 广州品唯软件有限公司 | Regression testing method, device and system and computer readable storage medium |
| CN111124875A (en) * | 2018-10-31 | 2020-05-08 | 北京金山云网络技术有限公司 | Test case determination method and device and electronic equipment |
| CN111309609A (en) * | 2020-02-13 | 2020-06-19 | 北京字节跳动网络技术有限公司 | Software processing system |
| CN111309611A (en) * | 2020-02-16 | 2020-06-19 | 苏州浪潮智能科技有限公司 | Multi-version testing method and system for software product |
| CN111400164A (en) * | 2020-02-07 | 2020-07-10 | 浙江口碑网络技术有限公司 | Software testing method and device |
| CN111408142A (en) * | 2020-05-06 | 2020-07-14 | 网易（杭州）网络有限公司 | Method and device for determining object with incidence relation, medium and electronic equipment |
| CN111611154A (en) * | 2019-02-26 | 2020-09-01 | 北京新能源汽车股份有限公司 | Regression testing method, device and equipment |
| CN112035374A (en) * | 2020-09-09 | 2020-12-04 | 中国铁塔股份有限公司 | Regression testing method and system and electronic equipment |
| CN112835779A (en) * | 2019-11-25 | 2021-05-25 | 上海哔哩哔哩科技有限公司 | Test case determination method and device and computer equipment |
| CN114741315A (en) * | 2022-04-28 | 2022-07-12 | 深圳市紫光同创电子有限公司 | Use case updating method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102750153A (en) * | 2012-06-29 | 2012-10-24 | 南京大学 | Regression testing case set construction method based on program change |
| CN103034582A (en) * | 2011-09-28 | 2013-04-10 | 腾讯科技（深圳）有限公司 | Method and system for positioning regression cases |
| US20130311976A1 (en) * | 2012-05-17 | 2013-11-21 | Cognizant Technology Solutions India Pvt. Ltd. | Method and system for generating and processing black box test cases |
| CN105302710A (en) * | 2014-07-03 | 2016-02-03 | 腾讯科技（深圳）有限公司 | Method and apparatus for determining test case in need of regression testing |
| CN106528399A (en) * | 2015-09-15 | 2017-03-22 | 腾讯科技（深圳）有限公司 | Test case determination method and apparatus |
-
2017
- 2017-04-18 CN CN201710252931.4A patent/CN107423214A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103034582A (en) * | 2011-09-28 | 2013-04-10 | 腾讯科技（深圳）有限公司 | Method and system for positioning regression cases |
| US20130311976A1 (en) * | 2012-05-17 | 2013-11-21 | Cognizant Technology Solutions India Pvt. Ltd. | Method and system for generating and processing black box test cases |
| CN102750153A (en) * | 2012-06-29 | 2012-10-24 | 南京大学 | Regression testing case set construction method based on program change |
| CN105302710A (en) * | 2014-07-03 | 2016-02-03 | 腾讯科技（深圳）有限公司 | Method and apparatus for determining test case in need of regression testing |
| CN106528399A (en) * | 2015-09-15 | 2017-03-22 | 腾讯科技（深圳）有限公司 | Test case determination method and apparatus |
Cited By (35)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108427637A (en) * | 2018-01-18 | 2018-08-21 | 平安科技（深圳）有限公司 | Test cases recommends method, electronic device and readable storage medium storing program for executing |
| CN110347576B (en) * | 2018-04-04 | 2023-09-12 | 创新先进技术有限公司 | Pseudo code debugging method and device |
| CN110347576A (en) * | 2018-04-04 | 2019-10-18 | 阿里巴巴集团控股有限公司 | Pseudocode adjustment method and device |
| CN108763091B (en) * | 2018-05-31 | 2022-05-27 | 恒生电子股份有限公司 | Method, device and system for regression testing |
| CN108763091A (en) * | 2018-05-31 | 2018-11-06 | 恒生电子股份有限公司 | Method, apparatus and system for regression test |
| CN109240700A (en) * | 2018-07-06 | 2019-01-18 | 北京大学 | Key code localization method and system |
| CN109240911A (en) * | 2018-08-13 | 2019-01-18 | 腾讯科技（北京）有限公司 | Accurate test method, device and computer equipment |
| CN109388568B (en) * | 2018-09-29 | 2020-05-15 | 百度在线网络技术（北京）有限公司 | Code testing method and device |
| CN109388568A (en) * | 2018-09-29 | 2019-02-26 | 百度在线网络技术（北京）有限公司 | Code test method and device |
| CN111124875A (en) * | 2018-10-31 | 2020-05-08 | 北京金山云网络技术有限公司 | Test case determination method and device and electronic equipment |
| CN109828911A (en) * | 2018-12-26 | 2019-05-31 | 北京仁科互动网络技术有限公司 | A kind of test method and device |
| US11281570B2 (en) | 2019-01-03 | 2022-03-22 | Boe Technology Group Co., Ltd. | Software testing method, system, apparatus, device medium, and computer program product |
| CN109726132B (en) * | 2019-01-03 | 2021-03-23 | 京东方科技集团股份有限公司 | Software testing method and software testing automatic management system |
| CN109726132A (en) * | 2019-01-03 | 2019-05-07 | 京东方科技集团股份有限公司 | A kind of method for testing software and software test automation management system |
| CN109783382A (en) * | 2019-01-07 | 2019-05-21 | 郑州云海信息技术有限公司 | A kind of test method and system based on accurate test platform |
| CN111611154A (en) * | 2019-02-26 | 2020-09-01 | 北京新能源汽车股份有限公司 | Regression testing method, device and equipment |
| CN111611154B (en) * | 2019-02-26 | 2024-03-01 | 北京新能源汽车股份有限公司 | Regression testing method, device and equipment |
| CN110245081A (en) * | 2019-05-31 | 2019-09-17 | 厦门美柚信息科技有限公司 | Generate the method and device of minimum test scope |
| CN110489321A (en) * | 2019-07-08 | 2019-11-22 | 平安科技（深圳）有限公司 | Test case screening technique, device, computer equipment and storage medium |
| CN110727597B (en) * | 2019-10-15 | 2023-03-10 | 杭州安恒信息技术股份有限公司 | Method for checking invalid code completion case based on log |
| CN110727597A (en) * | 2019-10-15 | 2020-01-24 | 杭州安恒信息技术股份有限公司 | Method for completing use case based on log troubleshooting invalid codes |
| CN110928770B (en) * | 2019-10-29 | 2023-11-28 | 航天信息股份有限公司 | Software testing method, device, system, storage medium and electronic equipment |
| CN110928770A (en) * | 2019-10-29 | 2020-03-27 | 航天信息股份有限公司 | Software testing method, device, system, storage medium and electronic equipment |
| CN112835779A (en) * | 2019-11-25 | 2021-05-25 | 上海哔哩哔哩科技有限公司 | Test case determination method and device and computer equipment |
| CN110941555A (en) * | 2019-11-26 | 2020-03-31 | 广州品唯软件有限公司 | Test case recommendation method and device, computer equipment and storage medium |
| CN110941555B (en) * | 2019-11-26 | 2023-07-28 | 广州品唯软件有限公司 | Test case recommendation method and device, computer equipment and storage medium |
| CN111045944A (en) * | 2019-12-11 | 2020-04-21 | 广州品唯软件有限公司 | Regression testing method, device and system and computer readable storage medium |
| CN111400164A (en) * | 2020-02-07 | 2020-07-10 | 浙江口碑网络技术有限公司 | Software testing method and device |
| CN111309609A (en) * | 2020-02-13 | 2020-06-19 | 北京字节跳动网络技术有限公司 | Software processing system |
| CN111309609B (en) * | 2020-02-13 | 2023-10-03 | 抖音视界有限公司 | software processing system |
| CN111309611A (en) * | 2020-02-16 | 2020-06-19 | 苏州浪潮智能科技有限公司 | Multi-version testing method and system for software product |
| CN111408142B (en) * | 2020-05-06 | 2023-09-08 | 网易（杭州）网络有限公司 | Method and device for determining object with association relationship, medium and electronic equipment |
| CN111408142A (en) * | 2020-05-06 | 2020-07-14 | 网易（杭州）网络有限公司 | Method and device for determining object with incidence relation, medium and electronic equipment |
| CN112035374A (en) * | 2020-09-09 | 2020-12-04 | 中国铁塔股份有限公司 | Regression testing method and system and electronic equipment |
| CN114741315A (en) * | 2022-04-28 | 2022-07-12 | 深圳市紫光同创电子有限公司 | Use case updating method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107423214A (en) | Software regression testing use-case acquisition methods, device and storage medium and electronic equipment | |
| US10877874B2 (en) | Systems and methods for modeling and generating test requirements for software applications | |
| CN103473342B (en) | A kind of report data generation method and system | |
| CN105589874B (en) | Detection method, device and the ETL tool of ETL task dependence | |
| CN100492316C (en) | System and method for test automation | |
| CN107957957A (en) | The acquisition methods and device of test case | |
| US20210279257A1 (en) | Identity Mapping For Cloud Migrations | |
| CN109992508A (en) | Test exemple automation generation method, device and electronic equipment | |
| CN109299083A (en) | A kind of data governing system | |
| CN106294128B (en) | A kind of automated testing method and device exporting report data | |
| CN103955429B (en) | Determine the method and device of regression test scope | |
| Marques-Silva | Computing Minimally Unsatisfiable Subformulas: State of the Art and Future Directions. | |
| CN109828750A (en) | Auto-configuration data buries method, apparatus, electronic equipment and storage medium a little | |
| CN107729510B (en) | Information interaction method, information interaction terminal and storage medium | |
| CN103970654B (en) | Software reliability virtual test method | |
| CN109800147B (en) | Test case generation method and terminal equipment | |
| CN107766253A (en) | A kind of method of the automatic maintenance test script based on model change | |
| Lin et al. | Finding metamorphic relations for scientific software | |
| CN116301745A (en) | Micro-service dividing method and device based on programming framework field knowledge | |
| Zhou et al. | Deeptle: Learning code-level features to predict code performance before it runs | |
| CN110147941A (en) | Content of examination acquisition methods, Stakeholder Evaluation method and device | |
| CN109542496A (en) | Incremental code determines method, apparatus and system | |
| CN115858337A (en) | Test method, test apparatus, computer-readable storage medium, and electronic device | |
| CN105354144B (en) | Business support system information model uniformity automated testing method and system | |
| CN115600972A (en) | Method, device, equipment and storage medium for verifying and selling of bad assets |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Hu Ruili Inventor before: Hu Ruili |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20171201 |