[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN102880546A - Software integration testing method and system based on extensible markup language (XML) database - Google Patents

Software integration testing method and system based on extensible markup language (XML) database Download PDF

Info

Publication number
CN102880546A
CN102880546A CN2012103217694A CN201210321769A CN102880546A CN 102880546 A CN102880546 A CN 102880546A CN 2012103217694 A CN2012103217694 A CN 2012103217694A CN 201210321769 A CN201210321769 A CN 201210321769A CN 102880546 A CN102880546 A CN 102880546A
Authority
CN
China
Prior art keywords
test
code
information
log
server
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
Application number
CN2012103217694A
Other languages
Chinese (zh)
Other versions
CN102880546B (en
Inventor
罗正海
赵伟
郑程光
赖铮
孙伟丰
李泉
李�浩
李书淦
程仁波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) CO LTD
Founder Information Industry Holdings Co Ltd
Peking University Founder Group Co Ltd
Original Assignee
FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) CO LTD
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) CO LTD filed Critical FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) CO LTD
Priority to CN201210321769.4A priority Critical patent/CN102880546B/en
Publication of CN102880546A publication Critical patent/CN102880546A/en
Application granted granted Critical
Publication of CN102880546B publication Critical patent/CN102880546B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Debugging And Monitoring (AREA)

Abstract

The invention provides a software integration testing method and a software integration testing system based on an extensible markup language (XML) database. An operation interface for extending a test case, a distributed load equalizer based on a minimum heap and Hash algorithm and code automatic compilation, analysis and submission functions are provided. A tester only needs to upload a compiled test case to a code memory, the operation interface which is provided by an integrated testing server of a testing tool is used for configuration, and new test case addition and continuous integration functions can be realized. Under the condition of addition or reduction of test resources, by dynamically constructing minimum heap and Hash, the distributed load equalizer can automatically meet requirements of new environment. By adoption of the code automatic compilation, analysis and submission functions, the submission quality of user codes is improved. Continuous integration in software is realized, the accuracy of code submission is improved, and the regression efficiency of test is improved. Moreover, by adoption of a distributed design idea, the problems about resource bottleneck of a testing machine and platform automatic selection are solved, and the utilization rate of resources is improved.

Description

