CN109753287A - A kind of method and system of SVN code dual test - Google Patents
A kind of method and system of SVN code dual test Download PDFInfo
- Publication number
- CN109753287A CN109753287A CN201811639893.9A CN201811639893A CN109753287A CN 109753287 A CN109753287 A CN 109753287A CN 201811639893 A CN201811639893 A CN 201811639893A CN 109753287 A CN109753287 A CN 109753287A
- Authority
- CN
- China
- Prior art keywords
- svn
- code
- server
- rule
- checks
- 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
Abstract
The invention discloses a kind of SVN code dual test method and system.The wherein method of inspection, comprising: installation and configuration code checking tool in first server；Continuous integrating platform is built in second server and installs and configure static analysis tools；SVN code is submitted by SVN client；The preconfigured code check tool of SVN server calls carries out rule for the first time to the SVN code before submission and checks；If mistake occurs for code, the submission of SVN code is terminated, and show error message in SVN client；If inspection passes through, SVN code is submitted；Platform calls preconfigured static analysis tools to carry out second of rule to the SVN code after compiling and checks that outgoing inspection is reported simultaneously.By code check tool and static analysis tools, the rule before being submitted for SVN code and after compiling checks the present invention, has standardized written in code rule, has improved code quality, cut operating costs.
Description
Technical field
The present invention relates to code check fields, more particularly, to a kind of method and system of SVN code dual test.
Background technique
Subversion (abbreviation SVN) is the version control system of a mainstream, open source.Subversion allows user
Same group of data is modified and managed in respective space, records data modification situation, and can take this before restoring data to
Version with check the modification details of data.Subversion promotes development teams cooperation, realizes version control management, has strong
It big function and is widely applied.But the code file under SVN system is caused frequently to be submitted since more people compile simultaneously, every time
Submission would be possible to introduce new mistake for code, while it is often difficult to find rule therein is wrong to the code write by user
It misses, even if therefore having done inspection before submission or can will lead to the generation of SVN system comprising the code files upload of a large amount of mistakes
Code library accumulates a large amount of error code file, increases modification difficulty and reduces the safety of code.
Summary of the invention
The purpose of the present invention is to propose to a kind of method and system of SVN code dual test, realize to the dual inspection of svn code
The method looked into realizes the preceding inspection with different code rule after compiling of compiling for different function module, and this method is effectively advised
The model redaction rule of code, has unified code spice, can effectively reduce the reading cost and code error of code；Pass through simultaneously
The code of compiling is checked, safety and the performance issues such as existing sql injection is found in time, improves code quality, reduce
Operation cost.
To achieve the above object, the invention proposes a kind of methods of SVN code dual test, comprising:
It is SVN server and installation and configuration code checking tool in the first server with first server；
Continuous integrating platform is built in the second server connecting with the first server and is installed and is configured quiet
State analysis tool；
SVN code is submitted to the SVN server by SVN client；
During the SVN code is submitted, the preconfigured code check tool pair of SVN server calls
SVN code before submission carries out rule for the first time and checks；
If the code check tool, which checks in the SVN code, occurs mistake, the submission of the SVN code is terminated,
And error message is shown in the SVN client；
If checking in the SVN code and mistake not occurring, the submission of the SVN code is executed and by the SVN code
It is committed to the SVN server；
The continuous integrating platform calls the preconfigured static analysis tools to the SVN generation after compiling submission
Code carries out second of rule and checks outgoing inspection report simultaneously.
Preferably, described to be SVN server with first server and generation is installed and configured in the first server
Code checking tool include:
Different function SVN code module is arranged not in advance by the checkstyle plug-in unit in the code check tool
Same inspection rule, and form the initial survey rule file before submitting.
Preferably, described to be SVN server with first server and generation is installed and configured in the first server
Code checking tool further include:
By the configuration file under svnchecker plug-in unit editor its installation directory in the code check tool, pass through
The path of the examined SVN code of the configuration file association and the initial survey rule file.
Preferably, during the SVN code is submitted, the preconfigured code inspection of SVN server calls
Look into tool includes: to the SVN code progress rule inspection for the first time before submission
The hook file under svn service installation directory is configured in the SVN server, is called by the hook file
The svnchecker plug-in unit simultaneously executes rule inspection for the first time according to the configuration file.
Preferably, described during the SVN code is submitted, the SVN server calls preconfigured generation
Code checking tool carries out rule for the first time to the SVN code before submission and checks further include:
SVN client carries out SVN code and submits operation, and the code check tool carries out the to SVN code before submission
Primary rule checks, does not pass through if checking, error message is shown in the SVN client, passes through if checking, completion mentions
It hands over.
Preferably, described to build continuous integrating platform in the second server connecting with the first server and install
And configuration static analysis tools includes:
The static analysis tools is findbugs, and compiling is submitted in setting in the findbugs static analysis tools
The reinspection that SVN code afterwards is checked is regular and generates reinspection rule file.
Preferably, the institute after the continuous integrating platform calls the preconfigured static analysis tools to submit compiling
It states second of rule inspection of SVN code progress while outgoing inspection is reported and includes:
Code check project is built in the continuous integrating platform, by described in code check project calling
Findbugs static analysis tools simultaneously examines second of rule of code progress after compiling submission according to the reinspection rule file
It looks into, while outgoing inspection is reported.
A kind of SVN code dual test system, comprising: first server, code check tool, continues second server
Integrated platform, static analysis tools, SVN client, the first server are SVN server, and the continuous integrating platform is set
It is placed in second server, the first server is connect with second server；
The code check tool is set in the SVN server, for carrying out for the first time to the SVN code before submission
Rule checks；
The static analysis tools is installed on the continuous integrating platform, carries out for the SVN code after submitting to compiling
Second of rule checks；
The SVN client is used to submit SVN code to the SVN server and shows submission result.
Preferably, the code check tool includes checkstyle and svnchecker plug-in unit, the checkstyle
Plug-in unit is used to formulate the initial survey rule file checked the first time, and the svnchecker plug-in unit is for calling the initial survey to advise
Then file and the first time rule inspection according to initial survey rule file execution to the SVN code before submission.
Preferably, the static analysis tools is findbugs, and the findbugs can be to the SVN generation after compiling submission
Code system rechecks rule surely, after the continuous integrating platform is by calling the findbugs to be submitted according to reinspection rule to compiling
SVN code carries out second of rule and checks simultaneously outgoing inspection report.
The invention has the benefit that the present invention in SVN server by being arranged code check tool and in lasting collection
Static analysis tools is set at platform, different code after submitting before being submitted for SVN code different function module with compiling
Rule inspection, effectively standardized the redaction rule of code, unified code spice, be effectively reduced code reading cost and
Code error, while by checking the code of compiling, there are safety problems and performance issue for discovery in time, improve code
Quality cuts operating costs.
The device of the invention has other characteristics and advantages, these characteristics and advantages from the attached drawing being incorporated herein and with
It will be apparent in specific embodiment afterwards, or will be in the attached drawing and subsequent specific embodiment being incorporated herein
Middle to be stated in detail, the drawings and the detailed description together serve to explain specific principles of the invention.
Detailed description of the invention
Exemplary embodiment of the present is described in more detail in conjunction with the accompanying drawings, of the invention is above-mentioned and other
Purpose, feature and advantage will be apparent, which is characterized in that in exemplary embodiments of the present invention, identical with reference to mark
Number typically represent same parts.
Fig. 1 shows the flow chart of the step of method of SVN code dual test according to the present invention a kind of.
Specific embodiment
The present invention will be described in more detail below with reference to accompanying drawings.Although showing the preferred embodiment of the present invention in attached drawing,
However, it is to be appreciated that may be realized in various forms the present invention and should not be limited by the embodiments set forth herein.On the contrary, providing
These embodiments are of the invention more thorough and complete in order to make, and can will fully convey the scope of the invention to ability
The technical staff in domain.
Fig. 1 shows the flow chart of the step of method of SVN code dual test according to the present invention a kind of.
To achieve the above object, the invention proposes a kind of methods of SVN code dual test, comprising:
Step 1: being SVN server with first server and installation and configuration code check work in first server
Tool；
Step 2: building continuous integrating platform in the second server connecting with first server and install and configure
Static analysis tools；
Step 3: SVN code is submitted to SVN server by SVN client；
Step 4: during SVN code is submitted, before the preconfigured code check tool of SVN server calls is to submission
SVN code carry out for the first time rule check；
Step 5: if code check tool, which checks in SVN code, occurs mistake, terminating the submission of SVN code, and in SVN
Client shows error message；
Step 6: mistake not occurring if checking in SVN code, executes the submission of SVN code and is committed to SVN code
SVN server；
Step 7: the SVN code after continuous integrating platform calls preconfigured static analysis tools to submit compiling carries out
Second of rule checks outgoing inspection report simultaneously.
Specifically, checkstyle and svnchecker is installed on the server, wherein server 1 is svn server,
Build continuous integrating platform on a server 2, findbugs be installed on a server 2, by svnchecker and
Checkstyle plug-in unit is realized to the first time rule inspection of code before submitting, and continuous integrating platform construction code check is passed through
Project and findbugs, which are realized, checks second of rule of the code submitted after compiling, and generates report.
It in one example, is SVN server and installation and configuration code in first server with first server
Checking tool includes:
Different function SVN code module is arranged in advance by the checkstyle plug-in unit in code check tool different
It checks rule, and forms the initial survey rule file before submitting.
Specifically, different with setting is required according to the complexity of code to different function module by checkstyle plug-in unit
Inspection granularity and rule, and form the regular part checkstyle.xml of inspection, be uniformly placed on the regular file directory of inspection
checkstylefile。
It in one example, is SVN server and installation and configuration code in first server with first server
Checking tool further include:
By the configuration file under svnchecker plug-in unit editor its installation directory in code check tool, passes through and configure
The path of the examined SVN code of file association and initial survey rule file.
Specifically, the svncheckconfig.ini file edited under svnchecker installation directory was realized to examined generation
The path of code and file type, the output for checking rule file and inspection result etc. configure, while realizing in this document to difference
Module is configured respectively.
In one example, during SVN code is submitted, the preconfigured code check tool of SVN server calls
Carrying out rule inspection for the first time to the SVN code before submission includes:
The hook file under svn service installation directory is configured in SVN server, is called by hook file
Svnchecker plug-in unit simultaneously executes rule inspection for the first time according to configuration file.
Specifically, pre-commit (hook) file under configuration svn service installation directory, is called by this document
The association that svn code library and checkstyle are checked is realized in svnchecker application.
In one example, during SVN code is submitted, the preconfigured code check tool of SVN server calls
Rule for the first time is carried out to the SVN code before submission to check further include:
SVN client carries out SVN code and submits operation, and code checking tool carries out for the first time SVN code before submission
Rule checks, does not pass through if checking, error message is shown in SVN client, passes through if checking, completes to submit.
Specifically, submission code is carried out by the commit operation of svn client, is first carried out before submitting completion
The code regulation inspection of checkstyle, if not meeting inspection rule, inspection result will appear in svn client
In console (console), if meeting rule, complete to submit.
In one example, built in the second server being connect with first server continuous integrating platform and install with
And configuration static analysis tools includes:
Static analysis tools is findbugs, and the SVN after submitting to compiling is arranged in findbugs static analysis tools
The reinspection that code is checked is regular and generates reinspection rule file.
Specifically, it is realized by the findbugs_include_filter.xml file of findbugs to examined code
Rule configuration.
In one example, the SVN after continuous integrating platform calls preconfigured static analysis tools to submit compiling
Code carries out second of rule and checks that outgoing inspection report simultaneously includes:
Code check project is built in continuous integrating platform, and findbugs static analysis is called by code check project
Tool simultaneously checks second of rule of code progress after compiling submission according to reinspection rule file, while outgoing inspection report.
Specifically, it in the project of continuous integrating platform building code check, is called by build.xml file
Findbugs_include_filter.xml is realized to the code check after compiling, while realizing the output of audit report.
A kind of SVN code dual test system, comprising: first server, code check tool, continues second server
Integrated platform, static analysis tools, SVN client, first server are SVN server, and continuous integrating platform is set to second
In server, first server is connect with second server；
Code check tool is set in SVN server, is examined for carrying out rule for the first time to the SVN code before submission
It looks into；
Static analysis tools is installed on continuous integrating platform, carries out second for the SVN code after submitting to compiling and advises
Then check；
SVN client is used to submit SVN code to SVN server and shows submission result.
In one example, code check tool includes checkstyle and svnchecker plug-in unit, and checkstyle is inserted
Part is used to formulate the initial survey rule file checked for the first time, and svnchecker plug-in unit is for calling initial survey rule file and according to first
Examine first time rule inspection of the rule file execution to the SVN code before submission.
In one example, static analysis tools findbugs, findbugs can be to the SVN codes after compiling submission
Formulate reinspection rule, continuous integrating platform by call findbugs according to reinspection rule to compiling submit after SVN code into
Second of rule of row checks and outgoing inspection report.
Embodiment:
A kind of SVN code dual test system, comprising: Linux server 1, linux server 2, code check tool
Checkstyle and svnchecker, jenkins continuous integrating platform, static analysis tools, SVN client, Linux server
1 connect with linux server 2, and wherein Linux server 1 is SVN server, and jenkins continuous integrating platform is set to second
In server；Code check tool checkstyle and svnchecker are set to SVN server for the SVN generation before submission
Code carries out rule for the first time and checks；Static analysis tools findbugs is installed on jenkins continuous integrating platform, for compiling
SVN code after submission carries out second of rule and checks；SVN client is used to submit SVN code to SVN server and show to mention
Knot fruit.Wherein checkstyle plug-in unit is used to formulate the initial survey rule file checked for the first time, and svnchecker plug-in unit is used for
It calls initial survey rule file and the first time rule inspection to the SVN code before submission is executed according to initial survey rule file.It is static
SVN code after analysis tool findbugs can submit compiling formulates reinspection rule, and jenkins continuous integrating platform passes through
It calls findbugs to carry out second of rule to the SVN code after compiling submission according to reinspection rule and checks simultaneously outgoing inspection report
It accuses.
A kind of method of SVN code dual test, comprising:
Step 1: checkstyle and svnchecker being installed in Linux server 1, wherein Linux server 1 is
Svn server, the inspection granularity and rule different with setting is required according to the complexity of code to different function module, and formed
It checks rule file checkstyle.xml, is uniformly placed on the regular file directory checkstylefile of inspection, editor
Svncheckconfig.ini file under svnchecker installation directory realize to the path of examined code and file type,
It checks the configuration such as output of rule file and inspection result, while disparate modules is configured respectively in this document realization；
Realize that code is as follows:
[model1]
Main.Regex=^.../model1/.* $
Checkstyle.Java=.../jdk1.6.0_20/bin/java
Checkstyle.Classpath=.../checkstyle-5.6-all.jar
Checkstyle.ConfigFile=.../checkstylemodel1.xml
Checkstyle.FailureHandlers=Console
[model2]
Main.Regex=^.../model2/.* $
Checkstyle.Java=.../jdk1.6.0_20/bin/java
Checkstyle.Classpath=.../checkstyle-5.6-all.jar
Checkstyle.ConfigFile=.../checkstylemodel2.xml
Checkstyle.FailureHandlers=Console
Step 2: building jenkins continuous integrating platform on linux server 2, installed on linux server 2 quiet
The findbugs_include_filter.xml file of state analysis tool findbugs, findbugs are realized to examined code
Rule configuration；
Step 3: submission code is carried out by the commit operation of svn client；
Step 4: the pre-commit file being pre-configured under svn service installation directory is called by this document
The association that svn code library and checkstyle are checked is realized in svnchecker application；
Step 5: the code regulation inspection of checkstyle is first carried out before submitting completion, if not meeting check gauge
Then, inspection result will appear in the end console console of SVN client；
Step 6: if meeting rule, SVN code being committed to SVN server；
Step 7: in the project of jenkins continuous integrating platform building code check, being called by build.xml file
Findbugs_include_filter.xml is realized to the code check after compiling, while realizing the output of audit report.
Various embodiments of the present invention are described above, above description is exemplary, and non-exclusive, and
It is not limited to disclosed each embodiment.Without departing from the scope and spirit of illustrated each embodiment, for this skill
Many modifications and changes are obvious for the those of ordinary skill in art field.
Claims (10)
1. a kind of method of SVN code dual test characterized by comprising
It is SVN server and installation and configuration code checking tool in the first server with first server；
Continuous integrating platform is built in the second server connecting with the first server and installs and configure static point
Analysis tool；
SVN code is submitted to the SVN server by SVN client；
During the SVN code is submitted, the preconfigured code check tool of SVN server calls is to submission
Preceding SVN code carries out rule for the first time and checks；
If the code check tool, which checks in the SVN code, occurs mistake, the submission of the SVN code is terminated, and
The SVN client shows error message；
If checking in the SVN code and mistake not occurring, executes the submission of the SVN code and submit the SVN code
To the SVN server；
The continuous integrating platform call the preconfigured static analysis tools to compiling submit after the SVN code into
Second of rule of row checks outgoing inspection report simultaneously.
2. the method for SVN code dual test according to claim 1, which is characterized in that described to be with first server
SVN server and in the first server installation and configuration code checking tool include:
Different function SVN code module is arranged in advance by the checkstyle plug-in unit in the code check tool different
It checks rule, and forms the initial survey rule file before submitting.
3. the method for SVN code dual test according to claim 2, which is characterized in that described to be with first server
SVN server and installation and configuration code checking tool in the first server further include:
By the configuration file under svnchecker plug-in unit editor its installation directory in the code check tool, by described
The path of the examined SVN code of configuration file association and the initial survey rule file.
4. the method for SVN code dual test according to claim 3, which is characterized in that submitted in the SVN code
Cheng Zhong, the preconfigured code check tool of SVN server calls carry out first time rule to the SVN code before submission
It then checks and includes:
The hook file under svn service installation directory is configured in the SVN server, by described in hook file calling
Svnchecker plug-in unit simultaneously executes rule inspection for the first time according to the configuration file.
5. the method for SVN code dual test according to claim 4, which is characterized in that described to be mentioned in the SVN code
During friendship, the preconfigured code check tool of SVN server calls carries out first to the SVN code before submission
Secondary rule checks further include:
SVN client carries out SVN code and submits operation, and the code check tool carries out for the first time SVN code before submission
Rule checks, does not pass through if checking, error message is shown in the SVN client, passes through if checking, completes to submit.
6. the method for SVN code dual test according to claim 1, which is characterized in that described to be taken with described first
Continuous integrating platform, which is built, in the second server of business device connection and installs and configure static analysis tools includes:
The static analysis tools is findbugs, after compiling is submitted in setting in the findbugs static analysis tools
The reinspection that SVN code is checked is regular and generates reinspection rule file.
7. the method for SVN code dual test according to claim 6, which is characterized in that the continuous integrating platform tune
It is defeated simultaneously that the SVN code after being submitted with the preconfigured static analysis tools to compiling carries out second of rule inspection
Audit report includes: out
Code check project is built in the continuous integrating platform, the findbugs is called by the code check project
Simultaneously according to the reinspection rule file, to the code progress after compiling submission, rule checks static analysis tools for the second time, while defeated
Audit report out.
8. a kind of SVN code dual test system characterized by comprising first server, second server, code check
Tool, continuous integrating platform, static analysis tools, SVN client, the first server are SVN server, the lasting collection
It is set in second server at platform, the first server is connect with second server；
The code check tool is set in the SVN server, for carrying out rule for the first time to the SVN code before submission
It checks；
The static analysis tools is installed on the continuous integrating platform, carries out second for the SVN code after submitting to compiling
Secondary rule checks；
The SVN client is used to submit SVN code to the SVN server and shows submission result.
9. SVN code dual test system according to claim 8, which is characterized in that the code check tool includes
Checkstyle and svnchecker plug-in unit, the checkstyle plug-in unit are used to formulate the initial survey rule checked the first time
File, the svnchecker plug-in unit is for calling the initial survey rule file and being executed according to the initial survey rule file to mentioning
The first time rule inspection of SVN code before friendship.
10. SVN code dual test system according to claim 8, which is characterized in that the static analysis tools is
SVN code after findbugs, the findbugs can submit compiling formulates reinspection rule, and the continuous integrating platform is logical
The SVN code crossed after calling the findbugs to be submitted according to reinspection rule to compiling carries out second of rule and checks and export inspection
Look into report.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811639893.9A CN109753287A (en) | 2018-12-29 | 2018-12-29 | A kind of method and system of SVN code dual test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811639893.9A CN109753287A (en) | 2018-12-29 | 2018-12-29 | A kind of method and system of SVN code dual test |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109753287A true CN109753287A (en) | 2019-05-14 |
Family
ID=66404426
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811639893.9A Pending CN109753287A (en) | 2018-12-29 | 2018-12-29 | A kind of method and system of SVN code dual test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109753287A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112631894A (en) * | 2020-12-02 | 2021-04-09 | 北京健康之家科技有限公司 | Code detection method, device, storage medium and computer equipment |
| CN113553253A (en) * | 2020-04-24 | 2021-10-26 | 烽火通信科技股份有限公司 | Method and system for circle complexity check by combining with SVN |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103309804A (en) * | 2013-04-08 | 2013-09-18 | 中国电子科技集团公司第十研究所 | Automatic code rule checking platform |
| CN106095681A (en) * | 2016-06-14 | 2016-11-09 | 深圳市彬讯科技有限公司 | A kind of SVN integrated JSHint code detection method and system thereof |
| US20170262260A1 (en) * | 2016-03-09 | 2017-09-14 | Bank Of America Corporation | SVN Interface System for Heterogeneous Development Environments |
| CN107741908A (en) * | 2017-10-12 | 2018-02-27 | 郑州云海信息技术有限公司 | A kind of continuous integrating method and device based on automatic test |
-
2018
- 2018-12-29 CN CN201811639893.9A patent/CN109753287A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103309804A (en) * | 2013-04-08 | 2013-09-18 | 中国电子科技集团公司第十研究所 | Automatic code rule checking platform |
| US20170262260A1 (en) * | 2016-03-09 | 2017-09-14 | Bank Of America Corporation | SVN Interface System for Heterogeneous Development Environments |
| CN106095681A (en) * | 2016-06-14 | 2016-11-09 | 深圳市彬讯科技有限公司 | A kind of SVN integrated JSHint code detection method and system thereof |
| CN107741908A (en) * | 2017-10-12 | 2018-02-27 | 郑州云海信息技术有限公司 | A kind of continuous integrating method and device based on automatic test |
Non-Patent Citations (2)
| Title |
|---|
| WEIXIN_33670713: "《在SVN上实现代码风格自动检查》", 《 HTTPS://BLOG.CSDN.NET/WEIXIN_33670713/ARTICLE/DETAILS/86183308?UTM_SOURCE=APP&APP_VERSION=4.6.1》 * |
| 陈如水: "《FindBugs代码检查工具的使用》", 《HTTPS://BLOG.CSDN.NET/CHENRUSHUI/ARTICLE/DETAILS/51891813》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113553253A (en) * | 2020-04-24 | 2021-10-26 | 烽火通信科技股份有限公司 | Method and system for circle complexity check by combining with SVN |
| CN112631894A (en) * | 2020-12-02 | 2021-04-09 | 北京健康之家科技有限公司 | Code detection method, device, storage medium and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3769223B1 (en) | Unified test automation system | |
| US8005803B2 (en) | Best practices analyzer | |
| US20140006459A1 (en) | Rule-based automated test data generation | |
| US20150113510A1 (en) | Method and System for Automated Testing of Computer Applications | |
| US20120159421A1 (en) | System and Method for Exclusion of Inconsistent Objects from Lifecycle Management Processes | |
| US8762989B2 (en) | Application runtime expert for deployment of an application on multiple computer systems | |
| WO2014210177A1 (en) | Prioritization of tests of computer program code | |
| US20210191845A1 (en) | Unit testing of components of dataflow graphs | |
| KR101579493B1 (en) | Staging control method for source code, Computer program for the same, Recording medium storing computer program for the same | |
| US8302087B2 (en) | Quality assurance in software systems through autonomic reliability, availability and serviceability code generation | |
| Fisher et al. | Utilizing Atlassian JIRA for large-scale software development management | |
| CN113434158B (en) | Custom management method, device, equipment and medium for big data component | |
| Harrer et al. | Open source versus proprietary software in service-orientation: the case of BPEL engines | |
| CN109753287A (en) | A kind of method and system of SVN code dual test | |
| CN114327588A (en) | Method and device for processing code submission log | |
| Jezek et al. | Supplying compiler's static compatibility checks by the analysis of third-party libraries | |
| Li et al. | Tool support for secure programming by security testing | |
| US8316444B2 (en) | Third-party software product certification | |
| Carey et al. | A toolkit for event analysis and logging | |
| Schuster et al. | A Log-Tool Suite for Embedded Systems | |
| CN117850749A (en) | Service logic architecture splitting method based on FilterPipeline | |
| CN117194104A (en) | Disaster recovery switching processing method and device applied to multiple systems | |
| Antunes et al. | Software Assurance Guidance and Evaluation (SAGE) Tool | |
| CN116909928A (en) | Test case generation method, interface test method, system, equipment and medium | |
| CN116560715A (en) | Database version control method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190514 |
|
| RJ01 | Rejection of invention patent application after publication |