CN111427762A

CN111427762A - Automatic calling tool analysis techniques

Info

Publication number: CN111427762A
Application number: CN201911254884.2A
Authority: CN
Inventors: 赵光光; 李涛
Original assignee: Beijing Keyware Co ltd
Current assignee: Beijing Keyware Co ltd
Priority date: 2019-12-09
Filing date: 2019-12-09
Publication date: 2020-07-17

Abstract

The invention relates to an automatic calling tool analysis technology, which distributes items to different test servers, and the test servers analyze the items and return test results, and the automatic calling tool analysis technology comprises the following steps: step 1) configuring an environment variable on a computer provided with a test tool and configuring the environment variable required by the test tool; step 2) configuring information required by the tested project on the control computer, and adjusting according to different test projects; step 3) then the control machine distributes the project, and the control machine distributes the tested project, the development environment, the language, the report format, the environment variable call and other information to the test machine; step 4) after the testing machine receives the information sent by the control machine, the testing machine combines the information sent by the control machine and then tests the information, and sends the test result to the control machine; and 5) after the analysis is completed, displaying through a page, and simultaneously generating a test report.

Description

Automatic calling tool analysis techniques

Technical Field

The invention relates to an automatic calling tool analysis technology, which is a technology for distributing projects to different test servers, analyzing the projects by the test servers and returning test results.

Background

In an application system, software is increasingly applied, and as the functions of system software become more powerful, the software functions become more complex, so that the code quality needs to be tested to ensure the correctness of the software functions.

Software testing is generated in connection with the generation of software. The software scale in the early software development process is very small and low in complexity, the software development process is disordered and quite random, the test meaning is narrow, a developer is equal to debugging in the test process, the purpose is to correct known faults in the software, and the developer usually completes the part of work. The test is very little invested, the test is introduced late, and the test is usually performed after the code is formed and the product is basically finished. With the development of software in the direction of large-scale and high complexity, the quality of software becomes more and more important, the basic theory and practical technology of software testing begin to be formed, various processes and management methods begin to be designed for software development, and the software development mode gradually transits from a chaotic and disordered development process to a structured development process, and is characterized by structured analysis and design, structured review, structured program design and structured testing. And also, the concept of quality is integrated into the method, the definition of software test is changed, the test is not simply a process of finding errors, and the test is used as the main function of Software Quality Assurance (SQA) and comprises the content of software quality evaluation, Bill Hetzel indicates in the complete guideline for software test: "testing is any activity that aims at evaluating a program or system attribute. The test is a measure of the quality of the software. "software developers and testers are beginning to sit together to explore software engineering and testing problems.

Common test methods include static test methods and dynamic test methods, unit test, integration test, system test and acceptance test according to test levels, and test tools are indispensable aspects of the current test according to any method.

For some projects, if the tested project and the testing tool are not on the same computer, the tested project and the testing tool cannot be used, so that the testing tool cannot be effectively used, and the improvement of software quality is not greatly facilitated.

Disclosure of Invention

Aiming at the problem that no analysis tool exists in the market, the invention aims to provide a method for automatically distributing projects, automatically configuring project information, automatically calling a test tool to analyze and the like aiming at a static analysis tool which is mainstream in the market.

In order to achieve the purpose, the invention is realized by the following technical scheme: the method comprises the following steps of configuring environment variables on a computer provided with a test tool, configuring information required by a tested project on a control computer, distributing the project and testing, wherein the method comprises the following steps:

step 1) configuring environment variables on a computer provided with a test tool, compiling the tested project when the test tool analyzes the project, and ensuring that the project can be analyzed, wherein different projects need different compiling environments. Therefore, the analysis requires the environment variables to be configured correctly. Configuring a header file directory, a library file directory and a bin directory generally, and configuring according to an operation manual for some special development environments; for embedded development environments, information such as chip type is generally required to be configured. In order to avoid conflict between settings of various environment variables on one computer, parameters of each development environment are generally made into a file form, executable authorities (bat for windows and shell for linux) are given, the environment variables are set in the file form by calling during testing of a project, and after the test is completed, the environment variables disappear, so that the next test cannot be influenced;

and 2) secondly, configuring information required by the tested project on the control computer, and configuring different parameters on the control computer according to different test projects, wherein the parameters generally comprise project types, development environments, development languages, rules required to be used, environment variables required to be called, report formats and the like. For a common project, after the project is loaded, the type of the project can be automatically analyzed, development environment, development language, default rules and the like are matched, but for a project of a complex type, default matching may be incorrect and needs to be adjusted;

and 3) the control machine distributes the items, the control machine and the testing machine are communicated during distribution, and the IP and the testing tool of the corresponding testing machine are added in the control machine. The control machine sends all the information of the tested project, development environment, language, report format, environment variable call and the like to the testing machine;

and 4) testing is carried out finally, after the testing machine receives the information sent by the control machine, the information sent by the control machine is combined, the combination is completed, the environment variable is called for configuration, then the project is analyzed, the project is constructed once during analysis, if the project is compiled and passed, the project is analyzed directly, and if the project is failed, error information is returned. After the construction is successful, the project is directly analyzed, and after the analysis is completed, the test result is sent to a control machine;

and 5) after the analysis is completed, displaying through a page, enabling a tester or a developer to check each problem, determining whether the problem is the problem or not, editing and deleting the problem, restoring the problem to the database after the determination is completed, and generating a test report.

The invention has the following three important points:

1. the test tool is automatically called, before calling, information such as development environment, language, report format, environment variable and the like of items needs to be configured on a control machine, the information needs to be configured correctly, if errors exist, the test tool cannot run normally, the wrong test tool is called, a test result is incorrect and the like, and for error information, a control opportunity gives prompt information. After the configuration information is correct, the control machine sends the information to the testing machine, and the testing machine calls a testing tool to analyze after receiving the configuration information;

2. in the configuration of the environment, after the tester receives the configuration information of the project, the tester needs to call the environment variables according to the development environment and language information, so that the correctness of the development environment and the language needs to be ensured, and if the environment variables are incorrect, the calling of the environment variables is incorrect, and the project cannot be correctly analyzed. The environment variable is a key step for correctly calling the test tool, important information such as the name, a compiler, a linker, a header file, a library file, a chip type number and the like of the test tool is set in the environment variable, and the test tool analyzes the project according to the information;

3. and returning the test report, wherein after the test is finished, the test tool generates the test report according to the report format and returns the test report to the control machine, and the control machine displays or downloads the report according to the report format.

Drawings

Embodiments of the invention will now be described with reference to the accompanying drawings, in which:

FIG. 1 is a tool invocation process of the present invention.

FIG. 2 is an environment configuration process of the present invention.

Detailed Description

The automatic calling tool analysis technique of the present invention will be described in detail below with reference to the accompanying drawings.

The invention is realized by the following technical scheme: configuring environment variables on a computer provided with a test tool, configuring information required by a tested project on a control computer, distributing the project and testing.

It is to be understood that while the present invention has been disclosed in connection with the preferred embodiments thereof, the same is not to be considered as limiting. It will be apparent to those skilled in the art from this disclosure that many changes and modifications can be made, or equivalents modified, in the embodiments of the invention without departing from the scope of the invention. Therefore, any simple modification, equivalent change and modification made to the above embodiments according to the technical essence of the present invention are still within the scope of the protection of the technical solution of the present invention, unless the contents of the technical solution of the present invention are departed.

Claims

1. An automatic calling tool analysis technique for automatically calling and testing a static analysis tool, the method comprising:

step 1) configuring environment variables on a computer provided with a test tool, compiling the tested project when the test tool analyzes the project, and ensuring that the project can be analyzed, wherein different projects need different compiling environments. Therefore, the analysis requires the environment variables to be configured correctly. Configuring a header file directory, a library file directory and a bin directory generally, and configuring the header file directory, the library file directory and the bin directory according to an operation manual for some special development environments; for embedded development environments, information such as chip type is generally required to be configured. In order to avoid conflict between settings of various environment variables on one computer, parameters of each development environment are generally made into a file form, executable authorities (bat for windows and shell for linux) are given, the environment variables are set in the file form by calling during testing of a project, and after the test is completed, the environment variables disappear, so that the next test cannot be influenced;

and 2) secondly, configuring information required by the tested project on the control computer, and configuring different parameters on the control computer according to different test projects, wherein the parameters generally comprise project types, development environments, development languages, rules required to be used, environment variables required to be called, report formats and the like. For a common project, after the project is loaded, the type of the project can be automatically analyzed, development environment, development language, default rules and the like can be matched, but for a project with a complex type, default matching may be incorrect and needs to be adjusted;

and 3) the control machine distributes the items, the network is ensured to be intercommunicated between the control machine and the test machine during distribution, and the IP and the test tool of the corresponding test machine are added in the control machine. The control machine distributes all information such as the tested project, the development environment, the language, the report format, the environment variable call and the like to the testing machine;

and 5) after the analysis is completed, displaying through a page, enabling a tester or a developer to check each problem, determining whether the problem is the problem or not, editing and deleting the problem, storing the problem in a database again after the determination is completed, and generating a test report.