Software integration test method and system based on XML database
Technical Field
The invention relates to the technical field of computers, in particular to a software integration test system based on an XML database.
Background
The integration test is a logical extension of the unit test. It is in its simplest form: two tested units are combined into one component, and the interface between the two components is tested. In this layer sense, a component refers to an integrated aggregation of multiple units. In a real-world scenario, many units are combined into components, which are in turn aggregated into a larger portion of the program. The method is to test the combination of fragments and finally expand into a process, testing the module together with other groups of modules. Finally, all modules that make up the process are tested together. Furthermore, if a program consists of multiple processes, they should be tested in pairs, rather than testing all processes simultaneously.
Software integration test is an important process and method for guaranteeing software quality, the existing software integration test tools mainly aim at application software products, a test tool aiming at large-scale basic system software such as an XML database does not exist, and the existing tools do not have continuous integration capability, code compiling and analyzing capability and distributed load capability lacking expansibility and strong adaptability.
Disclosure of Invention
In order to solve the above problems, the software integration test system based on the XML database according to the present invention includes:
step S10: the integrated test server receives a request of a user, compiles and analyzes the code and generates a code analysis log;
step S20: calling unit tests or script test cases in sequence to perform test operation by using a test configuration file generated by a test case application interface, and generating a test log after the test operation;
step S30: analyzing whether the code is tested sufficiently according to the code test operation result and the code analysis log, and submitting the code to a code memory when the code is tested sufficiently;
step S40: centralized version control management is performed on code submitted thereto.
Optionally, the method further comprises:
the distributed load balancer receives the operation information transmitted by the integrated test server, and agent executors are selected by adopting a minimum heap and HASH algorithm;
and the selected agent executor compiles and runs the test case according to the configuration information transmitted by the distributed load balancing integrated test server, and returns the test execution result to the integrated test server.
Optionally, the selecting a corresponding agent executor according to the operation information sent by the integrated test server specifically includes:
step S110: constructing a dynamic hash table by using the IP address of each agent executor;
step S120: calculating the CPU utilization rate and the memory utilization rate of each agent executor through the hash table;
step S130: calculating the final resource utilization rate of each agent executor by using a weighted average method for the CPU utilization rate and the memory utilization rate of each agent executor;
step S140: constructing a minimum heap according to the final resource utilization rate of each agent executor;
step S150: and the distributed balanced integration test server selects the agent executor with the minimum load by removing the heap top element of the minimum heap, and reconstructs the minimum heap by using a heap algorithm while taking out the heap top element.
Optionally, further comprising:
during code analysis, original codes in a code memory are called through the svn blank function, and are compared with codes submitted to an integrated test server by a user for analysis, an updating path of the codes is found out, and the updating path is recorded into an integrated log;
when the codes are compiled, the compiler can generate corresponding symbol files, trace information is written into the symbol files during test running, so that code coverage paths are recorded, and finally whether the codes are tested fully or not is analyzed by comparing the updating paths with the test coverage paths.
Optionally, further comprising:
when the codes are compiled by using vs or gcc, corresponding compiling information can be generated by setting compiling parameters and warning levels, statements containing 'memory leak' in the information are filtered by analyzing the warning information in the compiling log, the statements can be recorded in the memory leak information log, the location of the memory leak codes can be recorded in the log in detail, and a code analysis log can be generated after the code analysis.
Optionally, the code submission further includes:
whether the code is submitted is determined by analyzing the test operation result and the code analysis log, if the test is completely passed and no code information with memory leakage and irregularity exists in the code log analysis, an update path in the code analysis is called by the svncommit code submitting function to submit the changed code to a code repository, otherwise, the code is not submitted.
Optionally, the test run further comprises:
using a configuration file generated by a test case application interface, calling unit tests or script test cases in sequence, writing test statistical information of each test case into a test log during execution, and counting passed test cases and failed test cases when the test is finished;
wherein, the information triplet includes: case-group-id: the group number represents the test information; case-id: representing a test case number; success/failed: indicating whether the test case passes or not; during test execution, each test case forms a triple format information.
The invention also provides a software integration test system based on the XML database, which comprises the following components:
the client is respectively used for receiving an integrated test configuration request of a user and sending the integrated test configuration request to the integrated test server;
an integrated test server, comprising:
the code compiling and analyzing module is used for compiling and analyzing the codes and generating a code analyzing log;
the test operation module is used for calling unit tests or script test cases in sequence to perform test operation through a test configuration file generated by using the test case application interface and generating a test log after the test operation is finished;
the code submitting module analyzes whether the code is tested sufficiently or not by analyzing the code test operation result and the code analysis log, and submits the code to the code memory when the code is tested sufficiently;
and the code storage is used for carrying out centralized version control management on the codes submitted by the integrated test server.
Optionally, the method further comprises:
the distributed load balancing integrated test server is respectively connected with the integrated test server and the agent executors and is used for selecting the corresponding agent executors according to the operation information sent by the integrated test server and returning the results of the agent executors after execution to the integrated test server;
and the selected agent executor is used for performing test execution according to the operation configuration file transmitted by the distributed load balancing integration test server and returning a test execution result to the integration test server through the distributed load balancing integration test server.
Optionally, the client receives an operation request including an integrated test server address configured by a user, a login account, a project to be executed, and a code analysis and submission option, and sends the operation request to the integrated test server.
Optionally, the code compiling and analyzing module further includes:
the code analysis module is used for calling the original code in the code memory and the code submitted to the integrated test server by a software developer to carry out comparison analysis, finding out an updating path of the code, recording a covering path of the code during test operation, and finally analyzing whether the code is tested fully or not by comparing the updating path with the testing covering path;
the code compiling module is used for compiling the code, generating corresponding compiling information by setting compiling parameters and warning levels, filtering the statement containing the 'memoryleaks' in the information by analyzing the warning information in the compiling log, and recording the statement containing the 'memory leak' into a memory leak information log.
Optionally, the integrated test server further includes a statistics module, where the statistics module is configured to count a change rate and a test passing rate of the code, and return a statistics result to the client for display.
Optionally, the integrated test server further includes a test trigger module, where the test trigger module is configured to set test operation of the trigger code according to the time and code change of the client.
Optionally, the recording of the coverage path of the code by the code analysis module during the test run is specifically that, during the code compilation, the compiler generates a corresponding symbol file, and the code coverage path is recorded by writing trace information into the symbol file during the test run.
Optionally, the memory leak information log records the location of the memory leak code, so that a developer can modify the code.
Optionally, the test log includes an information triple, and when the test operation is finished, the test case that the test passes and the test case that the test fails are counted by analyzing the information triple.
Optionally, the information triplet includes:
case-group-id: the group number represents the test information;
case-id: representing a test case number;
success/failed: compared with the prior art, the technical scheme has the following advantages that whether the test case passes or not is shown:
the technical scheme of the invention aims at the problems in the prior art and provides a software integration test system based on an XML database, which provides the following steps: the operation interface of the test case is expanded, and a tester only needs to upload the programmed test case to a code memory and configure the test case through the operation interface provided by the integrated test server end of the test tool to complete the functions of adding and continuously integrating the new test case; the distributed load balancer based on the minimum heap and the Hash algorithm can automatically adapt to the requirements under a new environment by dynamically constructing the minimum heap and the Hash under the condition that test resources are added or reduced; the automatic compiling, analyzing and submitting functions of the codes improve the quality of code submission of users. Continuous integration in software is realized, and meanwhile, the accuracy of code submission and the regression efficiency of testing are improved. In addition, the invention adopts a distributed design idea, thereby shielding the resource bottleneck problem of the tester and the automatic platform selection problem and improving the utilization rate of resources.
Drawings
FIG. 1 is a flow chart of a method for testing software integration based on XML database according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for selecting a corresponding agent executor according to operation information sent by the integrated test server in the XML database-based software integrated test method according to the embodiment of the present invention;
FIG. 3 is a framework diagram of an XML database based software integration test system according to an embodiment of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below. In the following description, specific details are set forth in order to provide a thorough understanding of the present invention. The invention can be implemented in a number of ways different from those described herein and similar generalizations can be made by those skilled in the art without departing from the spirit of the invention. Therefore, the present invention is not limited to the specific embodiments disclosed below.
The technical personnel in the field know that software integration test is an important process and method for guaranteeing software quality, the existing software integration test tools mainly aim at application software products, a test tool aiming at large-scale basic system software such as an XML database does not exist, and the existing tools do not have the defects of continuous integration capability, code compiling and analyzing capability, lack of expansibility, strong adaptability, distributed load capability and the like.
In order to solve the problems in the prior art, the inventor of the invention provides a software integration testing method based on an XML database through research. Referring to fig. 1, fig. 1 is a flowchart of a software integration testing method based on an XML database according to an embodiment of the present invention. The software integration test method based on the XML database comprises the following steps:
step S10: the integrated test server receives a request of a user, compiles and analyzes the code and generates a code analysis log;
during code analysis, original codes in a code memory are called through the svn blank function and are compared with codes submitted to an integrated test server by a user for analysis, an updating path of the codes is found out and is recorded in an integrated log;
when the codes are compiled, the compiler can generate corresponding symbol files, trace information is written into the symbol files during test running, so that code coverage paths are recorded, and finally whether the codes are tested fully or not is analyzed by comparing the updating paths with the test coverage paths.
Wherein, still further include in this step: when the codes are compiled by using vs or gcc, corresponding compiling information can be generated by setting compiling parameters and warning levels, statements containing 'memory leak' in the information are filtered by analyzing the warning information in the compiling log, the statements can be recorded in the memory leak information log, the location of the memory leak codes can be recorded in the log in detail, and a code analysis log can be generated after the code analysis.
Step S20: calling unit tests or script test cases in sequence to perform test operation by using a test configuration file generated by a test case application interface, and generating a test log after the test operation;
step S30: analyzing whether the code is tested sufficiently according to the code test operation result and the code analysis log, and submitting the code to a code memory when the code is tested sufficiently;
wherein, in this step, still further include:
the distributed load balancer receives the operation information transmitted by the integrated test server, and agent executors are selected by adopting a minimum heap and HASH algorithm;
and the selected agent executor compiles and runs the test case according to the configuration information transmitted by the distributed load balancing integrated test server, and returns the test execution result to the integrated test server.
The selecting of the corresponding agent executor according to the operation information sent by the integrated test server specifically comprises:
step S110: constructing a dynamic hash table by using the IP address of each agent executor;
step S120: calculating the CPU utilization rate and the memory utilization rate of each agent executor through the hash table;
step S130: calculating the final resource utilization rate of each agent executor by using a weighted average method for the CPU utilization rate and the memory utilization rate of each agent executor;
step S140: constructing a minimum heap according to the final resource utilization rate of each agent executor;
step S150: and the distributed balanced integration test server selects the agent executor with the minimum load by removing the heap top element of the minimum heap, and reconstructs the minimum heap by using a heap algorithm while taking out the heap top element.
Optionally, the code submission further includes:
whether the code is submitted is determined by analyzing the test operation result and the code analysis log, if the test is completely passed and no code information with memory leakage and irregularity exists in the code log analysis, an update path in the code analysis is called by the svncommit code submitting function to submit the changed code to a code repository, otherwise, the code is not submitted.
Optionally, the test run further comprises:
using a configuration file generated by a test case application interface, calling unit tests or script test cases in sequence, writing test statistical information of each test case into a test log during execution, and counting passed test cases and failed test cases when the test is finished;
wherein, the information triplet includes: case-group-id: the group number represents the test information; case-id: representing a test case number; success/failed: indicating whether the test case passes or not; during test execution, each test case forms a triple format information
Step S40: the code store performs centralized version control management of code submitted thereto.
Referring to fig. 3, the present invention further provides an integrated test system based on an XML database, including:
the system comprises a client 1, a test server and a test data processing system, wherein the client 1 is respectively used for receiving a request of a user and sending the request to an integrated test server; the client 1 comprises a VC client 11 and an eclipse client 12, which are convenient for users to use. In the client, the user can operate by only configuring the address of the integrated test server, logging in an account and selecting a project to be executed and code analysis and submission options. After receiving the configuration of the client 1, the integration test server 2 sets corresponding operations, and after the execution is finished, sends corresponding results to the client 1.
The integrated test server 2 is used for carrying out corresponding integrated test operation according to the integrated test request sent by the client and returning the operation result to the client for displaying;
wherein, the integrated test server 2 further comprises:
a code compiling and analyzing module 21, configured to compile and analyze a code and generate a code analysis log; wherein, the code compiling and analyzing module 21 further includes: the code analysis module 21a is used for finding out an updating path of the code by calling the original code in the code memory and performing comparative analysis on the code submitted to the integrated test server, and recording the updating path of the code into an integrated log; writing tracking information into a corresponding symbol file generated by a compiler when the code is compiled in a test operation so as to record a code coverage path, finally analyzing whether the code is tested to fully record the code coverage path or not by comparing an update path with a test coverage path, and finally analyzing whether the code is tested to fully by comparing the update path with the test coverage path; the code compiling module 21b is configured to generate corresponding compiling information by setting a compiling parameter and an alarm level when compiling the code using vs or gcc, filter statements containing "memory leaves" in the information by analyzing the warning information in the compiling log, and record the statements containing "memory leaks" in a memory leak information log.
The code submitting module 22 is used for analyzing whether the code is tested sufficiently according to the code test operation result and the code analysis log, and submitting the code to the code storage when the code is tested sufficiently;
the test operation module 23 is configured to call the unit test or the script test case in sequence to perform test operation by using the test configuration file generated by the test case application interface, and generate a test log after the test operation; during test operation, an information triple including a group number where test information is located, a test case number and information indicating whether the test case passes or not is written into the test log, and when the test is finished, the passing test case and the failing test case can be counted through the information triple. Wherein,
for example,
testing a configuration file:
xqts test (: Note test group:)
xqts-1(: Note test case)
xqts-2
update test
fulltext test
Test logs generated after running:
<1,1,sucess>
<2,1,failed>
<3,1,sucess>
the statistical module 24 is used for counting the change rate and the test passing rate of the codes and returning the statistical result to the client for displaying; wherein the code change rate: dividing the number of lines of submitted codes by the number of lines of total codes by calculating the number of lines of submitted codes; test pass rate: the number of success in the triple information in the test log is divided by the total number of test cases. The information of the statistical module is transmitted to the client 1 for display after the test is finished.
The test triggering module 25 is used for triggering test operation of the code according to the time and the code change setting of the client; the module is mainly used for regression and verification of test cases, and is mainly triggered to run through time and code change settings, for example: setting the time to be 8:00am, changing the code to be true, and otherwise, triggering operation is executed only when the code is changed, or else, not executed. The provision of the test departure module 25 improves the efficiency of the trigger operation while avoiding the misoperation of manual code submission.
The distributed load balancing integrated test server 3 is used for selecting a corresponding agent executor according to the operation information sent by the integrated test server;
the agent executor 4 is respectively used for downloading codes from a code memory according to the operation information transmitted by the distributed balanced load integrated test server for compiling and testing, and transmitting an execution result to the integrated test server through a network;
a code store 5 for centralized version control management of the code submitted thereto. The code memory is used for the version control function of the code, and mainly utilizes the existing tools such as svn.
In summary, the technical scheme of the invention has the following advantages:
the technical scheme of the invention aims at the problems in the prior art and provides a software integration test system based on an XML database, which provides the following steps: the operation interface of the test case is expanded, and a tester only needs to upload the programmed test case to a code memory and configure the test case through the operation interface provided by the integrated test server end of the test tool to complete the functions of adding and continuously integrating the new test case; the distributed load balancer based on the minimum heap and the Hash algorithm can automatically adapt to the requirements under a new environment by dynamically constructing the minimum heap and the Hash under the condition that test resources are added or reduced; the automatic compiling, analyzing and submitting functions of the codes improve the quality of code submission of users. Continuous integration in software is realized, and meanwhile, the accuracy of code submission and the regression efficiency of testing are improved. In addition, the invention adopts a distributed design idea, thereby shielding the resource bottleneck problem of the tester and the automatic platform selection problem and improving the utilization rate of resources.
It is to be understood that the methods and systems described herein may be implemented in various forms of hardware, software, firmware, special purpose processors, or a combination thereof. In particular, at least a portion of the present invention is preferably implemented as an application program including program instructions. These program instructions are tangibly embodied in one or more program storage devices (including, but not limited to, hard disks, magnetic floppy disks, RAM, ROM, CD, ROM, etc.) and executable by any device or machine comprising suitable architecture, such as a general purpose digital computer having a processor, memory, and input/output interfaces. It is to be further understood that, because some of the constituent system components and process steps depicted in the accompanying figures are preferably implemented in software, the connections between system modules (or the logic flow of method steps) may differ depending upon the manner in which the present invention is programmed. Given the teachings herein, one of ordinary skill in the related art will be able to contemplate these and similar implementations of the present invention.
While various aspects and embodiments of the invention are disclosed above, other aspects and embodiments of the invention will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are presented by way of example only, and not by way of limitation, such that the true scope and spirit of the invention is indicated by the following claims.

Claims (17)

1. A software integration test method based on an XML database is characterized by comprising the following steps:
step S10: the integrated test server receives a request of a user, compiles and analyzes the code and generates a code analysis log;
step S20: calling unit tests or script test cases in sequence to perform test operation by using a test configuration file generated by a test case application interface, and generating a test log after the test operation;
step S30: analyzing whether the code is tested sufficiently according to the code test operation result and the code analysis log, and submitting the code to a code memory when the code is tested sufficiently;
step S40: centralized version control management is performed on code submitted thereto.
2. The XML database-based software integration test method of claim 1, further comprising:
the distributed load balancer receives the operation information transmitted by the integrated test server, and agent executors are selected by adopting a minimum heap and HASH algorithm;
and the selected agent executor compiles and runs the test case according to the configuration information transmitted by the distributed load balancing integrated test server, and returns the test execution result to the integrated test server.
3. The XML-database-based software integration test method according to claim 2, wherein the selecting a corresponding agent executor according to the operation information sent by the integration test server specifically comprises:
step S110: constructing a dynamic hash table by using the IP address of each agent executor;
step S120: calculating the CPU utilization rate and the memory utilization rate of each agent executor through the hash table;
step S130: calculating the final resource utilization rate of each agent executor by using a weighted average method for the CPU utilization rate and the memory utilization rate of each agent executor;
step S140: constructing a minimum heap according to the final resource utilization rate of each agent executor;
step S150: and the distributed balanced integration test server selects the agent executor with the minimum load by removing the heap top element of the minimum heap, and reconstructs the minimum heap by using a heap algorithm while taking out the heap top element.
4. The XML database-based software integration test method of claim 1, further comprising:
during code analysis, original codes in a code memory are called through the svn blank function, and are compared with codes submitted to an integrated test server by a user for analysis, an updating path of the codes is found out, and the updating path is recorded into an integrated log;
when the codes are compiled, the compiler can generate corresponding symbol files, trace information is written into the symbol files during test running, so that code coverage paths are recorded, and finally whether the codes are tested fully or not is analyzed by comparing the updating paths with the test coverage paths.
5. The XML database-based software integration test method of claim 1, wherein the code compilation further comprises:
when the codes are compiled by using vs or gcc, corresponding compiling information can be generated by setting compiling parameters and warning levels, statements containing 'memory leak' in the information are filtered by analyzing the warning information in the compiling log, the statements can be recorded in the memory leak information log, the location of the memory leak codes can be recorded in the log in detail, and a code analysis log can be generated after the code analysis.
6. The XML database-based software integration test method of claim 1, wherein the code submission further comprises:
whether the code is submitted is determined by analyzing the test operation result and the code analysis log, if the test is completely passed and no code information with memory leakage and irregularity exists in the code log analysis, the svncommit code submitting function calls an updating path in the code analysis to submit the changed code to a code repository, otherwise, the code is not submitted.
7. The XML database-based software integration test method of claim 1, wherein the test run further comprises:
using a configuration file generated by a test case application interface, calling unit tests or script test cases in sequence, writing test statistical information of each test case into a test log during execution, and counting passed test cases and failed test cases when the test is finished;
wherein, the information triplet includes:
case-group-id: the group number represents the test information;
case-id: representing a test case number;
success/failed: indicating whether the test case passes or not;
during test execution, each test case forms a triple format information.
8. A software integration test system based on XML database, characterized by comprising:
the client is respectively used for receiving an integrated test configuration request of a user and sending the integrated test configuration request to the integrated test server;
an integrated test server, comprising:
the code compiling and analyzing module is used for compiling and analyzing the codes and generating a code analyzing log;
the test operation module is used for calling unit tests or script test cases in sequence to perform test operation through a test configuration file generated by using the test case application interface and generating a test log after the test operation is finished;
the code submitting module analyzes whether the code is tested sufficiently or not by analyzing the code test operation result and the code analysis log, and submits the code to the code memory when the code is tested sufficiently;
and the code storage is used for carrying out centralized version control management on the codes submitted by the integrated test server.
9. The XML database-based software integration test system of claim 8, further comprising:
the distributed load balancing integrated test server is respectively connected with the integrated test server and the agent executors and is used for selecting the corresponding agent executors according to the operation information sent by the integrated test server and returning the results of the agent executors after execution to the integrated test server;
and the selected agent executor is used for performing test execution according to the operation configuration file transmitted by the distributed load balancing integration test server and returning a test execution result to the integration test server through the distributed load balancing integration test server.
10. The XML database-based software integration test system of claim 8, wherein the client receives an operation request including an integrated test server address configured by a user, a login account number, and items to be executed, a code analysis and submission option, and sends the operation request to the integrated test server.
11. The XML database-based software integration test system of claim 8, wherein the code compiling and analyzing module further comprises:
the code analysis module is used for calling the original code in the code memory and the code submitted to the integrated test server by a software developer to carry out comparison analysis, finding out an updating path of the code, recording a covering path of the code during test operation, and finally analyzing whether the code is tested fully or not by comparing the updating path with the testing covering path;
the code compiling module is used for compiling the code, generating corresponding compiling information by setting compiling parameters and warning levels, filtering the statement containing the 'memoryleaks' in the information by analyzing the warning information in the compiling log, and recording the statement containing the 'memory leak' into a memory leak information log.
12. The XML-database-based software integration test system of claim 8, wherein the integration test server further comprises a statistics module, and the statistics module is configured to count a change rate and a test passing rate of the code and return a statistics result to the client for display.
13. The XML-database-based software integration test system of claim 8, wherein the integration test server further comprises a test trigger module for setting a test operation of the trigger code according to the time and code change of the client.
14. The XML-database-based software integration test system according to claim 13, wherein the code analysis module records an overlay path of the code at the test runtime, specifically, at the time of code compilation, the compiler generates a corresponding symbol file, and records the overlay path of the code at the test runtime by writing trace information into the symbol file.
15. The XML-database-based software integration test system according to claim 8, wherein the memory leak information log records a location of the memory leak code, so that a developer can modify the code.
16. The XML-database-based software integration test system of claim 8, wherein the test log includes information triples, and when the test operation is completed, the test cases that pass the test and the test cases that fail the test are counted by analyzing the information triples.
17. The XML database-based software integration test system of claim 16, wherein the information triplets include:
case-group-id: the group number represents the test information;
case-id: representing a test case number;
success/failed: indicating whether the test case passes or not.
CN201210321769.4A 2012-09-03 2012-09-03 Software integration testing method and system based on extensible markup language (XML) database Expired - Fee Related CN102880546B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201210321769.4A CN102880546B (en) 2012-09-03 2012-09-03 Software integration testing method and system based on extensible markup language (XML) database

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201210321769.4A CN102880546B (en) 2012-09-03 2012-09-03 Software integration testing method and system based on extensible markup language (XML) database

Publications (2)

Publication Number Publication Date
CN102880546A true CN102880546A (en) 2013-01-16
CN102880546B CN102880546B (en) 2015-06-17

Family

ID=47481880

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201210321769.4A Expired - Fee Related CN102880546B (en) 2012-09-03 2012-09-03 Software integration testing method and system based on extensible markup language (XML) database

Country Status (1)

Country Link
CN (1) CN102880546B (en)

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103150255A (en) * 2013-03-29 2013-06-12 北京经纬恒润科技有限公司 Method and device for testing script
CN103530225A (en) * 2013-09-10 2014-01-22 武汉烽火网络有限责任公司 Automatic compilation testing method and automatic compilation testing platform for realizing same
CN103617118A (en) * 2013-11-28 2014-03-05 北京奇虎科技有限公司 Method, device and system for uniformly processing test results
CN104156224A (en) * 2013-05-14 2014-11-19 广东电网公司信息中心 Continuous integration method and system for software construction
CN104461670A (en) * 2014-11-21 2015-03-25 闻泰通讯股份有限公司 Management method for multi-project public code
CN105095089A (en) * 2015-09-14 2015-11-25 北京金山安全软件有限公司 Method and device for testing performance of application software
CN105786691A (en) * 2014-12-25 2016-07-20 重庆重邮信科通信技术有限公司 Automatic integration testing device, method and system of mobile terminal
CN105843651A (en) * 2016-03-31 2016-08-10 广州华多网络科技有限公司 Method, device and system for managing continuous integration processing script
CN103412816B (en) * 2013-08-12 2016-10-19 浪潮电子信息产业股份有限公司 A kind of continuous integrating test platform building method based on linux
CN106326116A (en) * 2016-08-17 2017-01-11 北京奇虎科技有限公司 Method and device for testing product
CN106775911A (en) * 2016-11-25 2017-05-31 努比亚技术有限公司 A kind of method of testing and device for application and development
CN106897223A (en) * 2017-02-24 2017-06-27 郑州云海信息技术有限公司 A kind of software kit delivery method and device based on continuous integrating
CN106933736A (en) * 2015-12-31 2017-07-07 中移(苏州)软件技术有限公司 A kind of method and system of project continuous integrating
CN107203473A (en) * 2017-05-26 2017-09-26 四川长虹电器股份有限公司 The automatization test system and method for automatic expansion interface test case
CN108205492A (en) * 2016-12-20 2018-06-26 阿尔卡特朗讯 For the method and apparatus of the Test Driven Development in continuous integrating frame
WO2018126964A1 (en) * 2017-01-04 2018-07-12 中兴通讯股份有限公司 Task execution method and apparatus and server
CN108388511A (en) * 2018-02-12 2018-08-10 安徽千云度信息技术有限公司 A kind of integration test method for component-based software
CN108491210A (en) * 2018-03-27 2018-09-04 无锡华云数据技术服务有限公司 Code continuous integrating method, apparatus, system and server
CN109165165A (en) * 2018-09-04 2019-01-08 中国平安人寿保险股份有限公司 Interface test method, device, computer equipment and storage medium
CN109634865A (en) * 2018-12-13 2019-04-16 平安科技(深圳)有限公司 A kind of code turns to survey method, apparatus and turns to survey terminal
CN110647460A (en) * 2019-08-05 2020-01-03 微梦创科网络科技(中国)有限公司 Test resource management method and device and test client
CN111190778A (en) * 2019-12-26 2020-05-22 曙光信息产业股份有限公司 Disk array test system for distributed storage system
CN111367791A (en) * 2020-02-19 2020-07-03 北京字节跳动网络技术有限公司 Method, device, medium and electronic equipment for generating test case
CN112486812A (en) * 2020-11-26 2021-03-12 北京海量数据技术股份有限公司 Distributed framework software testing method and device supporting cloud
CN113656291A (en) * 2021-08-04 2021-11-16 成都中科合迅科技有限公司 Dynamic calling method for software script engine
US11327723B1 (en) 2021-02-25 2022-05-10 Red Hat, Inc. Development environment integrated with failure detection system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101515232A (en) * 2008-02-21 2009-08-26 卓望数码技术(深圳)有限公司 Software continuous integration system and method
CN101833500A (en) * 2010-04-07 2010-09-15 南京航空航天大学 Embedded software intelligent testing method based on Agent
CN101982815A (en) * 2010-11-03 2011-03-02 北京世纪高通科技有限公司 Software test system and method
US20110307860A1 (en) * 2010-06-09 2011-12-15 Hong Seong Park Simulation-based interface testing automation system and method for robot software components

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101515232A (en) * 2008-02-21 2009-08-26 卓望数码技术(深圳)有限公司 Software continuous integration system and method
CN101833500A (en) * 2010-04-07 2010-09-15 南京航空航天大学 Embedded software intelligent testing method based on Agent
US20110307860A1 (en) * 2010-06-09 2011-12-15 Hong Seong Park Simulation-based interface testing automation system and method for robot software components
CN101982815A (en) * 2010-11-03 2011-03-02 北京世纪高通科技有限公司 Software test system and method

Cited By (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103150255A (en) * 2013-03-29 2013-06-12 北京经纬恒润科技有限公司 Method and device for testing script
CN103150255B (en) * 2013-03-29 2016-12-28 北京经纬恒润科技有限公司 A kind of script method of testing and device
CN104156224A (en) * 2013-05-14 2014-11-19 广东电网公司信息中心 Continuous integration method and system for software construction
CN104156224B (en) * 2013-05-14 2017-11-07 广东电网公司信息中心 A kind of software building continuous integrating method and system
CN103412816B (en) * 2013-08-12 2016-10-19 浪潮电子信息产业股份有限公司 A kind of continuous integrating test platform building method based on linux
CN103530225B (en) * 2013-09-10 2016-07-06 武汉烽火网络有限责任公司 Automatization's compiler test method and realize automatization's compiler test platform of the method
CN103530225A (en) * 2013-09-10 2014-01-22 武汉烽火网络有限责任公司 Automatic compilation testing method and automatic compilation testing platform for realizing same
CN103617118B (en) * 2013-11-28 2016-06-29 北京奇虎科技有限公司 The method that is uniformly processed of test result, Apparatus and system
CN103617118A (en) * 2013-11-28 2014-03-05 北京奇虎科技有限公司 Method, device and system for uniformly processing test results
CN104461670A (en) * 2014-11-21 2015-03-25 闻泰通讯股份有限公司 Management method for multi-project public code
CN104461670B (en) * 2014-11-21 2017-11-28 闻泰通讯股份有限公司 Entry public code management method
CN105786691A (en) * 2014-12-25 2016-07-20 重庆重邮信科通信技术有限公司 Automatic integration testing device, method and system of mobile terminal
CN105095089A (en) * 2015-09-14 2015-11-25 北京金山安全软件有限公司 Method and device for testing performance of application software
CN106933736A (en) * 2015-12-31 2017-07-07 中移(苏州)软件技术有限公司 A kind of method and system of project continuous integrating
CN106933736B (en) * 2015-12-31 2020-04-21 中移(苏州)软件技术有限公司 Method and system for continuously integrating projects
CN105843651A (en) * 2016-03-31 2016-08-10 广州华多网络科技有限公司 Method, device and system for managing continuous integration processing script
CN105843651B (en) * 2016-03-31 2019-10-11 广州华多网络科技有限公司 A kind of methods, devices and systems of management continuous integrating processing script
CN106326116A (en) * 2016-08-17 2017-01-11 北京奇虎科技有限公司 Method and device for testing product
CN106775911A (en) * 2016-11-25 2017-05-31 努比亚技术有限公司 A kind of method of testing and device for application and development
CN108205492A (en) * 2016-12-20 2018-06-26 阿尔卡特朗讯 For the method and apparatus of the Test Driven Development in continuous integrating frame
WO2018126964A1 (en) * 2017-01-04 2018-07-12 中兴通讯股份有限公司 Task execution method and apparatus and server
CN106897223A (en) * 2017-02-24 2017-06-27 郑州云海信息技术有限公司 A kind of software kit delivery method and device based on continuous integrating
CN107203473A (en) * 2017-05-26 2017-09-26 四川长虹电器股份有限公司 The automatization test system and method for automatic expansion interface test case
CN108388511A (en) * 2018-02-12 2018-08-10 安徽千云度信息技术有限公司 A kind of integration test method for component-based software
CN108491210B (en) * 2018-03-27 2019-05-03 无锡华云数据技术服务有限公司 Code continuous integrating method, apparatus, system and server
CN108491210A (en) * 2018-03-27 2018-09-04 无锡华云数据技术服务有限公司 Code continuous integrating method, apparatus, system and server
CN109165165A (en) * 2018-09-04 2019-01-08 中国平安人寿保险股份有限公司 Interface test method, device, computer equipment and storage medium
CN109634865A (en) * 2018-12-13 2019-04-16 平安科技(深圳)有限公司 A kind of code turns to survey method, apparatus and turns to survey terminal
CN109634865B (en) * 2018-12-13 2024-03-22 平安科技(深圳)有限公司 Code transfer testing method and device and transfer testing terminal
CN110647460B (en) * 2019-08-05 2023-09-05 微梦创科网络科技(中国)有限公司 Test resource management method and device and test client
CN110647460A (en) * 2019-08-05 2020-01-03 微梦创科网络科技(中国)有限公司 Test resource management method and device and test client
CN111190778A (en) * 2019-12-26 2020-05-22 曙光信息产业股份有限公司 Disk array test system for distributed storage system
CN111367791A (en) * 2020-02-19 2020-07-03 北京字节跳动网络技术有限公司 Method, device, medium and electronic equipment for generating test case
CN111367791B (en) * 2020-02-19 2023-08-01 北京字节跳动网络技术有限公司 Method, device, medium and electronic equipment for generating test case
CN112486812A (en) * 2020-11-26 2021-03-12 北京海量数据技术股份有限公司 Distributed framework software testing method and device supporting cloud
US11327723B1 (en) 2021-02-25 2022-05-10 Red Hat, Inc. Development environment integrated with failure detection system
CN113656291A (en) * 2021-08-04 2021-11-16 成都中科合迅科技有限公司 Dynamic calling method for software script engine

Also Published As

Publication number Publication date
CN102880546B (en) 2015-06-17

Similar Documents

Publication Publication Date Title
CN102880546B (en) Software integration testing method and system based on extensible markup language (XML) database
US11163731B1 (en) Autobuild log anomaly detection methods and systems
CN109726093B (en) Method, apparatus and computer program product for executing test cases
US11762717B2 (en) Automatically generating testing code for a software application
US9064056B2 (en) Completing functional testing
US7512933B1 (en) Method and system for associating logs and traces to test cases
US9558106B1 (en) Testing service with control testing
US20140068567A1 (en) Determining relevant events in source code analysis
WO2014210177A1 (en) Prioritization of tests of computer program code
KR20090017598A (en) Iterative static and dynamic software analysis
US20160259713A1 (en) Method and system for determining functional tests to execute based on code coverage
US9087155B2 (en) Automated data collection, computation and reporting of content space coverage metrics for software products
CN110750458A (en) Big data platform testing method and device, readable storage medium and electronic equipment
CN109815119B (en) APP link channel testing method and device
CA3036812A1 (en) Test case generator built into data-integration workflow editor
CN110196809B (en) Interface testing method and device
US10705949B2 (en) Evaluation of library test suites using mutation testing
US8850407B2 (en) Test script generation
US11169910B2 (en) Probabilistic software testing via dynamic graphs
US9842044B2 (en) Commit sensitive tests
US9983965B1 (en) Method and system for implementing virtual users for automated test and retest procedures
US10185647B2 (en) Debugging remote vertex code on test machine
CN111435327B (en) Log record processing method, device and system
US20150261646A1 (en) Selective profiling of applications
CN106656684B (en) Grid resource reliability monitoring method and device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
ASS Succession or assignment of patent right

Owner name: FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) C

Effective date: 20130118

Owner name: BEIDA FANGZHENG GROUP CO. LTD.

Free format text: FORMER OWNER: FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) CO., LTD.

Effective date: 20130118

C10 Entry into substantive examination
C41 Transfer of patent application or patent right or utility model
COR Change of bibliographic data

Free format text: CORRECT: ADDRESS; FROM: 201203 PUDONG NEW AREA, SHANGHAI TO: 100871 HAIDIAN, BEIJING

SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20130118

Address after: 100871 Beijing, Haidian District into the house road, founder of the building on the 5 floor, No. 298

Applicant after: PEKING UNIVERSITY FOUNDER GROUP Co.,Ltd.

Applicant after: FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) Co.,Ltd.

Address before: 201203, No. 608, midsummer Road, Zhangjiang hi tech park, Shanghai, Shanghai, Pudong New Area

Applicant before: Founder Digital Publishing Technology (Shanghai) Co.,Ltd.

ASS Succession or assignment of patent right

Owner name: FOUNDER INFORMATION INDUSTRY HOLDING CO., LTD. FOU

Free format text: FORMER OWNER: FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) CO., LTD.

Effective date: 20130912

C41 Transfer of patent application or patent right or utility model
TA01 Transfer of patent application right

Effective date of registration: 20130912

Address after: 100871 Beijing, Haidian District into the house road, founder of the building on the 5 floor, No. 298

Applicant after: PEKING UNIVERSITY FOUNDER GROUP Co.,Ltd.

Applicant after: FOUNDER INFORMATION INDUSTRY HOLDINGS Co.,Ltd.

Applicant after: FOUNDER DIGITAL PUBLISHING TECHNOLOGY (SHANGHAI) Co.,Ltd.

Address before: 100871 Beijing, Haidian District into the house road, founder of the building on the 5 floor, No. 298

Applicant before: PEKING UNIVERSITY FOUNDER GROUP Co.,Ltd.

Applicant before: Founder Digital Publishing Technology (Shanghai) Co.,Ltd.

C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20150617

Termination date: 20170903

CF01 Termination of patent right due to non-payment of annual fee