CN113791953A - Test scheduling and log management method and device, computer equipment and storage medium - Google Patents

Test scheduling and log management method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN113791953A
CN113791953A CN202111087289.1A CN202111087289A CN113791953A CN 113791953 A CN113791953 A CN 113791953A CN 202111087289 A CN202111087289 A CN 202111087289A CN 113791953 A CN113791953 A CN 113791953A
Authority
CN
China
Prior art keywords
test
software package
information
service cluster
log
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111087289.1A
Other languages
Chinese (zh)
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.)
Ping An Puhui Enterprise Management Co Ltd
Original Assignee
Ping An Puhui Enterprise Management 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 Ping An Puhui Enterprise Management Co Ltd filed Critical Ping An Puhui Enterprise Management Co Ltd
Priority to CN202111087289.1A priority Critical patent/CN113791953A/en
Publication of CN113791953A publication Critical patent/CN113791953A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3065Monitoring arrangements determined by the means or processing involved in reporting the monitored data

Abstract

The invention relates to the field of artificial intelligence, and discloses a method and a device for test scheduling and log management, computer equipment and a storage medium, wherein the method comprises the following steps: acquiring an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing A/B test on the test service cluster and the production service cluster running the production software package; acquiring a code merging request of an iterative software package, and extracting attribute information from the code merging request according to a preset attribute extraction rule; and extracting the index information from the test information according to the test information generated by the A/B test and a preset index extraction rule, and integrating the attribute information and the index information into a test log. The invention also relates to a blockchain technique, where information can be stored in blockchain nodes. The invention improves the testing efficiency of the software package, realizes the acquisition of key information and main viewpoints transmitted by the testing information, and accurately and quickly acquires affiliated departments and developers.

Description

Test scheduling and log management method and device, computer equipment and storage medium
Technical Field
The invention relates to the technical field of artificial intelligence software testing, in particular to a method and a device for testing scheduling and log management, computer equipment and a readable storage medium.
Background
Software testing refers to the process of operating a program under specified conditions to discover program errors, measure software quality, and evaluate whether it can meet design requirements.
However, the inventor realizes that the current software test usually requires a tester to manually arrange an iterative software package, which not only results in low test efficiency, but also causes the test result not to be correlated to a specific development end because an object of the current software test scheme only concerns the software package but ignores information of the development end for developing the software package, and further fails to realize evaluation of development effect of the development end based on the test information; meanwhile, because the test information of the software package is usually huge and complex, if the test information is simply stored, subsequent development teams cannot quickly and accurately grasp the main content and viewpoint transmitted by the test information of each time, and the work efficiency of further developing and perfecting the software package is low.
Disclosure of Invention
The invention aims to provide a test scheduling and log management method, a test scheduling and log management device, computer equipment and a readable storage medium, which are used for solving the problems that the test efficiency is low, a test result cannot be associated to a specific development end and main contents and viewpoints transmitted by test information of previous times cannot be quickly and accurately grasped in the prior art.
In order to achieve the above object, the present invention provides a method for test scheduling and log management, which is characterized by comprising:
acquiring an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing A/B test on the test service cluster and the production service cluster running the production software package; the A/B test is a test scheme which is based on the same test target, respectively sends request information to the test service cluster and the production service cluster according to a preset proportion, and evaluates the processing effect of the test service cluster and the production service cluster on the request information;
acquiring a code merging request of the iterative software package from the GIT system, and extracting attribute information from the code merging request according to a preset attribute extraction rule; the GIT system is distributed version control software for performing version management on a production software package and an iteration software package, and the code merging request is a request instruction which is sent to the GIT system by a development end developing the iteration software package and is used for integrating development codes developed by the development end into the iteration software package;
and receiving test information generated by the control end according to the A/B test, extracting index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log.
In the above scheme, the obtaining an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing an a/B test on the test service cluster and the production service cluster running the production software package includes:
receiving a software number sent by a control end, identifying a generating service cluster in which a production software package corresponding to the software number runs from a production environment, acquiring an iteration software package corresponding to the software number from a preset GIT system, and deploying the iteration software package in the testing service cluster;
acquiring a load balancer connected with the test service cluster and the production service cluster respectively, and constructing a request distribution strategy in the load balancer, wherein the request distribution strategy defines the proportion of request information distributed to the test service cluster and the production service cluster;
and calling the load balancer and sending request information to the test service cluster and the production service cluster according to the request distribution strategy so as to carry out A/B test on the production software package and the iteration software package.
In the foregoing solution, before the obtaining the code merge request of the iterative software package from the GIT system, the method further includes:
creating a log table, defining the characteristics of columns in the log table to obtain column labels, and constructing attribute extraction rules and index extraction rules according to the column labels.
In the foregoing solution, the acquiring a code merge request of the iterative software package from the GIT system, and extracting attribute information from the code merge request according to a preset attribute extraction rule includes:
identifying a main branch generating the iterative software package in the GIT system, and acquiring a code merging request for generating the iterative software package from the main branch;
and acquiring attribute metadata in the attribute extraction rule, and acquiring attribute information corresponding to the attribute metadata from the code merging request.
In the above scheme, extracting the index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log includes:
acquiring index metadata from the index extraction rule, and extracting the index information from the test information according to the index metadata;
and summarizing the index information and the attribute information to form an information set, and taking the identity information in the attribute information as the name of the information set to obtain the test log.
In the foregoing solution, after integrating the attribute information and the index information into a test log, the method further includes:
and loading the test log into the log table, shooting a snapshot of the test information to obtain a test screenshot, and loading the test screenshot into the log table and associating the test screenshot with the test log.
In the foregoing solution, after the test screenshot is loaded into the log table and associated with the test log, the method further includes:
extracting a test screenshot in the log table to convert the log table into a text table, storing the test screenshot in a preset database, and associating the test screenshot with the test log in the text table; extracting the identity information of each test log in the text table, summarizing to form an index table, associating the index table with the text table, and storing the index table and the text table in a preset buffer;
after the storing the index table and the text table in a preset buffer, the method further comprises:
and uploading the index table and the text table to a block chain.
In order to achieve the above object, the present invention further provides a test scheduling and log management apparatus, including:
the test scheduling module is used for acquiring an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing A/B test on the test service cluster and the production service cluster running the production software package; the A/B test is a test scheme which is based on the same test target, respectively sends request information to the test service cluster and the production service cluster according to a preset proportion, and evaluates the processing effect of the test service cluster and the production service cluster on the request information;
the attribute extraction module is used for acquiring a code merging request of the iterative software package from the GIT system and extracting attribute information from the code merging request according to a preset attribute extraction rule; the GIT system is distributed version control software for performing version management on a production software package and an iteration software package, and the code merging request is a request instruction which is sent to the GIT system by a development end developing the iteration software package and is used for integrating development codes developed by the development end into the iteration software package;
and the log management module is used for receiving test information generated by the control terminal according to the A/B test, extracting index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log.
In order to achieve the above object, the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor of the computer device implements the steps of the test scheduling and log management method when executing the computer program.
In order to achieve the above object, the present invention further provides a computer-readable storage medium, which stores a computer program, and when the computer program stored in the computer-readable storage medium is executed by a processor, the computer program implements the steps of the test scheduling and log management method.
According to the test scheduling and log management method, device, computer equipment and storage medium provided by the invention, the effect of distinguishing the production software package and the iteration software package is realized by acquiring the iteration software package corresponding to the currently running production software package and deploying the iteration software package in the preset test service cluster, so that the production software package and the iteration software package can be conveniently subjected to A/B test subsequently, and the development end and/or the control end can accurately and quickly find the effect difference between the production software package and the iteration software package through automatic A/B test, so that the test efficiency of the software package is improved.
And acquiring a development end of the iterative software package by extracting attribute information from the code merging request through an attribute extraction rule, further realizing the association of the test information and the specific development end so as to be convenient for the subsequent combination with index information in the test information and be used for comprehensively evaluating the development effect of the development end, and reducing the data storage capacity for describing the attribute information of the development end of the iterative software package in the test log by extracting main attribute information. And obtaining the key information and the main viewpoint transmitted by the test information by a mode of extracting the index information from the test information through the index extraction rule, so that a developer can accurately evaluate the using effect of the iterative software package only through the key index. Meanwhile, the attribute information and the index information are integrated into the test information, so that the attribute information and the index information correspond to each other one by one, developers can accurately and quickly obtain departments to which the index information belongs and develop the iterative software package, and the iterative software package can be conveniently managed subsequently.
Drawings
FIG. 1 is a flowchart of a test scheduling and log management method according to a first embodiment of the present invention;
FIG. 2 is a schematic diagram of an environment application of a test scheduling and log management method according to a second embodiment of the test scheduling and log management method of the present invention;
FIG. 3 is a flowchart of a method for test scheduling and log management according to a second embodiment of the present invention;
FIG. 4 is a schematic diagram of program modules of a third embodiment of a test scheduling and log management apparatus according to the present invention;
fig. 5 is a schematic diagram of a hardware structure of a computer device according to a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention provides a test scheduling and log management method, a test scheduling and log management device, computer equipment and a storage medium, which are suitable for the technical field of artificial intelligent software test and provide a test scheduling and log management method based on a test scheduling module, an attribute extraction module and a log management module. The method comprises the steps of A/B testing a test service cluster and a production service cluster running a production software package by acquiring the iteration software package corresponding to the currently running production software package and deploying the iteration software package in the test service cluster; acquiring a code merging request of an iterative software package from a GIT system, and extracting attribute information from the code merging request according to an attribute extraction rule; and receiving test information generated by the control end according to the A/B test, extracting index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log.
The first embodiment is as follows:
referring to fig. 1, a method for test scheduling and log management in this embodiment includes:
s101: acquiring an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing A/B test on the test service cluster and the production service cluster running the production software package; the A/B test is a test scheme which is based on the same test target, respectively sends request information to the test service cluster and the production service cluster according to a preset proportion, and evaluates the processing effect of the test service cluster and the production service cluster on the request information.
S103: acquiring a code merging request of the iterative software package from the GIT system, and extracting attribute information from the code merging request according to a preset attribute extraction rule; the GIT system is distributed version control software for performing version management on a production software package and an iteration software package, and the code merging request is a request instruction which is sent to the GIT system by a development end for developing the iteration software package and is used for integrating development codes developed by the development end into the iteration software package.
S104: and receiving test information generated by the control end according to the A/B test, extracting index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log.
In an exemplary embodiment, the method comprises the steps of obtaining an iteration software package corresponding to a currently running production software package, deploying the iteration software package in a preset test service cluster, achieving the effect of distinguishing and arranging the production software package and the iteration software package, and facilitating the follow-up A/B test on the production software package and the iteration software package, wherein the A/B test is to make two (A/B) or multiple (A/B/n) versions for a Web or App interface or process, respectively enabling visitor groups (target groups) with the same (similar) composition to randomly access the versions in the same time dimension, collecting user experience data and service data of each group, and finally analyzing and evaluating the best version and a formally adopted test scheme; the automatic A/B test is adopted, so that the development end and/or the control end can accurately and quickly find the effect difference between the production software package and the iteration software package, and the test efficiency of the software package is improved.
The development end of the iterative software package is obtained by acquiring the code merging request of the iterative software package from the GIT system and extracting the attribute information from the code merging request according to the preset attribute extraction rule, so that the test information is associated with the specific development end, the subsequent combination with the index information in the test information is facilitated, the development effect of the development end is comprehensively evaluated, and the data storage quantity for describing the attribute information of the development end of the iterative software package in the test log is reduced by extracting the main attribute information. By receiving the test information generated by the control end according to the A/B test and extracting the index information from the test information according to the preset index extraction rule, the key information and the main viewpoint transmitted by the test information are obtained, so that a developer can accurately evaluate the using effect of the iterative software package only through the key index. Meanwhile, the attribute information and the index information are integrated into the test information, so that the attribute information and the index information correspond to each other one by one, developers can accurately and quickly obtain departments to which the index information belongs and develop the iterative software package, and the iterative software package can be conveniently managed subsequently.
Example two:
the embodiment is a specific application scenario of the first embodiment, and the method provided by the present invention can be more clearly and specifically explained through the embodiment.
Next, in a server running with a test scheduling and log management method, performing A/B test on a test service cluster and a production service cluster; the method provided by the embodiment is specifically described by taking an example of extracting attribute information from a code merging request of an iterative software package, extracting index information from test information of an a/B test, and integrating the attribute information and the index information into a test log. It should be noted that the present embodiment is only exemplary, and does not limit the protection scope of the embodiments of the present invention.
Fig. 2 schematically illustrates an environment application diagram of a test scheduling and log management method according to a second embodiment of the present application.
In an exemplary embodiment, the server 2 in which the test scheduling and log management method is located is respectively connected with the test service cluster 21, the production service cluster 22, the GIT system 3 and the control terminal 4 through a network; the server 2 may provide services through one or more networks, which may include various network devices, such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and/or the like. The network may include physical links, such as coaxial cable links, twisted pair cable links, fiber optic links, combinations thereof, and/or the like. The network may include wireless links, such as cellular links, satellite links, Wi-Fi links, and/or the like; the control terminal 4 may be a computer device such as a smart phone, a tablet computer, a notebook computer, and a desktop computer.
Fig. 3 is a flowchart of a method for scheduling test and managing log according to an embodiment of the present invention, where the method specifically includes steps S201 to S206.
S201: acquiring an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing A/B test on the test service cluster and the production service cluster running the production software package; the A/B test is a test scheme which is based on the same test target, respectively sends request information to the test service cluster and the production service cluster according to a preset proportion, and evaluates the processing effect of the test service cluster and the production service cluster on the request information.
In order to achieve an effect difference between the production software package and the iteration software package automatically, this step is performed by obtaining the iteration software package corresponding to the currently running production software package, and the iterative software package is deployed in a preset test service cluster to realize the effect of distinguishing and arranging the production software package and the iterative software package so as to carry out A/B test on the production software package and the iterative software package subsequently, wherein, the A/B test refers to that two (A/B) or a plurality of (A/B/n) versions are manufactured for a Web or App interface or process, in the same time dimension, visitor groups (target groups) with the same (similar) components are respectively allowed to randomly access the versions, user experience data and service data of each group are collected, the best version is finally analyzed and evaluated, and a test scheme is formally adopted; the A/B test is convenient for the development end and/or the control end, so that the effect difference between the production software package and the iteration software package can be accurately and quickly found, and the test efficiency of the software package is improved.
In a preferred embodiment, the obtaining an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing an a/B test on the test service cluster and the production service cluster running the production software package includes:
s11: receiving a software number sent by a control end, identifying a generating service cluster running a production software package corresponding to the software number from a production environment, acquiring an iteration software package corresponding to the software number from a preset GIT system, and deploying the iteration software package in the testing service cluster.
In this step, the software number is a unique identifier representing software, and the corresponding iterative software package is accurately obtained in a manner of obtaining the corresponding iterative software package from the GIT system through the software number sent by the control terminal. And further, identifying the software package in the GIT system according to the software number, acquiring the software package with the latest version number and setting the software package as the software package to be tested. Identifying a generation service cluster in which a production software package corresponding to the software number runs from a production environment, and judging whether the version number of the production software package is consistent with the version number of the software package to be tested; if yes, ending; and if not, setting the software package to be tested as the iteration software package.
It should be noted that the GIT system refers to a distributed version control system, is used for development and version iteration of a software project, is connected with at least one development end to distribute development tasks to the development end, and forms an iterative software package for version updating of a currently produced software package by receiving and merging function codes sent by the development end.
S12: and acquiring a load balancer connected with the test service cluster and the production service cluster respectively, and constructing a request distribution strategy in the load balancer, wherein the request distribution strategy defines the proportion of distributing request information to the test service cluster and the production service cluster.
In this step, the load balancer is a data routing device that distributes requests to a plurality of servers/service clusters for execution based on the existing network structure, thereby achieving the effects of expanding the bandwidth of network devices and servers, increasing throughput, enhancing network data processing capability, and improving network flexibility and availability.
By constructing the request distribution strategy in the load balancer, the proportion of sending request information to the test service cluster and the production service cluster is defined in the load balancer, so that the operation of testing the iterative software package is simplified, and the testing efficiency is improved.
S13: and calling the load balancer and sending request information to the test service cluster and the production service cluster according to the request distribution strategy so as to carry out A/B test on the production software package and the iteration software package.
In this step, the A/B test is performed through the request distribution strategy, so that the control end can generate test information for evaluating the advantages and the characteristics of the iterative software package according to the A/B test.
S202: creating a log table, defining the characteristics of columns in the log table to obtain column labels, and constructing attribute extraction rules and index extraction rules according to the column labels.
In order to realize self-defined attribute extraction rules and index extraction rules, so that developers can obtain corresponding information according to requirements, a log table for storing the test log is constructed by creating the log table, defining a mode of obtaining column labels by the characteristics of columns in the log table, and then the test log is inquired conveniently in the follow-up process. By constructing the attribute extraction rule and the index extraction rule according to the column label, developers can obtain corresponding attribute information and index information according to the requirements of the developers, the comprehensiveness of the attribute of the test object and the preservation of the test index is ensured, and the preservation space of the attribute information and the index information is greatly reduced.
S203: acquiring a code merging request of the iterative software package from the GIT system, and extracting attribute information from the code merging request according to a preset attribute extraction rule; the GIT system is distributed version control software for performing version management on a production software package and an iteration software package, and the code merging request is a request instruction which is sent to the GIT system by a development end for developing the iteration software package and is used for integrating development codes developed by the development end into the iteration software package.
In order to identify an initiation side of an iterative software package so as to evaluate the development effect of the initiation side based on test information, this step extracts attribute information from a code merge request by obtaining the code merge request of the iterative software package from the GIT system according to a preset attribute extraction rule,
the development end of the iterative software package is obtained, and then the test information is associated with the specific development end, so that the subsequent combination with the index information in the test information is facilitated, the development effect of the development end is comprehensively evaluated, and the data storage quantity of the attribute information of the development end of the iterative software package in the test log is reduced by extracting the main attribute information.
In a preferred embodiment, the acquiring a code merge request of the iterative software package from the GIT system, and extracting attribute information from the code merge request according to a preset attribute extraction rule includes:
s31: identifying a main branch generating the iterative software package in the GIT system, and acquiring a code merging request for generating the iterative software package from the main branch.
In this step, the code merging request in the GIT system records a function branch corresponding to the management branch where the function code is located and a main branch where the main code for receiving and merging the function code is located; the attribute information is recorded and comprises identity information, an update name and an update description, wherein the identity information is a unique identifier of the attribute information, can be a primary key ID of the attribute information, and can also be a software ID which is integrated according to a software number and a version number and represents the identity of the iterative software package; the updating name is used for briefly explaining the functional tasks realized by the iterative software package; the update description is used for describing the functional tasks realized by the iterative software package in detail and recording the developer and the department thereof for developing the iterative software package.
S32: and acquiring attribute metadata in the attribute extraction rule, and acquiring attribute information corresponding to the attribute metadata from the code merging request.
In this step, the attribute metadata is a column label used for representing the attribute characteristics of the development end in the log table, and the attribute information can be obtained from the code merging request in a targeted manner according to the attribute metadata, so that the accuracy of extracting the attribute information is ensured.
Illustratively, the attribute metadata is as follows:
ID string comment 'Primary Key ID', (for obtaining identity information)
dep _ cls1 string comment 'first class department' (for getting developers and their departments)
dep _ cls2 string comment 'second level department' (for getting developers and their departments)
dep _ cls3 string comment 'three-level department' (for getting developers and their departments)
S204: and receiving test information generated by the control end according to the A/B test, extracting index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log.
In order to obtain the key information in the test information and accurately express the main content and the viewpoint to be transmitted in the test information, the key information and the main viewpoint transmitted by the test information are obtained by receiving the test information generated by the control end according to the A/B test and extracting the index information from the test information according to a preset index extraction rule, so that a developer can accurately evaluate the using effect of the iterative software package only through the key index.
Meanwhile, the attribute information and the index information are integrated into the test information, so that the attribute information and the index information correspond to each other one by one, developers can accurately and quickly obtain departments to which the index information belongs and develop the iterative software package, and the iterative software package can be conveniently managed subsequently.
In a preferred embodiment, extracting the index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log includes:
s41: and acquiring index metadata from the index extraction rule, and extracting the index information from the test information according to the index metadata.
In this step, the index metadata is a column label used for representing the index characteristics of the development terminal in the log table, and the index information can be obtained from the code merging request in a targeted manner according to the index metadata, so that the accuracy of extracting the index information is ensured.
Illustratively, the metric metadata is as follows:
aim of the test 'aim',
aim _ index _ data string comment 'target index',
drive _ index _ data string comment 'drive index',
threshold _ index _ data string comment 'guardrail index',
p _ value default (16,2) comment 'p value',
test _ html string comment 'web page information of the test',
test _ pic string comment 'screenshot of the test'.
S42: and summarizing the index information and the attribute information to form an information set, and taking the identity information in the attribute information as the name of the information set to obtain the test log.
In this step, the identity information of the attribute information is a unique identifier of the attribute information, which may be a primary key ID of the attribute information, or a software ID that characterizes the identity of the iterative software package and is integrated according to a software number and a version number. The test log is obtained by taking the identity information in the attribute information as the name of the information set, so that the attribute information and index information required by a developer can be conveniently and accurately searched through the name.
S205: and loading the test log into the log table, shooting a snapshot of the test information to obtain a test screenshot, and loading the test screenshot into the log table and associating the test screenshot with the test log.
In order to facilitate the storage of the test result, the test log is loaded into the log table in the step, so that the test log can be stored and managed subsequently; because complete test information is sometimes used according to the guidance of the test log on the subsequent development scheme, in order to ensure the comprehensiveness of test information storage, in this step, a test screenshot is obtained by taking a snapshot of the test information, and the test screenshot is loaded into the log table and associated with the test log.
S206: extracting a test screenshot in the log table to convert the log table into a text table, storing the test screenshot in a preset database, and associating the test screenshot with the test log in the text table; and extracting the identity information of each test log in the text table, summarizing to form an index table, associating the index table with the text table, and storing the index table and the text table in a preset buffer.
In order to avoid the problems that the storage space of a buffer is insufficient and the feedback data is slow due to the fact that large files such as test screenshots and the like are stored in the buffer, the test screenshots in the log table are extracted to convert the log table into a text table, the test screenshots are stored in a preset database, the test screenshots are associated with test logs in the text table, the text table is stored in the preset buffer, the large files such as the test screenshots and the like in the log table are extracted and stored in the database, and the obtaining probability of the common test screenshots is low, so that the feedback efficiency of the test logs in the log table is guaranteed, the test screenshots with comprehensive information records are provided for the test logs according to the information obtaining requirement of a development end, and the information feedback speed and the comprehensiveness are considered.
In order to facilitate the query of the test logs, in the step, the identity information of each test log in the text table is extracted and summarized to form an index table, and the index table is associated with the text table, so that developers can obtain the required test logs only through the index table, and the feedback efficiency of the test logs is improved. Meanwhile, the efficiency of calling the index table by developers and acquiring the test logs through the index table is further improved by storing the index table and the text table in a preset buffer.
Preferably, after the storing the index table and the text table in a preset buffer, the method further includes:
and uploading the index table and the text table to a block chain.
It should be noted that, based on the index table and the text table, corresponding digest information is obtained, specifically, the digest information is obtained by performing hash processing on the index table and the text table, for example, by using the sha256s algorithm. Uploading summary information to the blockchain can ensure the safety and the fair transparency of the user. The user equipment can download the summary information from the blockchain so as to check whether the index table and the text table are tampered. The blockchain referred to in this example is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
Example three:
referring to fig. 4, a test scheduling and log management apparatus 1 of the present embodiment includes:
the test scheduling module 11 is configured to obtain an iterative software package corresponding to a currently running production software package, deploy the iterative software package in a preset test service cluster, and perform an a/B test on the test service cluster and the production service cluster running the production software package; the A/B test is a test scheme which is based on the same test target, respectively sends request information to the test service cluster and the production service cluster according to a preset proportion, and evaluates the processing effect of the test service cluster and the production service cluster on the request information;
an attribute extraction module 13, configured to obtain a code merging request of the iterative software package from the GIT system, and extract attribute information from the code merging request according to a preset attribute extraction rule; the GIT system is distributed version control software for performing version management on a production software package and an iteration software package, and the code merging request is a request instruction which is sent to the GIT system by a development end developing the iteration software package and is used for integrating development codes developed by the development end into the iteration software package;
and the log management module 14 is configured to receive test information generated by the control terminal according to the a/B test, extract index information from the test information according to a preset index extraction rule, and integrate the attribute information and the index information into a test log.
Optionally, the test scheduling and log management apparatus 1 further includes:
the rule making module 12 is configured to create a log table, define characteristics of columns in the log table to obtain column labels, and construct an attribute extraction rule and an index extraction rule according to the column labels.
And the snapshot log module 15 is configured to load the test log into the log table, take a snapshot of the test information to obtain a test screenshot, and load the test screenshot into the log table and associate the test screenshot with the test log.
An index text module 16, configured to extract a test screenshot in the log table, so that the log table is converted into a text table, store the test screenshot in a preset database, and associate the test screenshot with a test log in the text table; and extracting the identity information of each test log in the text table, summarizing to form an index table, associating the index table with the text table, and storing the index table and the text table in a preset buffer.
Optionally, the test scheduling module 11 further includes:
the iteration deployment unit 111 is configured to receive a software number sent by a control end, identify a generation service cluster in which a production software package corresponding to the software number is operated from a production environment, acquire an iteration software package corresponding to the software number from a preset GIT system, and deploy the iteration software package in the test service cluster.
A policy constructing unit 112, configured to obtain load balancers respectively connected to the test service cluster and the production service cluster, and construct a request distribution policy in the load balancers, where the request distribution policy defines a ratio of distributing request information to the test service cluster and the production service cluster.
And the test execution unit 113 is configured to invoke the load balancer and send request information to the test service cluster and the production service cluster according to the request distribution policy, so as to perform an a/B test on the production software package and the iterative software package.
Optionally, the attribute extracting module 13 further includes:
a request extracting unit 131, configured to identify a main branch generating the iterative software package in the GIT system, and obtain a code merging request for generating the iterative software package from the main branch.
An attribute extraction unit 132, configured to obtain attribute metadata in the attribute extraction rule, and obtain attribute information corresponding to the attribute metadata from the code merge request.
Optionally, the log management module 14 further includes:
an index extracting unit 141, configured to obtain index metadata from the index extraction rule, and extract the index information from the test information according to the index metadata.
And a log generating unit 142, configured to summarize the index information and the attribute information to form an information set, and obtain the test log by using the identity information in the attribute information as a name of the information set.
The embodiment of the application can acquire and process related data based on an artificial intelligence technology. Among them, Artificial Intelligence (AI) is a theory, method, technique and application system that simulates, extends and expands human Intelligence using a digital computer or a machine controlled by a digital computer, senses the environment, acquires knowledge and uses the knowledge to obtain the best result.
The artificial intelligence infrastructure generally includes technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and the like.
The technical scheme is applied to the field of artificial intelligence data processing, and is characterized in that an iterative software package corresponding to a currently running production software package is obtained and deployed in a test service cluster, A/B tests are carried out on the test service cluster and the production service cluster running the production software package through the artificial intelligence technology, a code merging request of the iterative software package is obtained from a GIT system, attribute information is extracted from the code merging request according to an attribute extraction rule, index information is extracted from the test information according to a preset index extraction rule according to test information generated by the A/B tests, and the attribute information and the index information are integrated into a test log.
Example four:
in order to achieve the above object, the present invention further provides a computer device 5, where components of the test scheduling and log management apparatus in the third embodiment may be distributed in different computer devices, and the computer device 5 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster formed by multiple application servers) that executes a program, and the like. The computer device of the embodiment at least includes but is not limited to: a memory 51, a processor 52, which may be communicatively coupled to each other via a system bus, as shown in FIG. 5. It should be noted that fig. 5 only shows a computer device with components, but it should be understood that not all of the shown components are required to be implemented, and more or fewer components may be implemented instead.
In this embodiment, the memory 51 (i.e., a readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 51 may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. In other embodiments, the memory 51 may be an external storage device of a computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device. Of course, the memory 51 may also include both internal and external storage devices of the computer device. In this embodiment, the memory 51 is generally used for storing an operating system and various application software installed in the computer device, such as program codes of the test scheduling and log management apparatus in the third embodiment. Further, the memory 51 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 52 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 52 is typically used to control the overall operation of the computer device. In this embodiment, the processor 52 is configured to run a program code stored in the memory 51 or process data, for example, run a test scheduling and log management apparatus, so as to implement the test scheduling and log management methods of the first and second embodiments.
Example five:
to achieve the above objects, the present invention also provides a computer readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application store, etc., on which a computer program is stored, which when executed by a processor 52, implements corresponding functions. The computer-readable storage medium of this embodiment is used for storing a computer program for implementing the test scheduling and log management method, and when being executed by the processor 52, implements the test scheduling and log management method of the first embodiment and the second embodiment.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (10)

1. A test scheduling and log management method is characterized by comprising the following steps:
acquiring an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing A/B test on the test service cluster and the production service cluster running the production software package; the A/B test is a test scheme which is based on the same test target, respectively sends request information to the test service cluster and the production service cluster according to a preset proportion, and evaluates the processing effect of the test service cluster and the production service cluster on the request information;
acquiring a code merging request of the iterative software package from the GIT system, and extracting attribute information from the code merging request according to a preset attribute extraction rule; the GIT system is distributed version control software for performing version management on a production software package and an iteration software package, and the code merging request is a request instruction which is sent to the GIT system by a development end developing the iteration software package and is used for integrating development codes developed by the development end into the iteration software package;
and receiving test information generated by the control end according to the A/B test, extracting index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log.
2. The method according to claim 1, wherein the obtaining of the iterative software package corresponding to the currently running production software package, deploying the iterative software package in a preset test service cluster, and performing a/B test on the test service cluster and the production service cluster running the production software package comprises:
receiving a software number sent by a control end, identifying a generating service cluster in which a production software package corresponding to the software number runs from a production environment, acquiring an iteration software package corresponding to the software number from a preset GIT system, and deploying the iteration software package in the testing service cluster;
acquiring a load balancer connected with the test service cluster and the production service cluster respectively, and constructing a request distribution strategy in the load balancer, wherein the request distribution strategy defines the proportion of request information distributed to the test service cluster and the production service cluster;
and calling the load balancer and sending request information to the test service cluster and the production service cluster according to the request distribution strategy so as to carry out A/B test on the production software package and the iteration software package.
3. The test scheduling and log management method of claim 1, wherein before the obtaining the code merge request of the iterative software package from the GIT system, the method further comprises:
creating a log table, defining the characteristics of columns in the log table to obtain column labels, and constructing attribute extraction rules and index extraction rules according to the column labels.
4. The method of claim 1, wherein the obtaining of the code merge request of the iterative software package from the GIT system and the extracting of the attribute information from the code merge request according to the preset attribute extraction rule comprise:
identifying a main branch generating the iterative software package in the GIT system, and acquiring a code merging request for generating the iterative software package from the main branch;
and acquiring attribute metadata in the attribute extraction rule, and acquiring attribute information corresponding to the attribute metadata from the code merging request.
5. The method of claim 1, wherein the extracting the index information from the test information according to a preset index extraction rule and integrating the attribute information and the index information into the test log comprises:
acquiring index metadata from the index extraction rule, and extracting the index information from the test information according to the index metadata;
and summarizing the index information and the attribute information to form an information set, and taking the identity information in the attribute information as the name of the information set to obtain the test log.
6. The method of claim 1, wherein after integrating the attribute information and the metric information into a test log, the method further comprises:
and loading the test log into the log table, shooting a snapshot of the test information to obtain a test screenshot, and loading the test screenshot into the log table and associating the test screenshot with the test log.
7. The method of claim 6, wherein after the loading the test screenshots into the log table and associating with the test log, the method further comprises:
extracting a test screenshot in the log table to convert the log table into a text table, storing the test screenshot in a preset database, and associating the test screenshot with the test log in the text table; extracting the identity information of each test log in the text table, summarizing to form an index table, associating the index table with the text table, and storing the index table and the text table in a preset buffer;
after the storing the index table and the text table in a preset buffer, the method further comprises:
and uploading the index table and the text table to a block chain.
8. A test scheduling and log management apparatus, comprising:
the test scheduling module is used for acquiring an iterative software package corresponding to a currently running production software package, deploying the iterative software package in a preset test service cluster, and performing A/B test on the test service cluster and the production service cluster running the production software package; the A/B test is a test scheme which is based on the same test target, respectively sends request information to the test service cluster and the production service cluster according to a preset proportion, and evaluates the processing effect of the test service cluster and the production service cluster on the request information;
the attribute extraction module is used for acquiring a code merging request of the iterative software package from the GIT system and extracting attribute information from the code merging request according to a preset attribute extraction rule; the GIT system is distributed version control software for performing version management on a production software package and an iteration software package, and the code merging request is a request instruction which is sent to the GIT system by a development end developing the iteration software package and is used for integrating development codes developed by the development end into the iteration software package;
and the log management module is used for receiving test information generated by the control terminal according to the A/B test, extracting index information from the test information according to a preset index extraction rule, and integrating the attribute information and the index information into a test log.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the test scheduling and log management method according to any one of claims 1 to 7 are implemented when the computer program is executed by the processor of the computer device.
10. A computer-readable storage medium, on which a computer program is stored, wherein the computer program stored in the computer-readable storage medium, when being executed by a processor, implements the steps of the test scheduling and log management method according to any one of claims 1 to 7.
CN202111087289.1A 2021-09-16 2021-09-16 Test scheduling and log management method and device, computer equipment and storage medium Pending CN113791953A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111087289.1A CN113791953A (en) 2021-09-16 2021-09-16 Test scheduling and log management method and device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111087289.1A CN113791953A (en) 2021-09-16 2021-09-16 Test scheduling and log management method and device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN113791953A true CN113791953A (en) 2021-12-14

Family

ID=78878641

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111087289.1A Pending CN113791953A (en) 2021-09-16 2021-09-16 Test scheduling and log management method and device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113791953A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180253296A1 (en) * 2015-10-30 2018-09-06 Hewlett Packard Enterprise Development Lp Software kit release management
CN109471795A (en) * 2018-10-16 2019-03-15 平安普惠企业管理有限公司 It is grouped test method, device, computer equipment and storage medium
US20200125485A1 (en) * 2018-10-17 2020-04-23 Servicenow, Inc. Environment for continuous testing and integration of software
US10956132B1 (en) * 2018-06-11 2021-03-23 Amazon Technologies, Inc. Unified code and data management for model development
CN112596784A (en) * 2020-12-28 2021-04-02 青岛海尔科技有限公司 Iterative version deployment method and device
CN113032245A (en) * 2021-02-26 2021-06-25 深圳壹账通创配科技有限公司 Error positioning identification test method and device, computer equipment and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180253296A1 (en) * 2015-10-30 2018-09-06 Hewlett Packard Enterprise Development Lp Software kit release management
US10956132B1 (en) * 2018-06-11 2021-03-23 Amazon Technologies, Inc. Unified code and data management for model development
CN109471795A (en) * 2018-10-16 2019-03-15 平安普惠企业管理有限公司 It is grouped test method, device, computer equipment and storage medium
US20200125485A1 (en) * 2018-10-17 2020-04-23 Servicenow, Inc. Environment for continuous testing and integration of software
CN112596784A (en) * 2020-12-28 2021-04-02 青岛海尔科技有限公司 Iterative version deployment method and device
CN113032245A (en) * 2021-02-26 2021-06-25 深圳壹账通创配科技有限公司 Error positioning identification test method and device, computer equipment and storage medium

Similar Documents

Publication Publication Date Title
US10769228B2 (en) Systems and methods for web analytics testing and web development
CN109542791B (en) A kind of program large-scale concurrent evaluating method based on container technique
CN106156186B (en) Data model management device, server and data processing method
CN108563951B (en) Virus detection method and device
CN110474900B (en) Game protocol testing method and device
CN105095059A (en) Method and device for automated testing
CN115129736A (en) Rule engine-based rule event dynamic loading and updating method and related equipment
CN113157315A (en) Method, device, equipment and medium for identifying difference information of different versions of software
Wang et al. A model-based framework for cloud API testing
CN112231230A (en) Test case management method and device, electronic equipment and storage medium
CN113032245A (en) Error positioning identification test method and device, computer equipment and storage medium
CN114185808A (en) Automatic testing method and device, electronic equipment and computer readable storage medium
US20220405184A1 (en) Method, electronic device, and computer program product for data processing
Jiang et al. Assuring the model evolution of protocol software specifications by regression testing process improvement
CN114048024A (en) Task deployment method, device, equipment, storage medium and product
CN116088846A (en) Processing method, related device and equipment for continuous integrated code format
CN113568836A (en) Multi-time-series sample feature extraction method and software detection method applying same
CN112364022A (en) Information derivation management method and device, computer equipment and readable storage medium
CN111951112A (en) Intelligent contract execution method based on block chain, terminal equipment and storage medium
CN113791953A (en) Test scheduling and log management method and device, computer equipment and storage medium
CN111459828A (en) Non-functional test evaluation method and device for software version
CN114003737A (en) Double-record examination assisting method, device, equipment and medium based on artificial intelligence
CN114416596A (en) Application testing method and device, computer equipment and storage medium
CN111460436B (en) Unstructured data operation method and system based on blockchain
CN114003784A (en) Request recording method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination