CN109783358A - A kind of software version management method, system and the storage medium of regression test driving - Google Patents
A kind of software version management method, system and the storage medium of regression test driving Download PDFInfo
- Publication number
- CN109783358A CN109783358A CN201811535329.2A CN201811535329A CN109783358A CN 109783358 A CN109783358 A CN 109783358A CN 201811535329 A CN201811535329 A CN 201811535329A CN 109783358 A CN109783358 A CN 109783358A
- Authority
- CN
- China
- Prior art keywords
- test
- software
- version
- new
- source program
- 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
Landscapes
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses software version management method, system and the storage mediums of a kind of regression test driving, the method: it submits source program to carry out first stage verifying to new using the available test case in test program corresponding to previous version software source program, obtains covering result for the first time；According to first time covering as a result, submitting source program to carry out automatic generating test case to new；It submits source program to carry out second stage verifying to new using test case generated, obtains second of covering result；According to second of covering as a result, writing new test case, the new test program for submitting source program is generated；Verification file and the version number for calculating test program generate new version software in conjunction with the new verification file for submitting source program and version number.The present invention can effectively solve the problem that current SVM tool is difficult to that the management of test code, regression test information is effectively supported to be unable to fully the problem utilized, and then research staff is helped to improve software version management quality, improve software product efficiency of research and development.
Description
Technical field
The present invention relates to software version management method, system and the storage mediums of a kind of regression test driving, belong to software
EVOLUTION ANALYSIS technical field.
Background technique
Traditional software development process defines the fixed mode of software development, as waterfall model divides software development process
For six root phases such as plan, demand analysis, software design, programming, software test, operation and maintenance, people is researched and developed
Member is sequentially sequentially completed.However, with the fast development of Software Industry, software size is increasing, complicated process is higher and higher,
Software development cycle, development cost problem out of control are got worse.At this point, emphasizing that iterative developing, increment are delivered, persistently collected
Come into being at the agile development model that, feedback pushes, and by its quickly research and development, quickly deliver, capability of fast response obtains
Being widely recognized as of industry.During agile development, a large project may be broken down into it is multiple connect each other, can be independent
The sub-project of operation is developed respectively, and demand change is encountered in exploitation may require that research staff actively embraces variation, thus can be produced
The software version of raw multiple and different forms.At this time, it may be necessary to Software Edition management tool SVM (Software Version
Management, software version management) it is recorded and is managed, to help research staff to be best understood from software in different times
Function and performance.
Currently, software version management has become the important component in Current software R&D process, academia and work
Industry also proposes various software method for edition management in succession, and has developed SVM tool (such as CVS, SVN, Git of a variety of maturations
Deng).By SVM tool, research staff can store catalogue and file modification history, support software configuration management activity,
Track the exploitation and maintenance activity, the relevant information for issuing software of multiple versions, research and development of these functions to software product is improved
Efficiency plays the role of vital.However, although current SVM tool provides well the management of software source program
It supports, but is also not provided with the support of effect to the management that software includes test code.Traditional SVM tool will test code mostly
See a part of software source program as, research staff needs oneself to safeguard the test code of each software version；Furthermore new
When version is submitted, due to functionality change, error correction, Format adjusting etc., there may be not for the test case of previous version
Situations such as can using, is inadequate, needs manually to be modified it and supplement, time and effort consuming.
Summary of the invention
It is an object of the invention to overcome deficiency in the prior art, a kind of software version pipe of regression test driving is provided
Reason method, system and storage medium can effectively solve the problem that current SVM tool is difficult to effectively support the management of test code, return
Test information is unable to fully the problem utilized, and then research staff is helped to improve software version management quality, improves software product
Efficiency of research and development.
In order to achieve the above objectives, the present invention adopts the following technical solutions realization:
In a first aspect, the present invention provides a kind of software version management method of regression test driving, the method includes
Following steps:
Using the available test case in test program corresponding to previous version software source program to it is new submit source program into
The verifying of row first stage obtains covering result for the first time；
According to first time covering as a result, submitting source program to carry out automatic generating test case to new；
It submits source program to carry out second stage verifying to new using test case generated, obtains second of covering knot
Fruit；
According to second of covering as a result, writing new test case, the new test program for submitting source program is generated；
Verification file and the version number for calculating test program generate in conjunction with the new verification file for submitting source program and version number
New version software.
With reference to first aspect, further, described to include: with the acquisition methods of test case
According to the source program of given software storage and current software version, the test case of previous software version is searched；
Availability analysis is carried out to the test case of previous software version, the available test case that analysis is obtained is as new
The available test case of version software source program.
With reference to first aspect, further, the method for the second stage verifying includes:
With the source program of given current software version, covering result and maximized window width, the width are used for for the first time
The maximum number for limiting Test Auto-generation result generates base to cover the sentence other than result for the first time as test target
In the exception error test case of randomized policy；
The new exception error for submitting source program to be included is detected using the exception error test case.
With reference to first aspect, further, if the new submission source program fails through first stage verifying or second-order
Section verifying then returns to the modification new version software source program.
With reference to first aspect, further, the method for generating the new version software includes:
The integrity checking and new version software source program of test program binary version are calculated separately using Checksum algorithm
The integrity checking of binary version and, and thus generate test program verification file, new version software source program verification file；
Text is verified according to the verification file generated new version software of the verification file of test program, new version software source program
Part；
The version number of test program, new version software source are worked out using GNU or Windows or .Net Framework style
The version number of program；
The version number of the version number of test program, new version software source program is combined and generates new version software version
Number；
File is verified according to new version software, new version software version number generates new version software.
It with reference to first aspect, further, include parity check code, exclusive or check code, CRC check in the verification file
Code, LRC check code, Gray code check code, MD5 check code.
Second aspect, the embodiment of the invention provides a kind of software version management system of regression test driving, features
It is, the system comprises:
First authentication module: for using the available test case in test program corresponding to previous version software source program
It submits source program to carry out first stage verifying to new, obtains covering result for the first time；
Test cases technology module: being used for according to covering for the first time as a result, submitting source program development test case certainly to new
It is dynamic to generate；
Second authentication module: for submitting source program to carry out second stage verifying to new using test case generated,
Obtain second of covering result；
Write module: for, as a result, writing new test case, the test of source program newly to be submitted in generation according to second of covering
Program；
Computing module: for calculating verification file and the version number of test program；
New version software generation module: for according to the verification file of test program and version number, new source program of submitting
It verifies file and version number generates new version software.
The third aspect, the embodiment of the invention also provides a kind of software version management systems of regression test driving, including
Processor and storage medium；
The storage medium is for storing instruction；
The processor is used for the step of being operated according to described instruction to execute according to preceding method.
Fourth aspect, the embodiment of the invention provides computer readable storage mediums, are stored thereon with computer program,
The step of being characterized in that, preceding method realized when which is executed by processor.
To sum up, software version management method, system and the storage medium of regression test driving provided in an embodiment of the present invention,
It can effectively solve the problem that current SVM tool is difficult to effectively to support what the test management of code, regression test information were unable to fully to utilize
Problem, and then research staff is helped to improve software version management quality, improve software product efficiency of research and development.
Detailed description of the invention
Fig. 1 is the flow chart for the software version management method that the present invention implements a kind of regression test provided driving；
Fig. 2 is the flow chart of software version automatic verification method in Fig. 1；
Fig. 3 is the flow chart of automatic example generation method in Fig. 1；
Fig. 4 is the flow chart of beta version automatic management method in Fig. 1；
Fig. 5 is the flow chart of software version automatic management method in Fig. 1.
Specific embodiment
The invention will be further described below in conjunction with the accompanying drawings.Following embodiment is only used for clearly illustrating the present invention
Technical solution, and not intended to limit the protection scope of the present invention.
Fig. 1 is a kind of flow chart of the software version management method for regression test driving that present invention implementation provides, including
Following steps:
Step1 software version is verified automatically: the source program version newly submitted for user, analyzes the previous version source of the version
Available test case in test program corresponding to program, and the defects of new submission source program: defect if it exists is detected with it,
Then show source program there are problem, needs to resubmit after modifying；Otherwise show that source program is verified by the first stage, it is defeated at this time
Test case and its coverage information can be used out, to instruct next stage Test Auto-generation.
Step2 automatic generating test case: it does not cover sentence using previous step and submits source program to open for new as test target
Test Auto-generation is opened up, constantly executes newly-generated test case while generating, whether to observe new submission source program
It is abnormal mistake: if being abnormal, showing source program there are problem, need to resubmit after modifying；Otherwise show source journey
Sequence is verified by second stage, exports newly-generated test case and coverage information at this time, to instruct next stage test to use
Example is write.During Test Auto-generation, do not cover result with previous stage meets situation building stopping criterion.
Step3 beta version manages automatically: not covering sentence using first two steps as test target and submits source program for new
It carries out test case to write, newly-generated test case is constantly executed while writing, to detect new submit in source program
Defect: defect if it exists then shows source program there are problem, needs to resubmit after modifying；Otherwise show that source program passes through
Phase III verifying generates the new test program of Test cases technology based on first two steps at this time, and calculates the verification of test program
Code, exports the verification file of test program.
Step4 software version manages automatically: calculating and generates the new version number for submitting source program, and cooperates with test program version
Number generate software version number；Analysis generates the new verification file for submitting source program, and cooperates with the verification file of test program raw
At the verification file of software；After software version number, verification file generated, source program and its corresponding test program are submitted together with new
It saves into software storage, completes the generation and registration of software new version.
Fig. 2 is the flow chart that software version is verified automatically.For the source program version newly submitted, by analyzing previous version
Corresponding test program identification is new to submit the available test case of source program, is executed to it and to verify the source newly submitted automatically
Program, while generating coverage information and providing guidance for Test Auto-generation.Specific step is as follows:
Step 1: initial state；
Step 2: the current version Pi of Input Software warehouse SR, source program；
Step 3: judge whether Pi is initial version P0, it is no to then follow the steps 6 if so then execute step 4；
Step 4: initialization test set of uses case Toldi is sky NULL；
Step 5: the coverage information cov (Toldi) for initializing Toldi is sky NULL, executes step 10；
Step 6: software version Vi-1=< IDVi-1, Pi-1, Ti-1, CC_ where the previous version of Pi are taken out from SR
FILE_Vi-1 >, IDVi-1, Pi-1, Ti-1, CC_FILE_Vi-1 respectively indicate the version number of Vi-1, source program, test program
With verification file；
Step 7: identifying that the available test case of all Pi constitutes Toldi in Ti-1；
Step 8: executing Toldi using Pi, Toldi is further divided into successfully by test use cases according to implementing result
Told_passedi and failure testing set of uses case Told_failedi, and record the coverage information of Toldi；
Step 9: judging in Told_failedi whether content is otherwise sky NULL if so then execute step 10 executes step
Rapid 11；
Step 10:Pi exports Toldi and cov (Toldi) by the 1st phase authentication, executes step 12；
Step 11:Pi does not pass through the 1st phase authentication, exports Told_failedi；
Step 12: terminating state.
Fig. 3 is the flow chart of automatic generating test case.Made with the not covered code region of previous version test program
Carry out Test Auto-generation for test target, and is examined at the same time using the exception error that newly-generated program carries out new version source program
It surveys, record automatically generates the coverage information of test case.Stopping criterion is constructed with code coverage situation in Self -adaptive.Specifically
Steps are as follows:
Step 1: initial state；
Step 2: coverage information cov (Toldi) and window of current version Pi, the Pi of input source program on Toldi are wide
Spend window；
Step 3: calculating unlapped code region uncov (Toldi) in Pi；
Step 4: initialization test set of uses case Tnew_autoi be sky NULL, initialize sequence coverage listcov=<
Cov1, cov2 ..., covwindow > in each element value be sky；
Step 5: generating a test case t at random for Pi；
Step 6: executing t and calculate coverage information cov (t)；
Step 7: judge whether be abnormal when executing t, it is no to then follow the steps 8 if so then execute step 14；
Step 8: in addition t to Tnew_autoi, it may be assumed that Tnew_autoi=Tnew_autoi ∪ { t }；
Step 9: updating sequence coverage listcov；
Step 10: judge whether cov (Tnew_autoi) contains all sentences in uncov (Toldi), if so then execute
Step 13, no to then follow the steps 11；
Step 11: judge whether the quantity of test case in Tnew_autoi is greater than window, if so then execute step 12,
It is no to then follow the steps 5；
Step 12: judging whether the value of each element in listcov is identical, if so then execute step 13, otherwise executes step
Rapid 5；
Step 13:Pi exports Tnew_autoi and cov (Tnew_autoi) by the 2nd phase authentication, executes step 15；
Step 14:Pi does not pass through the 2nd phase authentication, and output causes the test case t of Pi exception；Step 15: terminating state.
Fig. 4 is the flow chart that beta version manages automatically.With previous version test program and automatically generate test case not
Covered code region carries out test case as test target and writes, and detects the defects of new submission source program with this.
After source program is verified, combination producing newly submits the corresponding test program of source program and its version number and verification file.Specifically
Steps are as follows:
Step 1: initial state；
Step 2: the current version Pi of input source program, previous version available test case Toldi and coverage information cov
(Toldi) and the test case Tnew_autoi and coverage information cov (Tnew_autoi) that automatically generate；
Step 3: calculating unlapped code region uncov (Toldi ∪ Tnew_autoi) in Pi；
Step 4: writing new test case for Pi using uncov (Toldi ∪ Tnew_autoi) as test target
Tnew_manuali；
Step 5: executing Tnew_manuali using Pi, Tnew_manuali is further divided by success according to implementing result
Test use cases Tnew_manual_passedi and failure testing set of uses case Tnew_manual_failedi；
Step 6: judging whether Tnew_manual_failedi is otherwise sky NULL if so then execute step 7 executes step
Rapid 12；
Step 7: Toldi, Tnew_autoi and Tnew_manuali being merged and generate the corresponding test program Ti of Pi；
Step 8: the version number IDTi of test program Ti is worked out using the styles such as GNU, Windows .Net Framework；
Step 9: using modes such as even-odd check, exclusive or check, CRC check, LRC verification, Gray's code check, MD5 verifications
Generate the check code of the files such as Toldi, Tnew_autoi, Tnew_manuali；
Step 10: using Checksum algorithm calculate Ti binary version integrity checking and, and thus generate the verification of Ti
File CC_FILE_Ti, content include the check code of the files such as Toldi, Tnew_autoi, Tnew_manuali, Ti；
Step 11:Pi exports Ti, IDTi and CC_FILE_Ti by the 3rd phase authentication, executes step 13；
Step 12:Pi does not pass through the 3rd phase authentication, exports Tnew_manual_failedi；Step 13: terminating state.
Fig. 5 is the flow chart that software version manages automatically.Analysis generates the new version number for submitting source program, and cooperates with test
The version number of program generates the version number of new version software；Analysis generates the new verification file for submitting source program, and cooperates with test
The verification file of the verification file generated new version software of program；New version is added into software storage, completes software new version
Registration and publication.Specific step is as follows:
Step 1: initial state；
Step 2: the current version Pi of input source program and corresponding test program Ti, test program version IDTi and verification
File CC_FILE_Ti；
Step 3: the version number IDPi of source program is worked out using the styles such as GNU, Windows .Net Framework；
Step 4: by source program version number and test program version combination producing software version number IDVi=< IDPi,
IDTi>；
Step 5: using Checksum algorithm calculate Pi binary version integrity checking and, and thus generate Pi verification text
Part CC_FILE_Pi, content include the check code of the files such as CC_FILE_Pi；
Step 6: by the verification file CC_ of content combination producing software version Vi in CC_FILE_Pi and CC_FILE_Ti
FILE_Vi, content include the check code of the files such as Pi, Toldi, Tnew_autoi, Tnew_manuali, Ti；
Step 7: software version Vi=<IDPi, Pi, Ti, CC_FILE_Vi>is added in software storage SR；
Step 8: output Current software warehouse SR and software version Vi；
Step 9: terminating state.
It is difficult to effectively support the management of test code, regression test letter in conclusion the present invention solves current SVM tool
The problem underused is ceased, so as to enhance SVM tool software product function, research staff is helped to promote software version management
Quality has finally played the purpose for improving software product efficiency of research and development and ensureing speed measuring with software.
The embodiment of the invention also provides a kind of software version management system of regression test driving, the system can be used
In the software version management method for executing regression test driving above-mentioned, comprising:
First authentication module: for using the available test case in test program corresponding to previous version software source program
It submits source program to carry out first stage verifying to new, obtains covering result for the first time；
Test cases technology module: being used for according to covering for the first time as a result, submitting source program development test case certainly to new
It is dynamic to generate；
Second authentication module: for submitting source program to carry out second stage verifying to new using test case generated,
Obtain second of covering result；
Write module: for, as a result, writing new test case, the test of source program newly to be submitted in generation according to second of covering
Program；
Computing module: for calculating verification file and the version number of test program；
New version software generation module: for according to the verification file of test program and version number, new source program of submitting
It verifies file and version number generates new version software.
The embodiment of the invention also provides a kind of software version management systems of regression test driving, also can be used in executing
The software version management method of regression test driving above-mentioned, including processor and storage medium；
The storage medium is for storing instruction；
The processor is used for the step of being operated according to described instruction to execute according to preceding method.
The embodiment of the invention also provides computer readable storage mediums, are stored thereon with computer program, the program quilt
The step of preceding method is realized when processor executes.
The above is only a preferred embodiment of the present invention, it is noted that for the ordinary skill people of the art
For member, without departing from the technical principles of the invention, several improvement and deformations can also be made, these improvement and deformations
Also it should be regarded as protection scope of the present invention.
Claims (9)
1. a kind of software version management method of regression test driving, which is characterized in that described method includes following steps:
Source program is submitted to carry out the to new using the available test case in test program corresponding to previous version software source program
One phase authentication obtains covering result for the first time；
According to first time covering as a result, submitting source program to carry out automatic generating test case to new；
It submits source program to carry out second stage verifying to new using test case generated, obtains second of covering result；
According to second of covering as a result, writing new test case, the new test program for submitting source program is generated；
Verification file and the version number for calculating test program generate new edition in conjunction with the new verification file for submitting source program and version number
This software.
2. the software version management method of regression test driving according to claim 1, which is characterized in that the survey
The acquisition methods of example on probation include:
According to the source program of given software storage and current software version, the test case of previous software version is searched；
Availability analysis is carried out to the test case of previous software version, the available test case that analysis is obtained is as new version
The available test case of software source program.
3. the software version management method of regression test driving according to claim 1, which is characterized in that the second-order
Section verifying method include:
With the source program of given current software version, for the first time covering result and maximized window width, the width is for limiting
The maximum number of Test Auto-generation result, to cover the sentence other than result for the first time as test target, generate based on
The exception error test case of machine strategy；
The new exception error for submitting source program to be included is detected using the exception error test case.
4. the software version management method of regression test driving according to claim 3, which is characterized in that if described newly mention
Source program is handed over to fail then to return to the modification new version software source program by first stage verifying or second stage verifying.
5. the software version management method of regression test driving according to claim 1, which is characterized in that generate described new
The method of version software includes:
Using Checksum algorithm calculate separately test program binary version integrity checking and new version software source program two into
Make a plate this integrity checking and, and thus generate test program verification file, new version software source program verification file；
File is verified according to the verification file generated new version software of the verification file of test program, new version software source program；
The version number of test program, new version software source program are worked out using GNU or Windows or .Net Framework style
Version number；
The version number of the version number of test program, new version software source program is combined and generates new version software version number；
File is verified according to new version software, new version software version number generates new version software.
6. the software version management method of regression test driving according to claim 5, which is characterized in that the verification text
It include parity check code, exclusive or check code, cyclic redundancy check, LRC check code, Gray code check code, MD5 check code in part.
7. a kind of software version management system of regression test driving, which is characterized in that the system comprises:
First authentication module: for using the available test case in test program corresponding to previous version software source program to new
It submits source program to carry out first stage verifying, obtains covering result for the first time；
Test cases technology module: for being given birth to automatically according to first time covering as a result, carrying out test case to new submission source program
At；
Second authentication module: it for submitting source program to carry out second stage verifying to new using test case generated, obtains
Second of covering result；
Write module: for, as a result, writing new test case, the test journey of source program newly to be submitted in generation according to second of covering
Sequence；
Computing module: for calculating verification file and the version number of test program；
New version software generation module: for according to the verification file of test program and version number, the new verification for submitting source program
File and version number generate new version software.
8. a kind of software version management system of regression test driving, which is characterized in that including processor and storage medium；
The storage medium is for storing instruction；
The processor is used to be operated according to described instruction to execute the step of any one the method according to claim 1 ~ 6
Suddenly.
9. computer readable storage medium is stored thereon with computer program, which is characterized in that when the program is executed by processor
The step of realizing any one of claim 1 ~ 6 the method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811535329.2A CN109783358B (en) | 2018-12-14 | 2018-12-14 | Regression test driven software version management method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811535329.2A CN109783358B (en) | 2018-12-14 | 2018-12-14 | Regression test driven software version management method, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109783358A true CN109783358A (en) | 2019-05-21 |
| CN109783358B CN109783358B (en) | 2022-05-27 |
Family
ID=66496967
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811535329.2A Active CN109783358B (en) | 2018-12-14 | 2018-12-14 | Regression test driven software version management method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109783358B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112613894A (en) * | 2020-12-31 | 2021-04-06 | 中国农业银行股份有限公司 | Method and device for associating source code and product |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102831060A (en) * | 2012-08-24 | 2012-12-19 | 东南大学 | Modification influence analysis based regression test case updating method of part software |
| CN103123607A (en) * | 2013-03-08 | 2013-05-29 | 扬州大学 | Software regression testing method based on formal conceptual analysis |
| CN103699385A (en) * | 2013-12-23 | 2014-04-02 | 国云科技股份有限公司 | Continuous code integration method |
| US20160034382A1 (en) * | 2014-08-01 | 2016-02-04 | Unisys Corporation | Automated regression test case selector and black box test coverage tool for product testing |
-
2018
- 2018-12-14 CN CN201811535329.2A patent/CN109783358B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102831060A (en) * | 2012-08-24 | 2012-12-19 | 东南大学 | Modification influence analysis based regression test case updating method of part software |
| CN103123607A (en) * | 2013-03-08 | 2013-05-29 | 扬州大学 | Software regression testing method based on formal conceptual analysis |
| CN103699385A (en) * | 2013-12-23 | 2014-04-02 | 国云科技股份有限公司 | Continuous code integration method |
| US20160034382A1 (en) * | 2014-08-01 | 2016-02-04 | Unisys Corporation | Automated regression test case selector and black box test coverage tool for product testing |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112613894A (en) * | 2020-12-31 | 2021-04-06 | 中国农业银行股份有限公司 | Method and device for associating source code and product |
| CN112613894B (en) * | 2020-12-31 | 2024-04-16 | 中国农业银行股份有限公司 | Method and device for associating source code with product |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109783358B (en) | 2022-05-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7644398B2 (en) | System and method for automatic test-case generation for software | |
| Kalinowski et al. | Evidence-based guidelines to defect causal analysis | |
| US8954936B2 (en) | Enhancing functional tests coverage using traceability and static analysis | |
| CN105094851A (en) | Method for momentarily issuing codes based on Git | |
| US9760073B2 (en) | Technique and tool for efficient testing of controllers in development | |
| US20150370685A1 (en) | Defect localization in software integration tests | |
| CN107797929A (en) | The statistical method and device of FPGA emulation testing function coverage | |
| CN104408264A (en) | System and method for verifying embedded memory controller based on assertion | |
| US10761961B2 (en) | Identification of software program fault locations | |
| CN109885541A (en) | The method and apparatus of information batch processing | |
| CN111104155A (en) | Database script management platform and method, electronic equipment and storage medium | |
| CN102234046A (en) | Lift control software field debugging system | |
| CN115168868B (en) | Business vulnerability analysis method and server applied to artificial intelligence | |
| CN110377468A (en) | A kind of test method and relevant apparatus of CPU activation core number setting | |
| CN115437336A (en) | Test method and device for test case, electronic equipment and storage medium | |
| CN109783358A (en) | A kind of software version management method, system and the storage medium of regression test driving | |
| CN104142959A (en) | Automated test device and method based on expert knowledge database | |
| CN105630661A (en) | Automatic cross-system program debugging method and device | |
| US20120054560A1 (en) | Verifying correctness of processor transactions | |
| WO2021036697A1 (en) | Commissioning method and apparatus, device and storage medium | |
| CN110109837B (en) | Integrated test method, integrated test device, controller and medium | |
| CN105320510A (en) | Method and device for automatically tracking data relation | |
| CN117112400A (en) | Automatic test case generation platform | |
| CN110413515A (en) | A kind of bios code walks checking method, system and code walkthrough tool automatically | |
| Dalla | Lean Software Development Practices and Principles in Terms of Observations and Evolution Methods to increase work environment productivity |
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 |