CN111858315B - Software debugging method, device, equipment and medium based on version management - Google Patents
Software debugging method, device, equipment and medium based on version management Download PDFInfo
- Publication number
- CN111858315B CN111858315B CN202010602969.1A CN202010602969A CN111858315B CN 111858315 B CN111858315 B CN 111858315B CN 202010602969 A CN202010602969 A CN 202010602969A CN 111858315 B CN111858315 B CN 111858315B
- Authority
- CN
- China
- Prior art keywords
- version
- performance test
- version number
- configuration file
- naming rule
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3628—Software debugging of optimised code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a software debugging method, a device, equipment and a medium based on version management, and relates to the technical field of computers. The embodiment of the invention carries out code version management from the development of submitted codes, provides an automatic integrated deployment function, and can realize the automatic management of development code versions, configuration file versions, interface message versions, performance test script versions, performance test scene versions and test result versions; the performance environment can be automatically built by associating each version, the deployment of the production environment is simulated, and when the performance problem occurs in the production environment, a quasi-production environment can be quickly built on a platform for performance problem investigation; the method for debugging the performance problem is more convenient while version management is considered, environment construction can be carried out according to test requirements, autonomous association among different versions is provided, or manual association is carried out on different versions for deployment and execution.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a software debugging method, apparatus, device, and medium based on version management.
Background
In recent years, with the development of agility, devOps and other fast-paced development modes, software performance testing gradually tends to be normalized, and with the rapid development of information technology, the requirements of people on the performance quality of software are higher and higher, the frequency of performance problems of the software in a production environment is more and more frequent, meanwhile, the problems of frequent iteration of software performance testing versions, complex management, time-consuming performance environment deployment for recurring production problems and difficult troubleshooting are faced by the performance testing at present.
In view of the above situation, the application number CN201410376419.7 in the prior art and the patent name "a method and system for managing performance test versions" provide a method and system for managing performance test versions, which achieve the purpose of traceability of performance test versions by uniformly naming, managing rights and managing versions of performance test documents, script scenarios and analysis data, and facilitate performance testing engineers to compare performance differences of different versions in the same scenario.
The method for managing the performance test versions focuses on naming of the performance test versions so as to facilitate traceability of the test versions, only a naming method is provided, each version needs to be manually uploaded to a relevant directory for sorting, automatic management and comparison of the versions are not realized, the naming method only relates to documents, scripts, scenes and result data, and other relevant data of performance tests such as unassociated codes, messages, configuration, performance environments and the like, in addition, the method only can play a role in induction, and automatic deployment simulating various environments cannot be performed.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a software debugging method, apparatus, device and medium based on version management, to implement automatic management of each version in the software testing process, and to more conveniently debug the software performance problem.
In a first aspect, the present invention provides a software debugging method based on version management, including: version initialization process and version multiplexing process;
the version initialization process includes the steps of:
a1, obtaining a code of a tested software, automatically integrating, deploying and constructing to obtain a development code version, and generating a development code version number according to a naming rule of the development code version;
a2, extracting a configuration file version from the development code version, and generating a configuration file version number according to a configuration file version naming rule;
a3, obtaining an interface message version obtained by at least one transaction test of the tested software, and generating an interface message version number according to an interface message version naming rule;
a4, acquiring a performance test script version obtained after debugging the interface message version in a performance test scene version, generating a performance test script version number according to a performance test script version naming rule, and generating a performance test scene version number according to the performance test scene version naming rule;
step A5, associating a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number for use in a version multiplexing process;
the version multiplexing process comprises a direct multiplexing process and a building multiplexing process:
the direct multiplexing process includes: selecting a corresponding development code version, configuration file version, interface message version, performance test script version and performance test scene version to perform multiplexing execution according to the development code version, configuration file version, interface message version, performance test script version and performance test scene version which are associated in the initialization process;
the building multiplexing process comprises the following steps: and according to the requirement, designating a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number, selecting a corresponding development code version, configuration file version, interface message version, performance test script version and performance test scene version to deploy and execute, and realizing the debugging of the tested software in a simulated production environment.
Preferably, the version initialization process further includes:
a6, generating a test result according to the associated version number, and generating a test result version number according to a test result naming rule; the test results include: concurrency number, TPS, response time and CPU index; the test result naming rule is as follows: date timestamp _ system under test number _ code version number _ test result number.
Preferably, the development code version naming rule is further specifically: date timestamp _ tested system number _ code version number;
the configuration file version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ configuration file number;
the interface message version naming rule is further specifically as follows: date and time stamp _ tested system number _ code version number _ message version number _ tested transaction name;
the performance test script version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ script version number _ tested transaction name;
the performance test scenario version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ scene version number;
the step A5 is further specifically: and associating the development code version number, the configuration file version number, the interface message version number, the performance test script version number and the performance test scene version number according to the generated version numbers for the version multiplexing process.
Further, the configuration file comprises a thread pool, a middleware configuration, a database configuration and a background application program configuration.
In a second aspect, the present invention provides a software debugging apparatus based on version management, including: the version initialization module and the version multiplexing module;
the version initialization module includes: the system comprises a development code version management module, a configuration file version management module, a message version management module, a performance test version management module and a version correlation module;
the development code version management module is used for acquiring the code of the tested software, automatically integrating, deploying and constructing to obtain a development code version, and generating a development code version number according to the development code version naming rule;
the configuration file version management module is used for extracting a configuration file version from the development code version and generating a configuration file version number according to a configuration file version naming rule;
the message version management module is used for acquiring an interface message version obtained by at least one transaction test of the tested software and generating an interface message version number according to an interface message version naming rule;
the performance test version management module is used for acquiring a performance test script version obtained after the interface message version is debugged in a performance test scene version, generating a performance test script version number according to a performance test script version naming rule, and generating a performance test scene version number according to a performance test scene version naming rule;
the version correlation module is used for correlating a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number for the version multiplexing module to use;
the version multiplexing module includes: direct multiplexing module and building multiplexing module;
the direct multiplexing module is used for selecting a corresponding development code version, a configuration file version, an interface message version, a performance test script version and a performance test scene version to perform multiplexing execution according to the development code version, the configuration file version, the interface message version, the performance test script version and the performance test scene version which are associated in the initialization module;
the building multiplexing module is used for appointing a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number according to requirements to select a corresponding development code version, a configuration file version, an interface message version, a performance test script version and a performance test scene version to automatically deploy and execute, and debugging of the tested software in a simulated production environment is achieved.
Preferably, the version initialization module further includes: a test result management module;
the test result management module is used for generating a test result according to the associated version number and generating a test result version number according to a test result naming rule; the test results include: concurrency number, TPS, response time and CPU index; the test result naming rule is as follows: date timestamp _ system under test number _ code version number _ test result number.
Preferably, the developing code version naming rule is further specifically: date timestamp _ tested system number _ code version number;
the configuration file version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ configuration file number;
the interface message version naming rule is further specifically as follows: date and time stamp _ tested system number _ code version number _ message version number _ tested transaction name;
the performance test script version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ script version number _ tested transaction name;
the property test scenario version naming rule is further specifically as follows: date timestamp _ system under test number _ code version number _ scene version number;
the version correlation module is further specifically configured to correlate the development code version number, the configuration file version number, the interface message version number, the performance test script version number, and the performance test scenario version number for use in the version multiplexing process according to each generated version number.
Further, the configuration file comprises a thread pool, a middleware configuration, a database configuration and a background application program configuration.
In a third aspect, the present invention provides an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of the first aspect when executing the program.
In a fourth aspect, the invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the method of the first aspect.
One or more technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages:
1. the version number is generated according to the set naming rule automatically for the version of each stage of the software test, the related information of the named version does not need to be sorted manually and the version file is uploaded, so that the automatic management of the development code version, the configuration file version, the interface message version, the performance test script version, the performance test scene version and the test result version can be realized, the labor is saved, the accuracy of version management is improved, and the performance test work is more standardized and unified;
2. the code version management is carried out by starting from the development and submission of the code, an automatic integrated deployment function is provided, each version is associated with an automatic performance environment building mode, the deployment of a production environment is simulated, when the performance problem occurs in the production environment, a quasi-production environment can be built on a platform quickly for performance problem troubleshooting, the problems that the deployment performance environment consumes time and the like can be solved effectively, and the performance testing efficiency is improved;
3. a related performance environment is set up by selecting a specified version number according to test requirements, production problems are reproduced, and then a contrast elimination method is adopted, so that the performance problems caused by version iteration are more accurately positioned.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
The invention will be further described with reference to the following examples with reference to the accompanying drawings.
FIG. 1 is a flow chart of a method according to one embodiment of the present invention;
FIG. 2 is a schematic view of a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of an electronic device according to a third embodiment of the invention;
FIG. 4 is a schematic structural diagram of a medium according to a fourth embodiment of the present invention;
FIG. 5 is a flowchart of a method according to a fifth embodiment of the present invention;
fig. 6 is a schematic structural diagram of a system in the fifth embodiment of the present invention.
Detailed Description
The embodiment of the application realizes the automatic management of a development code version, a configuration file version, an interface message version, a performance test script version and a performance test scene version by providing a software debugging method, a device, equipment and a medium based on version management; the function of deploying and building the associated version information is provided, the initialized version can be reused according to the requirement, and a set of personalized performance test environment required by developers or performance testers can be built quickly.
Example one
The present embodiment provides a software debugging method based on version management, as shown in fig. 1, including: version initialization process and version multiplexing process;
the version initialization process includes the steps of:
a1, obtaining a code of tested software, automatically integrating, deploying and constructing to obtain a development code version, and generating a development code version number according to a development code version naming rule;
a2, extracting a configuration file version from the development code version, and generating a configuration file version number according to a configuration file version naming rule, wherein the configuration file can comprise a thread pool, middleware configuration, database configuration, background application program configuration and the like;
a3, obtaining an interface message version obtained by at least one transaction test of the tested software, and generating an interface message version number according to an interface message version naming rule;
a4, acquiring a performance test script version obtained after debugging the interface message version in a performance test scene version, generating a performance test script version number according to a performance test script version naming rule, and generating a performance test scene version number according to the performance test scene version naming rule;
and step A5, associating the development code version number, the configuration file version number, the interface message version number, the performance test script version number and the performance test scene version number for the use of the version multiplexing process.
In the version initialization process, unified code version management is automatically performed from the development and submission of the code of each tested software, so that the automatic association of the development code version, the configuration file version, the interface message version, the performance test script version and the performance test scene version is realized, and the use in the multiplexing process is facilitated.
The version multiplexing process comprises a direct multiplexing process and a building multiplexing process.
The direct multiplexing process includes: and selecting the corresponding development code version, configuration file version, interface message version, performance test script version and performance test scene version for multiplexing execution according to the development code version, configuration file version, interface message version, performance test script version and performance test scene version which are associated in the initialization process.
If the performance environment of the same version needs to be multiplexed, the associated version number in the version initialization process is directly multiplexed and executed, so that the debugging time can be greatly saved, and the debugging efficiency is improved.
The building multiplexing process comprises the following steps: and according to the requirement, designating a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number, selecting a corresponding development code version, configuration file version, interface message version, performance test script version and performance test scene version to deploy and execute, and realizing the debugging of the tested software in a simulated production environment.
If it is necessary to multiplex different versions of the performance test environment, for example: if the production environment has performance problems, each version needing to be connected in a hanging mode is selected according to the production performance environment, such as a corresponding code version, a script version, a scene version and the like, and the production environment can be quickly restored and debugged by providing a multiplexing means of manually selecting the versions and then automatically deploying and executing.
In one possible implementation manner, the version initialization process may further include:
a6, generating a test result according to the associated version number, and generating a test result version number according to a test result naming rule; the test results include: concurrency number, TPS, response time and CPU index; the test result naming rule is as follows: date timestamp _ system under test number _ code version number _ test result number.
And generating a test result version number according to the test result naming rule by the test result, and performing unified management to facilitate subsequent analysis on the test result.
In a possible implementation manner, the developing a code version naming rule is further specifically: date timestamp _ tested system number _ code version number (e.g., 20200616174601_A01 _Code01);
the configuration file version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ configuration file number (e.g., 20200616174601_A01_Code01 _Config01);
the interface message version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ message version number _ tested transaction name (e.g., 20200616174601_A01_Code01_MSG01_ tested transaction name);
the performance test script version naming rule is further specifically as follows: date timestamp _ system under test _ code version number _ script version number _ transaction name under test (for example: 20200616174601_a01_Code01_Script01_ test transaction name);
the property test scenario version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ scene version number (e.g., 20200616174601_a01_code01 _scanario01);
the step A5 is further specifically as follows: and associating the version number of the development code, the version number of the configuration file, the version number of the interface message, the version number of the performance test script and the version number of the performance test scene for the use of a version multiplexing process according to the generated version numbers.
By uniformly developing the naming rule of the code version, the accuracy of version management can be improved, and meanwhile, the performance test work is more standardized and unified; the naming rules of other versions are further expanded on the basis of developing the naming rules of the code versions, and a basis is provided for the subsequent process of associating the versions.
Based on the same inventive concept, the application also provides a device corresponding to the method in the first embodiment, which is detailed in the second embodiment.
Example two
In this embodiment, a software debugging apparatus based on version management is provided, as shown in fig. 2, including: the version initialization module and the version multiplexing module;
the version initialization module comprises: the system comprises a development code version management module, a configuration file version management module, a message version management module, a performance test version management module and a version correlation module;
the development code version management module is used for acquiring the code of the tested software, automatically integrating, deploying and constructing to obtain a development code version, and generating a development code version number according to a development code version naming rule;
the configuration file version management module is used for extracting a configuration file version from the development code version and generating a configuration file version number according to a configuration file version naming rule; the configuration file can comprise a thread pool, middleware configuration, database configuration, background application program configuration and the like;
the message version management module is used for acquiring an interface message version obtained by at least one transaction test of the tested software and generating an interface message version number according to an interface message version naming rule;
the performance test version management module is used for acquiring a performance test script version obtained after the interface message version is debugged in a performance test scene version, generating a performance test script version number according to a performance test script version naming rule, and generating a performance test scene version number according to the performance test scene version naming rule;
the version correlation module is used for correlating the version number of the development code, the version number of the configuration file, the version number of the interface message, the version number of the performance test script and the version number of the performance test scene for the version multiplexing module to use;
the version multiplexing module includes: direct multiplexing module and building multiplexing module;
the direct multiplexing module is used for selecting a corresponding development code version, a configuration file version, an interface message version, a performance test script version and a performance test scene version to perform multiplexing execution according to the development code version, the configuration file version, the interface message version, the performance test script version and the performance test scene version which are associated in the initialization module;
and the building multiplexing module is used for selecting a corresponding development code version, configuration file version, interface message version, performance test script version and performance test scene version according to the specified development code version, configuration file version, interface message version, performance test script version and performance test scene version to automatically deploy and execute, and debugging the tested software in a simulated production environment.
In one possible implementation manner, the version initialization module further includes: a test result management module;
the test result management module is used for generating a test result according to the associated version number and generating a test result version number according to a test result naming rule; the test results include: concurrency number, TPS, response time and CPU index; the test result naming rule is as follows: date timestamp _ system under test number _ code version number _ test result number.
In a possible implementation manner, the developing a code version naming rule is further specifically: date timestamp _ tested system number _ code version number;
the configuration file version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ configuration file number;
the interface message version naming rule is further specifically as follows: date and time stamp _ tested system number _ code version number _ message version number _ tested transaction name;
the performance test script version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ script version number _ tested transaction name;
the property test scenario version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ scene version number;
the version correlation module is further specifically configured to correlate the development code version number, the configuration file version number, the interface message version number, the performance test script version number, and the performance test scenario version number for use in the version multiplexing process according to each generated version number.
Since the apparatus described in the second embodiment of the present invention is an apparatus used for implementing the method of the first embodiment of the present invention, based on the method described in the first embodiment of the present invention, a person skilled in the art can understand the specific structure and the deformation of the apparatus, and thus the details are not described herein. All the devices adopted in the method of the first embodiment of the present invention belong to the protection scope of the present invention.
Based on the same inventive concept, the application provides an electronic device embodiment corresponding to the first embodiment, which is detailed in the third embodiment.
EXAMPLE III
The embodiment provides an electronic device, as shown in fig. 3, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, any one of the first embodiment modes may be implemented.
Since the electronic device described in this embodiment is a device used for implementing the method in the first embodiment of the present application, based on the method described in the first embodiment of the present application, a specific implementation of the electronic device in this embodiment and various variations thereof can be understood by those skilled in the art, and therefore, how to implement the method in the first embodiment of the present application by the electronic device is not described in detail herein. The equipment used by those skilled in the art to implement the method in the embodiments of the present application is all within the protection scope of the present application.
Based on the same inventive concept, the application provides a storage medium corresponding to the fourth embodiment, which is described in detail in the fourth embodiment.
Example four
The present embodiment provides a computer-readable storage medium, as shown in fig. 4, on which a computer program is stored, and when the computer program is executed by a processor, the computer program may implement any one of the embodiments.
The technical scheme provided in the embodiment of the application at least has the following technical effects or advantages: the methods, devices, systems, apparatuses, and media provided by embodiments of the present application,
EXAMPLE five
One embodiment of the present invention:
(I) implementation procedure
Referring to fig. 5, the implementation flow of the present embodiment is divided into two stages: version initialization phase and version multiplexing phase;
1. version initialization phase
The version initialization phase mainly comprises the following processes:
step 1: the system obtains the development code of the tested software submitted by a developer from an svn (an open source code version control system), automatically integrates, deploys and constructs on the system to obtain the development code version, generates the development code version number, and generates the rules as follows: date timestamp system number development code version number (e.g., 20200616174601_A01 _Code01) and stored in the development code version management module.
Step 2: the system extracts configuration files (including file configurations such as thread pools, middleware configurations, database configurations and background application program configurations) from the development code versions built and deployed, and generates configuration file versions, wherein the generation rule of the configuration file version numbers is as follows: date timestamp system number development code version number configuration file number (e.g., 20200616174601_A01_Code01 _Config01) and stored in a configuration file version management module.
And 3, step 3: the performance test engineer selects a common transaction interface of the tested system to debug according to test requirements to obtain an interface message version, the system records the tested transaction interface message according to the operation of the performance test engineer, and stores the interface message version in a message version management module to generate a version number, and the generation rule is as follows: development code version number _ message version number _ tested transaction name (e.g., 20200616174601_A01_Code01_MSG01_ tested transaction name).
And 4, step 4: the performance test engineer debugs the performance test script version and sets the performance test scene version on the platform on line according to the interface message version, the system automatically generates the performance test script version number and the performance test scene version number according to the tested system code version number and stores the performance test script version number and the performance test scene version number into the script version management module and the scene version management module, and the generation rule of the performance test script version number is as follows: development code version number _ script version number (e.g.: 20200616174601 \ua01 \uCode01 \uscript 01_ tested transaction name), and the generation rule of the performance test scenario version number is as follows: code version number _ scene version number (e.g., 20200616174601_A01_Code01 _Scenario01).
And 5: the system associates each initialization version in the test environment version management module to obtain the performance test environment version, executes and generates the initial performance test result, and the execution record is recorded in the execution record version management module so as to facilitate the next multiplexing.
Step 6: the system generating the performance test result comprises: the concurrency number, TPS, response time, CPU index and the like, and the performance test result automatically generates a version number (such as 20200616174601 \uA01 \uCode01 _Result01) and stores the version number in a performance test result version management module.
2. And a version multiplexing stage.
The version multiplexing stage mainly comprises two modules, namely 1, a direct multiplexing module (for multiplexing the same version) 2 and a building multiplexing module (for multiplexing different versions), and the specific process is as follows:
step 1: if the performance environment of the same version needs to be multiplexed, the generated performance test environment version in the version initialization stage is multiplexed and executed in the test environment version management module.
Step 2: if it is necessary to multiplex different versions of the performance test environment, for example: if the production environment has performance problems, selecting each version needing to be hung in the environment building module according to the production performance environment for building preemptively, for example, selecting a corresponding code version, a script version, a scene version and the like.
And step 3: after the associated version is selected, the deployment and execution functions are selected, the system can automatically deploy codes of the associated version, and automatically call corresponding performance test scripts, performance test scenes and the like to form a set of performance debugging environment for simulating production.
(II) System architecture
Referring to fig. 6, the present embodiment discloses a software debugging system based on version management, which includes a version management module and an environment building module.
1. The version management module realizes the full-flow version management from the development code version to the performance test result version; the method mainly comprises the following steps: the system comprises a development code version management module, a configuration file version management module, a message version management module, a performance test script version management module, a performance test scene version management module, a test result version management module and a test environment version management module.
The development code version management module is mainly used for automatically integrating and deploying various version codes, acquiring code version numbers and realizing the analysis of different version codes and the purpose of code version management on the basis;
the configuration file version management module is mainly used for managing environment configurations corresponding to different system versions, such as thread pool number, middleware configuration, database configuration, background application program configuration and the like;
the message version management module comprises: 1. message online debugging function, 2, storing and managing messages of each version, and 3, inquiring message function;
the performance test script version management module comprises: 1. online debugging of performance test scripts, 2, storing and managing the performance test scripts of various versions, and 3, inquiring, synchronously analyzing and comparing different functions (such as script parameters and the like) of the scripts of different versions;
the performance test scenario version management module comprises: 1. setting and executing performance test scenes on line, and 2, saving and inquiring the performance test scenes of each version;
the test result version management module comprises: 1. on-line analysis of performance test results, 2, storing and managing the performance test results of each version;
the test environment version management module can automatically associate codes, performance test scripts and performance test scenes of the same version and provide a deployment function, so that the environment can be conveniently reused.
2. The environment building module mainly comprises environment association and environment deployment functions.
The environment association function mainly provides autonomous association among different versions; the various versions are manually associated according to the test requirements, for example: and performing comparison verification in the performance test, wherein the code version is upgraded from V0.10 to V0.20, the performance test result shows a descending trend, in order to solve the problem, the elimination verification is required, and whether the environment configuration is changed or not is verified by using the code version of V0.20 and the environment configuration version of V0.10.
The environment association function is realized by the following steps: 1. and (3) selecting a code version 3 needing to be deployed under the newly-built version, selecting a configuration version 4 needing to be deployed and used under the newly-built version, mapping the selected code and the configuration version to a server needing to be used, and selecting a scene version needing to be reused.
The environment deployment function mainly provides deployment execution function after the association of each version.
The method comprises the following concrete steps:
1. clicking a starting button of the list operation column, and deploying an environment under a corresponding server by the system according to the selected version number;
2. after the starting is successful, clicking the performance scene version to execute, and initiating a performance test according to the selected performance test scene by the system;
3. and generating a performance test result after the performance test is finished, wherein the version number naming mode of the performance test result is consistent with the environment version.
According to one or more technical schemes provided by the embodiment of the invention, the version number is generated according to the set naming rule automatically for the version at each stage of the software test, the related information of the named version does not need to be manually arranged and the version file is uploaded, the automatic management of the development code version, the configuration file version, the interface message version, the performance test script version, the performance test scene version and the test result version can be realized, the labor is saved, the accuracy of version management is improved, and meanwhile, the performance test work is more standardized and unified; the code version management is carried out by starting from the development and submission of the code, an automatic integrated deployment function is provided, each version is associated with an automatic performance environment building mode, the deployment of a production environment is simulated, when the performance problem occurs in the production environment, a quasi-production environment can be built on a platform quickly for performance problem troubleshooting, the problems that the deployment performance environment consumes time and the like can be solved effectively, and the performance testing efficiency is improved; and a related performance environment is set up by selecting a specified version number according to the test requirements, the production problem is reproduced, and then a comparison elimination method is adopted, so that the performance problem caused by version iteration is more accurately positioned.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Although specific embodiments of the invention have been described above, it will be understood by those skilled in the art that the specific embodiments described are illustrative only and are not limiting upon the scope of the invention, and that equivalent modifications and variations can be made by those skilled in the art without departing from the spirit of the invention, which is to be limited only by the appended claims.
Claims (10)
1. A software debugging method based on version management is characterized by comprising the following steps: version initialization process and version multiplexing process;
the version initialization process includes the steps of:
a1, obtaining a code of tested software, automatically integrating, deploying and constructing to obtain a development code version, and generating a development code version number according to a development code version naming rule;
step A2, extracting a configuration file version from the development code version, and generating a configuration file version number according to a configuration file version naming rule;
a3, obtaining an interface message version obtained by at least one transaction test of the tested software, and generating an interface message version number according to an interface message version naming rule;
step A4, obtaining a performance test script version obtained after debugging the interface message version in a performance test scenario version, generating a performance test scenario version number according to a performance test script version naming rule, and generating a performance test scenario version number according to a performance test scenario version naming rule;
step A5, associating a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number for use in a version multiplexing process;
the version multiplexing process comprises a direct multiplexing process and a building multiplexing process:
the direct multiplexing process includes: selecting a corresponding development code version, configuration file version, interface message version, performance test script version and performance test scene version to perform multiplexing execution according to the development code version, configuration file version, interface message version, performance test script version and performance test scene version which are associated in the initialization process;
the building multiplexing process comprises the following steps: and according to the requirement, designating a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number, selecting a corresponding development code version, configuration file version, interface message version, performance test script version and performance test scene version to deploy and execute, and realizing the debugging of the tested software in a simulated production environment.
2. The method of claim 1, wherein: the version initialization process further includes:
a6, generating a test result according to the associated version number, and generating a test result version number according to a test result naming rule; the test results include: concurrency number, TPS, response time and CPU index; the test result naming rule is as follows: date timestamp _ system under test number _ code version number _ test result number.
3. The method of claim 1, wherein:
the development code version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number;
the configuration file version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ configuration file number;
the interface message version naming rule is further specifically as follows: date and time stamp _ tested system number _ code version number _ message version number _ tested transaction name;
the performance test script version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ script version number _ tested transaction name;
the property test scenario version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ scene version number;
the step A5 is further specifically as follows: and associating the version number of the development code, the version number of the configuration file, the version number of the interface message, the version number of the performance test script and the version number of the performance test scene for the use of a version multiplexing process according to the generated version numbers.
4. The method of claim 1, wherein: the configuration file comprises a thread pool, a middleware configuration, a database configuration and a background application program configuration.
5. A software debugging device based on version management is characterized by comprising: the version initialization module and the version multiplexing module;
the version initialization module includes: the system comprises a development code version management module, a configuration file version management module, a message version management module, a performance test version management module and a version correlation module;
the development code version management module is used for acquiring the code of the tested software, automatically integrating, deploying and constructing to obtain a development code version, and generating a development code version number according to a development code version naming rule;
the configuration file version management module is used for extracting a configuration file version from the development code version and generating a configuration file version number according to a configuration file version naming rule;
the message version management module is used for acquiring an interface message version obtained by at least one transaction test of the tested software and generating an interface message version number according to an interface message version naming rule;
the performance test version management module is used for acquiring a performance test script version obtained after the interface message version is debugged in a performance test scene version, generating a performance test script version number according to a performance test script version naming rule, and generating a performance test scene version number according to the performance test scene version naming rule;
the version correlation module is used for correlating a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number for the version multiplexing module to use;
the version multiplexing module comprises: direct multiplexing module and building multiplexing module;
the direct multiplexing module is used for selecting a corresponding development code version, a configuration file version, an interface message version, a performance test script version and a performance test scene version to perform multiplexing execution according to the development code version, the configuration file version, the interface message version, the performance test script version and the performance test scene version which are associated in the initialization module;
the building multiplexing module is used for appointing a development code version number, a configuration file version number, an interface message version number, a performance test script version number and a performance test scene version number according to requirements to select a corresponding development code version, a configuration file version, an interface message version, a performance test script version and a performance test scene version to automatically deploy and execute, and debugging of the tested software in a simulated production environment is achieved.
6. The apparatus of claim 5, wherein: the version initialization module further includes: a test result management module;
the test result management module is used for generating a test result according to the associated version number and generating a test result version number according to a test result naming rule; the test results include: concurrency number, TPS, response time and CPU index; the test result naming rule is as follows: date timestamp _ system under test number _ code version number _ test result number.
7. The apparatus of claim 5, wherein:
the development code version naming rule is further specifically as follows: date timestamp _ system number under test _ code version number;
the configuration file version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ configuration file number;
the interface message version naming rule is further specifically as follows: date and time stamp _ tested system number _ code version number _ message version number _ tested transaction name;
the performance test script version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ script version number _ tested transaction name;
the property test scenario version naming rule is further specifically as follows: date timestamp _ tested system number _ code version number _ scene version number;
the version correlation module is further specifically configured to correlate the development code version number, the configuration file version number, the interface message version number, the performance test script version number, and the performance test scenario version number for use in the version multiplexing process according to each generated version number.
8. The apparatus of claim 5, wherein: the configuration file comprises a thread pool, middleware configuration, database configuration and background application program configuration.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 4 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010602969.1A CN111858315B (en) | 2020-06-29 | 2020-06-29 | Software debugging method, device, equipment and medium based on version management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010602969.1A CN111858315B (en) | 2020-06-29 | 2020-06-29 | Software debugging method, device, equipment and medium based on version management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111858315A CN111858315A (en) | 2020-10-30 |
| CN111858315B true CN111858315B (en) | 2022-10-18 |
Family
ID=72989499
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010602969.1A Active CN111858315B (en) | 2020-06-29 | 2020-06-29 | Software debugging method, device, equipment and medium based on version management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111858315B (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102053836B (en) * | 2010-12-31 | 2013-04-10 | 广东欧珀电子工业有限公司 | Implementation method of version management tool for Android application development |
| CN103995776A (en) * | 2014-05-28 | 2014-08-20 | 浪潮电子信息产业股份有限公司 | Automatic version verification method based on B/S structure system |
| CN104142891A (en) * | 2014-08-01 | 2014-11-12 | 浪潮电子信息产业股份有限公司 | Method and system for managing performance test versions |
| US10387368B2 (en) * | 2015-10-23 | 2019-08-20 | International Business Machines Corporation | Ideal age vector based file retention in a software testing system |
| CN110888652B (en) * | 2019-10-24 | 2023-07-07 | 福建天泉教育科技有限公司 | Multi-version construction method and terminal based on jenkins plug-in |
-
2020
- 2020-06-29 CN CN202010602969.1A patent/CN111858315B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN111858315A (en) | 2020-10-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109726132B (en) | Software testing method and software testing automatic management system | |
| CN110008113B (en) | Test method and device and electronic equipment | |
| WO2018010552A1 (en) | Test method and device | |
| US8918760B2 (en) | Test script generation for application image validation | |
| US7870169B2 (en) | Method for enabling traceability and recovery from errors during migration of software applications | |
| CN109840194B (en) | Method and system for detecting configuration file | |
| US20170153969A1 (en) | System and method for executing integration tests in multiuser environment | |
| US10592703B1 (en) | Method and system for processing verification tests for testing a design under test | |
| CN102999419B (en) | A kind of Android test incident record back method and device | |
| CN114297056A (en) | Automatic testing method and system | |
| US20190073292A1 (en) | State machine software tester | |
| CN106528429A (en) | UI testing method and device | |
| RU2678717C9 (en) | Method for building a software system for automating and visualizing testing of embedded software for electronic devices | |
| CN110928777B (en) | Test case processing method, device, equipment and storage medium | |
| CN110727575A (en) | Information processing method, system, device and storage medium | |
| CN114996127A (en) | Intelligent test method and system for solid state disk firmware module | |
| CN113391998A (en) | Regression testing method, device, electronic equipment and storage medium | |
| JP4672532B2 (en) | Operator simulation system and operator simulation method | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN111858315B (en) | Software debugging method, device, equipment and medium based on version management | |
| CN111708712A (en) | User behavior test case generation method, flow playback method and electronic equipment | |
| CN110471828B (en) | Operating system testing method, device and equipment thereof | |
| CN113806209A (en) | Interface testing method, frame, computer device and storage medium | |
| CN116719736A (en) | Test case generation method and device for testing software interface | |
| CN105339974B (en) | Analog sensor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |