CN113010208A - Version information generation method, version information generation device, version information generation equipment and storage medium - Google Patents
Version information generation method, version information generation device, version information generation equipment and storage medium Download PDFInfo
- Publication number
- CN113010208A CN113010208A CN202110469150.7A CN202110469150A CN113010208A CN 113010208 A CN113010208 A CN 113010208A CN 202110469150 A CN202110469150 A CN 202110469150A CN 113010208 A CN113010208 A CN 113010208A
- Authority
- CN
- China
- Prior art keywords
- query
- version information
- data
- demand
- data table
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 230000007547 defect Effects 0.000 claims description 55
- 238000012360 testing method Methods 0.000 claims description 52
- 238000012216 screening Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 6
- 238000001914 filtration Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 13
- 238000007726 management method Methods 0.000 description 13
- 238000013507 mapping Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 7
- 238000011161 development Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 238000012356 Product development Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000011056 performance test Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 230000033764 rhythmic process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- 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
-
- 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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
The embodiment of the invention discloses a method, a device, equipment and a storage medium for generating version information, wherein the method comprises the following steps: responding to the query instruction of the version information, and acquiring an access path corresponding to the query instruction; calling a database interface of at least one target application program corresponding to the operation subject according to the access path, and acquiring first version information of the target application program recorded in real time; confirming a corresponding query type according to the query instruction; according to the query conditions, the first version information is screened, the second version information corresponding to the query type is output, automatic acquisition of the version information of the cross-operation main body and the cross-target application program is achieved, the situation that a user accesses a database of the operation main body one by one to collect and summarize the version information is avoided, time spent on acquiring the version information is reduced, and the version information acquisition efficiency is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of networks, in particular to a method, a device, equipment and a storage medium for generating version information.
Background
In the fast iterative product, factors such as an update period, labor cost and technical reasons are considered, and when the research and development capability of an enterprise cannot meet the current project requirement, a corresponding technical service needs to be purchased to generate a new version of iterative product so as to support the update of the product and the group maintenance of users.
When a large platform system is subjected to version iteration once, a plurality of projects are jointly subjected to iterative release, a research and development process can be managed by using project management tools, and different projects are researched and developed by personnel of different companies, so that each project can have an independent project management tool, authority data are independent, and cross-company and cross-project version information recording and summarizing cannot be achieved. For the version iteration team personnel, the progress of all projects needs to be grasped, and the data is summarized to output an iteration report.
In the process of implementing the invention, the inventor finds that: the existing version iterative project management tools divide the authority according to companies and projects, need to manually record, check and summarize projects one by one, are seriously time-consuming and low in efficiency, and cannot generate a uniform iteration progress report to know the iteration progress of each company involved in one iteration.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a storage medium for generating version information, which are used for automatically acquiring the version information in a version iteration process.
In a first aspect, an embodiment of the present invention provides a method for generating version information, where the method includes:
responding to a query instruction of the version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction;
calling a database interface of at least one target application program corresponding to the operation subject according to the access path to acquire first version information of the target application program recorded in real time;
confirming a corresponding query type according to the query instruction; the query type includes at least one of: the method comprises the following steps of demand query, version iteration query, defect query and test case query;
and screening the first version information according to the query condition, and outputting second version information corresponding to the query type.
In a second aspect, an embodiment of the present invention provides an apparatus for generating version information, including:
the access path acquisition module is used for responding to a query instruction of the version information and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction;
the first version information acquisition module is used for calling a database interface of at least one target application program corresponding to the operation subject according to the access path and acquiring the first version information of the target application program recorded in real time;
the query type determining module is used for determining the corresponding query type according to the query instruction; the query type includes at least one of: the method comprises the following steps of demand query, version iteration query, defect query and test case query;
and the second version information acquisition module is used for screening the first version information according to the query conditions and outputting second version information corresponding to the query type.
In a third aspect, an embodiment of the present invention further provides an electronic device, including:
one or more processors;
storage means for storing one or more programs;
when the one or more programs are executed by the one or more processors, the one or more processors implement the version information generation method according to any embodiment of the present invention.
In a fourth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for generating version information according to any embodiment of the present invention.
According to the technical scheme provided by the embodiment of the invention, the access path corresponding to the query instruction is obtained in response to the query instruction of the version information; calling a database interface of at least one target application program corresponding to the operation subject according to the access path to acquire first version information of the target application program recorded in real time; meanwhile, according to the query instruction, confirming the corresponding query type; the first version information is screened according to the query condition in the query instruction, and the second version information corresponding to the query type is output, so that the automatic acquisition of the version information of the cross-operation main body and the cross-target application program is realized, the condition that a user accesses a database of the operation main body one by one to acquire and summarize the version information is avoided, the time spent is reduced, and the version information acquisition efficiency is improved; meanwhile, the second version information is obtained by obtaining the first version information recorded in real time and then screening, so that the real-time updating of the second version information is realized.
Drawings
Fig. 1A is a flowchart of a version information generating method according to an embodiment of the present invention;
fig. 1B is a schematic diagram of obtaining target query information according to an embodiment of the present invention;
fig. 1C is a representation view of a version information display diagram according to a first embodiment of the present invention;
FIG. 1D is a diagram illustrating an iterative progress report according to an embodiment of the present invention;
fig. 1E is a schematic diagram of performing data detail page jump according to an embodiment of the present invention;
fig. 1F is a schematic diagram of a table for obtaining iteration information according to an embodiment of the present invention;
FIG. 1G is a diagram illustrating a target email according to an embodiment of the present invention;
fig. 2A is a flowchart of a version information generating method according to a second embodiment of the present invention;
fig. 2B is a schematic flowchart of a version information generating method according to a second embodiment of the present invention;
fig. 3 is a block diagram of a version information generation apparatus according to a third embodiment of the present invention;
fig. 4 is a block diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Example one
Fig. 1A is a flowchart of a version information generation method according to an embodiment of the present invention, where this embodiment is applicable to automatic query and summarization of version information of cross-operator and cross-application programs in a version iteration process; the method may be performed by a version information generating apparatus, which may be implemented by software and/or hardware and integrated on an electronic device, and may be typically integrated in a server and a terminal device, and specifically includes the following steps:
s110, responding to a query instruction of the version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction.
The version information is data information submitted by each participant developer aiming at different application programs in the version iteration process, and can comprise a function test case, discovered defects, performance test results, issued legacy problems, online risks and the like; through the version information, the problems existing in the version iteration process of the current application program and the corresponding processing mode can be obtained; furthermore, by counting and summarizing the version information of each company corresponding to the current application program, the version iteration progress corresponding to the current application program can be known in real time, and the version iteration of the current application program can be controlled and adjusted according to the current progress and the development period.
The version iteration is to update the version of the application program according to a fixed development cycle; iterations are fixed periods of development rhythm and versions are the actual output delivered to the user. In practice, a version delivered to the user may include multiple iterations, that is, an upgraded version is generated after multiple development cycles and delivered to the user; an iteration can also comprise a plurality of versions, namely a plurality of upgraded versions are submitted to a user in a development cycle; for the two situations, flexible selection can be performed according to actual needs. Optionally, in the embodiment of the present invention, each time an iteration is performed, a version is submitted to the user; that is, each time a development cycle passes, an upgrade version is submitted to the user, so that the upgrade of the application version can be more fixed. The embodiment of the present invention is not particularly limited with respect to the relationship between the version and the iteration.
The query instruction is a data query command aiming at the version information and consists of a plurality of query conditions; by acquiring the query instruction of the user, iterative information of different companies aiming at different application programs is automatically searched, and then version information meeting query conditions is automatically returned, so that the automatic acquisition of the version information corresponding to a specific application program can be realized. The query condition, which is condition information for searching for version information, may include an operation subject to be queried, a target application, a data type, and creation information of data (e.g., creation date and creator); specifically, the user may input different query conditions in different query interfaces, for example, the first query interface inputs an operator to be queried, and the second query interface inputs an application to be queried, so as to query and acquire version information according to a plurality of query conditions. In the embodiment of the present invention, the content of the query condition is not specifically limited.
The access path is an access path of the database where the query instruction corresponds to the query data; optionally, in this embodiment of the present invention, the obtaining, in response to the query instruction of the version information, an access path corresponding to the query instruction may include: extracting an operation main body included in the query instruction and at least one target application program matched with the operation main body; and generating at least one access path according to the operation main body and each target application program. The operation subject is a company participating in iteration of the current application program version; and the target application program is an application program which needs to inquire corresponding version information and comprises the identification and the version identification of the application program. Specifically, after a query instruction input by a user is obtained, the query instruction is analyzed to obtain an included operation main body and a target application program corresponding to a current operation main body; searching matched storage data in a local database according to the operation subject and the target application program to acquire an access path corresponding to the query instruction; the local database stores the mapping relation between the query condition and the access path.
Optionally, in the embodiment of the present invention, a mapping relationship between an operation subject, an application program, and an access path is obtained in advance, and the mapping relationship is stored in a local database; the system comprises an operation main body, a plurality of application programs, a database and a database, wherein the operation main body corresponds to the application programs, and version iteration data corresponding to each application program are stored in the independent database; through the pre-configured mapping relation, the matched access path can be quickly acquired according to the query condition, and the acquisition efficiency of the version information can be improved. Particularly, if the identifier of the operation subject in the query condition is inconsistent with the identifier of the operation subject in the pre-configured mapping relationship, for example, the query condition input by the user is "hua ye", and the identifier of the operation subject in the mapping relationship in the local database is "hua ye technology limited company", a comparison relationship between the operation subject in the local database and a common name or an abbreviation of the operation subject may be pre-established, so as to achieve acquisition of an access path corresponding to the current name of the operation subject when an incomplete name of the operation subject in the query condition is acquired.
And S120, calling a database interface of at least one target application program corresponding to the operation subject according to the access path, and acquiring first version information of the target application program recorded in real time.
The management platform is adopted to monitor and manage version iteration of different operation subjects aiming at different application programs; the management platform may specifically include a Tencent Agile Product Development platform (TAPD); through the TAPD platform, version information aiming at different application programs uploaded by developers of all operation subjects is obtained, and tracking of iteration progress of all application program versions, management of task working hours and tracking management of defect problems can be achieved. Particularly, different companies participating in the current version iteration can correspond to different management platforms, further, different applications responsible for the same operation subject correspond to different groups in the management platforms, and the version information of the different operation subjects for the different applications is stored in respective independent databases; the version information between different management platforms and between different groups of the same management platform can not be shared, so that the grouping management of different application programs can be realized, and the leakage of the version information is avoided. As shown in fig. 1B, according to the obtained query condition, the first version information corresponding to the multiple target applications may be obtained through the matched access path, so that the first version information corresponding to the multiple target applications may be simultaneously queried and obtained, and the obtaining efficiency of the version information is improved.
The database interface is an access interface of the database; typically, the database Interface may specifically include an Application Programming Interface (API), where the API is a convention for linking different components of the software system, and through the API, an Application developer may access a set of routines without accessing source codes thereof and understanding details of internal working mechanisms; in the embodiment of the invention, after the corresponding access path is obtained according to the query instruction, the data query request based on Resttemplate is sent to the database corresponding to the target application program through the application program interface, so that the data information corresponding to the operation subject and the target application program in the database can be automatically obtained, the normal version iteration work of each target application program cannot be influenced, and the influence of version information query on the version iteration process is avoided. Wherein, RestTemplate is a data request tool based on hypertext transfer protocol.
Wherein the first version information is all data related to version iteration of the target application program; specifically, after the access path corresponding to the query instruction is acquired, the database corresponding to the target application program is accessed through the acquired access path, and all stored data matched with the version identifier of the target application program in the database are searched through the interface of the database to acquire the first version information, so that the acquisition of the version information of the cross-operation main body and the cross-application program is realized. Meanwhile, the first version information recorded in real time is obtained from the database, so that the first version information can be updated in real time, namely the matched version information newly submitted by developers can be obtained in real time, and the iteration progress of the target application program can be obtained in real time.
S130, confirming a corresponding query type according to the query instruction; the query type includes at least one of: requirement query, version iteration query, defect query and test case query.
Specifically, after the first version information of the target application program is acquired, the user can input a corresponding query condition (for example, date) in a new query interface, and issue a corresponding query instruction according to the query condition to determine the current query type; the query types comprise demand query, version iteration query, defect query and test case query; and then screening the first version information updated in real time according to the query type in the query instruction so as to obtain screening data matched with the query type.
S140, screening the first version information according to the query conditions, and outputting second version information corresponding to the query type.
The second version information is version information obtained after the first version information is screened according to the query condition; specifically, after the query type is determined according to the query instruction, the acquired real-time updated first version information is screened according to the query type to acquire the first version information matched with the query type as second version information; further, after second version information corresponding to the query type is acquired, the acquired second version information is displayed on a data display interface, wherein the second version information corresponding to different query types can be displayed on different data display interfaces; the method and the device have the advantages that the version information matched with the query instruction is obtained, meanwhile, the version information can be updated in real time according to the change of the iteration progress, the real-time obtaining of the version information corresponding to the target application program is guaranteed, and the real-time monitoring of the iteration progress is further realized.
As shown in fig. 1C, optionally, in the embodiment of the present invention, after the second version information is obtained, the obtained second version information may be displayed in a graph form, and by displaying each data item of the second version information in the graph form, a more intuitive version iteration progress may be viewed; meanwhile, when the second version information is updated, the corresponding updates are synchronized to the display chart.
Optionally, in this embodiment of the present invention, after the filtering the first version information according to the query condition and outputting the second version information corresponding to the query type, the method may further include: updating a query data table which is locally stored and corresponds to each query type according to the second version information; and generating a version iteration report matched with the query condition according to the query data matched with the second version information in the query data table. The query data table is table-form query data stored in a local database; specifically, after the corresponding second version information is acquired according to the query instruction each time, the acquired second version information is stored in the local database in a table form to generate a corresponding query data table, and the query data table corresponds to the query type one to one.
Specifically, when the second version information is stored, the second version information which is obtained latest at present is adopted to update the locally stored historical query data corresponding to the current query type so as to obtain the updated query data table corresponding to each query type; further, query data matched with the query conditions, namely query data matched with the operation subject, the target application program and the query types in the query conditions, are obtained from the updated query data table, and the obtained query data are classified and summarized according to the query types to generate version iteration reports matched with the query conditions, so that a user can view the current iteration progress more intuitively. Fig. 1D is a schematic diagram of a version iteration report according to an embodiment of the present invention. Optionally, in this embodiment of the present invention, before generating the version iteration report, the method may further include: acquiring a remark information adding instruction corresponding to the current application program version, acquiring remark information to be added according to the remark information adding instruction, and adding the remark information to the version iteration report according to a matched export sequence; the remark information may include, among other things, potential risks and reporting problems. By adding remark information, version information which cannot be acquired through query can be added to the version iteration report, and the content of the version iteration report is enriched.
Optionally, in this embodiment of the present invention, the query type may include: the second version information corresponding to the demand query comprises a plurality of demand data items, and each demand data item is distinguished through a demand identifier; correspondingly, the updating the locally stored query data table corresponding to each query type according to the second version information may include: matching and searching in a locally stored requirement data table; if a stored data item consistent with the requirement identification of a first target requirement data item is stored in the requirement data table, updating the data value of the stored data item by using the first target requirement data item; and if the demand data table does not store the stored data item consistent with the demand identification of the second target demand data item, adding the second target demand data item to the query data table.
The demand data table is a query data table which is locally stored and corresponds to demand query; the target demand data item is a demand data item which needs to be stored to the local in the current second version information; correspondingly, the stored data item is a required data item which is contained in the query data table when the data storage operation is currently executed. Specifically, when the query type is a requirement query, the acquired second version information is a plurality of requirement data items; after the demand data items are acquired, in order to avoid the storage of repeated data, before the demand data items are stored, searching is carried out in a stored demand data table according to the acquired demand identification of each demand data item; if the stored data item consistent with the requirement identifier of the first target requirement data item is found, the current requirement identifier and the corresponding data value exist in the current requirement data table, and at the moment, the stored data value is replaced by the data value of the requirement data item to be stored so as to obtain the latest data value information; and if the consistent stored data item is not found in the locally stored demand data table according to the demand identification of the second target demand data item, directly extracting the demand identification of the second target demand data item and the corresponding data value and adding the demand identification and the corresponding data value into the local query data table. The stored data items are updated by adopting the currently acquired demand data items, so that the condition that the same demand identification corresponds to different data values is avoided, and the redundancy of the stored data is reduced.
Optionally, in this embodiment of the present invention, the adding the second target demand data item to the query data table may include: if the second target demand data item is determined to comprise a demand detail page, acquiring a domain name path of the demand detail page; generating a corresponding jump link of the demand detail page according to the demand identification of the second target demand data item and the domain name path of the demand detail page; and adding the jump link to a corresponding row of the second target demand data item in a demand data table. Specifically, if a consistent stored data item is not found in a locally stored demand data table according to a demand identifier of a second target demand data item, and it is determined that a current second target demand data item includes a demand detail page, a domain name path of the data detail page and the demand identifier of the current second target demand data item are obtained, the domain name path and the demand identifier are spliced according to a Uniform Resource Locator (URL) to obtain an access website of the current demand detail page, the access website is added to a corresponding row of the current second target demand data item in the demand data table, and a link between the access website and the demand identifier is established.
As shown in fig. 1E, by obtaining the jump link of the requirement detail page, when the corresponding second target requirement data item is displayed, by clicking the requirement identifier, the corresponding requirement detail page can be jumped to through the jump link corresponding to the second target requirement data item, so that the requirement detail page can be viewed; meanwhile, the recording of specific demand data of the demand detail page is avoided, and the data required to be stored is reduced.
Optionally, in this embodiment of the present invention, the query type may include: the second version information corresponding to the defect query and/or the test case query comprises a plurality of data tables; correspondingly, the updating the locally stored query data table corresponding to each query type according to the second version information may include: identifying the file format of each data table, acquiring a target data table meeting the requirement of a preset format, and adding the target data table to a local storage; searching matched data in a first row with data in the target data table according to a preset column name, and if the matched data is searched in the first row with data in the target data table according to the preset column name, acquiring position information of the matched data in the target data table; generating an index in a key-value pair form corresponding to the target data table according to the preset column name and the position information; and acquiring the matched defect data item and/or test case data item in the target data table according to the index, and updating the locally stored defect data table and/or test case data table according to the defect data item and/or test case data item.
As shown in fig. 1F, when the query type is a defect query and/or a test case query, the second version information obtained by the query at this time is a data table corresponding to the query type; correspondingly, the locally matched query data table is updated according to the data in the data table. Specifically, firstly, reading the table name of each data table, intercepting the ". multidot.to the last character content to obtain the file format of the table data table, matching and comparing the obtained file format with the preset format requirement, and taking the data table passing through matching and comparison as a target data table; the preset format requirements comprise XLS and XLSX.
Further, after the target data table is obtained, the target data table is stored in a local database, a blank MAP mapping is established, and a preset column name is added to the blank MAP mapping as a key value; sequentially searching whether table data matched with a preset column name exists in a first row with data in the target data table from left to right; if the table data matched with the preset column name is not found in the target data table, the currently acquired target data table is invalid, and the current target data table is deleted from the local database, so that the occupation of the invalid data table on the local storage space is avoided.
If the matched table data is found in the target data table, recording the position information of the currently matched table data in the target data table, and adding the position information into the MAP mapping as a value of the MAP mapping; the MAP is a data structure type, wherein data exists in a key/value pair form. Taking the obtained MAP mapping as an index of the current target data table, and obtaining matched table data according to the index at the corresponding position in the target data table when the data of the current target data table needs to be read subsequently; by recording the position information of the matched table data instead of the specific data value, the table data of the corresponding position after updating can be read in real time when the corresponding data value is updated.
In addition, after table data matched with the preset column name is obtained, a query data table corresponding to a locally stored query type is updated according to the obtained table data so as to obtain an updated defect data table and a test case data table; the manner of updating the query data table corresponding to the local storage according to the table data is consistent with the manner of updating the stored data item according to the first target required data item, and is not described herein again.
Optionally, in this embodiment of the present invention, after updating the locally stored query data table corresponding to each query type according to the second version information, the method may further include: acquiring version identifications corresponding to currently updated demand data items in a demand data table, and adding the version identifications to corresponding rows of matched demand data items; and acquiring a requirement identifier corresponding to each currently updated defect data item and/or test case data item in the defect data table and/or test case data table, and adding the requirement identifier to a corresponding row of the matched defect data item and/or test case data item.
Correspondingly, the generating a version iteration report matched with the query condition according to the query data matched with the second version information in the query data table may include: searching matched demand data items in a demand data table according to the version identification in the query condition, and searching matched defect data items and test case data items in a defect data table and a test case data table according to the demand identification of the demand data items; and generating a version iteration report matched with the query condition according to the demand data item, the defect data item and the test case data item.
Specifically, after each locally stored query data table is updated according to the second version information, the version identifier of the target application program corresponding to each required data item in the required data table is obtained, and the version identifier is added to the corresponding row of each required data item; and simultaneously acquiring the requirement identifications of the requirement data items corresponding to each defect data item and each test case data item in the defect data table and the test case data table, and adding the requirement identifications to corresponding rows of each data item. Further, when a version iteration report is generated, according to the version identification of the target application program, searching a matched demand data item in a locally stored demand data table; respectively acquiring matched defect data items and test case data items from the defect data table and the test case data table according to the requirement identification of the matched requirement data item; and then, the obtained data items are classified and counted to obtain a version iteration report corresponding to the current version identification, so that the automatic obtaining of the version iteration report corresponding to the current query version of the target application program is realized, meanwhile, the version iteration report can be automatically updated according to the updating of the queried version information, and the obtaining of the iteration progress of the latest version is ensured.
The data items are classified and counted to obtain corresponding statistical parameters of all query types, and the statistical parameters corresponding to different query types can be consistent or inconsistent; typically, statistics is performed according to the data state of the defect data item, and the defect data is classified into closed data and non-closed data; further, the defect data are further classified into fatal, serious, general, prompt and suggestion according to the severity of the defect, and the corresponding quantity of each type of defect data is respectively counted; classifying according to the execution result of the test case data, dividing the test case data into pass, fail and non-execution, and respectively counting the number of each type of test case data. Meanwhile, generating a version iteration report according to the statistical result and a preset initial list; in the version iteration report, different pages can be adopted to display the statistical results of different data items.
Optionally, in this embodiment of the present invention, after generating the version iteration report matching the query condition according to the query data matching the second version information in the query data table, the method may further include: acquiring a preset mail template, acquiring user information of a target user, generating a target mail based on the preset mail template according to the user information and the version iteration report, and sending the target mail to the target user. Specifically, after the iteration progress report is obtained, the version iteration report is sent to a target user for viewing in a mail mode; the target users may include version iteration developers, demanders, production personnel, and testers, among others. Typically, fig. 1G is a schematic diagram of a target email provided in the embodiment of the present invention, where a preset email template and user information of a target user are obtained from a local database, and a target email is generated and sent to the target user in combination with an obtained version iteration report, so that the target user obtains an iteration progress report.
According to the technical scheme provided by the embodiment of the invention, the access path corresponding to the query instruction is obtained in response to the query instruction of the version information; calling a database interface of at least one target application program corresponding to the operation subject according to the access path to acquire first version information of the target application program recorded in real time; meanwhile, according to the query instruction, confirming the corresponding query type; the first version information is screened according to the query condition in the query instruction, and the second version information corresponding to the query type is output, so that the automatic acquisition of the version information of the cross-operation main body and the cross-target application program is realized, the condition that a user accesses a database of the operation main body one by one to acquire and summarize the version information is avoided, the time spent is reduced, and the version information acquisition efficiency is improved; meanwhile, the second version information is obtained by obtaining the first version information recorded in real time and then screening, so that the real-time updating of the second version information is realized.
Example two
Fig. 2A is a flowchart of a version information generating method according to a second embodiment of the present invention, which is embodied on the basis of the foregoing embodiment, in this embodiment, a query data table is updated according to acquired second version information, and a version iteration report corresponding to a query condition is generated according to query data matched in the query data table, where the method specifically includes:
s210, responding to a query instruction of the version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction.
S220, calling a database interface of at least one target application program corresponding to the operation subject according to the access path, and acquiring first version information of the target application program recorded in real time.
S230, confirming a corresponding query type according to the query instruction; the query type includes at least one of: requirement query, version iteration query, defect query and test case query.
S240, screening the first version information according to the query conditions, and outputting second version information corresponding to the query type.
And S250, updating a query data table which is locally stored and corresponds to each query type according to the second version information.
And S260, generating a version iteration report matched with the query condition according to the query data matched with the second version information in the query data table.
Fig. 2B is a flowchart illustrating a method for generating version information according to an embodiment of the present invention; acquiring version identification information of the target application program, such as date, name and the like, acquiring a database access path of the target application program according to the query instruction, and acquiring demand data corresponding to the target application program by calling an interface of the database; the demand data can come from a database of a management platform (such as TAPD and Zen channel) corresponding to each operation subject, specifically, a demand identifier and a jump link of the demand data are obtained, and the demand data can jump to a corresponding demand detail page through the current jump link; meanwhile, version information corresponding to defect query and test case query is obtained, information such as column names of tables needing to be uploaded is configured for the obtained data table, the target data table with the matching data is stored in a local database, and the matching data is stored under the matching requirement identification in an associated mode; after the acquisition of the required data, the defect data, the version iteration data and the test case data is completed, adding information such as online risks, legacy problems and the like corresponding to the iteration version of the target application program to generate an iteration progress report corresponding to the query instruction, and sending the iteration progress report in a mail mode; the mail format, such as color, font size, body and recipient information, can be pre-configured and sent without manual filling.
According to the technical scheme provided by the embodiment of the invention, after the second version information of the query type is acquired according to the query condition, the query data table stored locally is updated according to the second version information, and the version iteration report matched with the query condition is generated according to the query data matched with the second version information in the query data table, so that the acquisition of the version information of the cross-operation main body and the cross-application program is realized; meanwhile, a corresponding version iteration report is generated according to the acquired version information, so that a user can more visually check the iteration progress corresponding to each target application program, and the iteration progress is conveniently monitored and adjusted.
EXAMPLE III
Fig. 3 is a block diagram of a structure of a device for generating version information according to a third embodiment of the present invention, where the device specifically includes: an access path obtaining module 310, a first version information obtaining module 320, a query type determining module 330, and a second version information obtaining module 340;
an access path obtaining module 310, configured to, in response to a query instruction of the version information, obtain an access path corresponding to the query instruction; at least one query condition included in the query instruction;
a first version information obtaining module 320, configured to call, according to the access path, a database interface of at least one target application corresponding to the operation subject, and obtain first version information of the target application recorded in real time;
a query type determining module 330, configured to determine a corresponding query type according to the query instruction; the query type includes at least one of: the method comprises the following steps of demand query, version iteration query, defect query and test case query;
the second version information obtaining module 340 is configured to filter the first version information according to the query condition, and output second version information corresponding to the query type.
According to the technical scheme provided by the embodiment of the invention, the access path corresponding to the query instruction is obtained in response to the query instruction of the version information; calling a database interface of at least one target application program corresponding to the operation subject according to the access path to acquire first version information of the target application program recorded in real time; meanwhile, according to the query instruction, confirming the corresponding query type; the first version information is screened according to the query condition in the query instruction, and the second version information corresponding to the query type is output, so that the automatic acquisition of the version information of the cross-operation main body and the cross-target application program is realized, the condition that a user accesses a database of the operation main body one by one to acquire and summarize the version information is avoided, the time spent is reduced, and the version information acquisition efficiency is improved; meanwhile, the second version information is obtained by obtaining the first version information recorded in real time and then screening, so that the real-time updating of the second version information is realized.
Optionally, on the basis of the foregoing technical solution, the access path obtaining module 310 is specifically configured to extract an operation subject included in the query instruction and at least one target application program matched with the operation subject; and generating at least one access path according to the operation main body and each target application program.
Optionally, on the basis of the foregoing technical solution, the apparatus for generating version information further includes:
the data table updating module is used for updating the query data tables which are locally stored and correspond to the query types according to the second version information;
and the report generation module is used for generating a version iteration report matched with the query condition according to the query data matched with the second version information in the query data table.
Optionally, on the basis of the above technical solution, the query type includes: the second version information corresponding to the demand query comprises a plurality of demand data items, and each demand data item is distinguished through a demand identifier; a data table update module comprising:
the data table searching unit is used for performing matching searching in a locally stored demand data table;
a data value updating unit, configured to update a data value of a stored data item using a first target demand data item if the demand data table stores the stored data item that is consistent with a demand identifier of the first target demand data item;
and the data item adding unit is used for adding a second target demand data item into the query data table if the demand data table does not store a stored data item consistent with the demand identification of the second target demand data item.
Optionally, on the basis of the above technical solution, the data item adding unit is specifically configured to, if it is determined that the second target demand data item includes a demand detail page, obtain a domain name path of the demand detail page; generating a corresponding jump link of the demand detail page according to the demand identification of the second target demand data item and the domain name path of the demand detail page; and adding the jump link to a corresponding row of the second target demand data item in a demand data table.
Optionally, on the basis of the above technical solution, the query type includes: the second version information corresponding to the defect query and/or the test case query comprises a plurality of data tables; a data table update module comprising:
the format identification unit is used for identifying the file format of each data table, acquiring a target data table meeting the requirement of a preset format, and adding the target data table to a local storage;
the position information acquisition unit is used for searching matched data in the first line with data in the target data table according to a preset column name, and acquiring the position information of the matched data in the target data table if the matched data is searched in the first line with data in the target data table according to the preset column name;
the index generating unit is used for generating an index in a key value pair form corresponding to the target data table according to the preset column name and the position information;
and the first matching data item acquisition unit is used for acquiring the matched defect data item and/or test case data item in the target data table according to the index and updating the locally stored defect data item and/or test case data table according to the defect data item and/or test case data item.
Optionally, on the basis of the foregoing technical solution, the apparatus for generating version information further includes:
the version identification acquisition module is used for acquiring the version identification corresponding to each currently updated demand data item in the demand data table and adding each version identification to the corresponding row of the matched demand data item;
and the requirement identifier acquisition module is used for acquiring requirement identifiers corresponding to each currently updated defect data item and/or test case data item in the defect data table and/or the test case data table, and adding the requirement identifiers to corresponding rows of the matched defect data items and/or test case data items.
Optionally, on the basis of the above technical solution, the report generating module includes:
the second matching data item acquisition unit is used for searching a matching demand data item in a demand data table according to the version identification in the query condition, and searching a matching defect data item and a matching test case data item in a defect data table and a test case data table according to the demand identification of the demand data item;
and the report generating unit is used for generating a version iteration report matched with the query condition according to the demand data item, the defect data item and the test case data item.
The device can execute the generation method of the version information provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method. For technical details not described in detail in this embodiment, reference may be made to the method provided in any embodiment of the present invention.
Example four
Fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 4 is only an example and should not bring any limitation to the function and the scope of use of the embodiment of the present invention.
As shown in FIG. 4, electronic device 12 is embodied in the form of a general purpose computing device. The components of electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 that couples various system components including the memory 28 and the processing unit 16.
The memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, and commonly referred to as a "hard drive"). Although not shown in FIG. 4, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
The processing unit 16 executes various functional applications and data processing by running a program stored in the memory 28, for example, implementing a generation method of version information provided by any of the embodiments of the present invention. Namely: responding to a query instruction of the version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction; calling a database interface of at least one target application program corresponding to the operation subject according to the access path to acquire first version information of the target application program recorded in real time; confirming a corresponding query type according to the query instruction; the query type includes at least one of: the method comprises the following steps of demand query, version iteration query, defect query and test case query; and screening the first version information according to the query condition, and outputting second version information corresponding to the query type.
EXAMPLE five
Fifth, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a method for generating version information according to any embodiment of the present invention; the method comprises the following steps:
responding to a query instruction of the version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction;
calling a database interface of at least one target application program corresponding to the operation subject according to the access path to acquire first version information of the target application program recorded in real time;
confirming a corresponding query type according to the query instruction; the query type includes at least one of: the method comprises the following steps of demand query, version iteration query, defect query and test case query;
and screening the first version information according to the query condition, and outputting second version information corresponding to the query type.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A method for generating version information, comprising:
responding to a query instruction of the version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction;
calling a database interface of at least one target application program corresponding to the operation subject according to the access path to acquire first version information of the target application program recorded in real time;
confirming a corresponding query type according to the query instruction; the query type includes at least one of: the method comprises the following steps of demand query, version iteration query, defect query and test case query;
and screening the first version information according to the query condition, and outputting second version information corresponding to the query type.
2. The method of claim 1, wherein the obtaining, in response to the query instruction of the version information, the access path corresponding to the query instruction comprises:
extracting an operation main body included in the query instruction and at least one target application program matched with the operation main body;
and generating at least one access path according to the operation main body and each target application program.
3. The method of claim 1, further comprising, after filtering the first version information according to the query condition and outputting second version information corresponding to the query type:
updating a query data table which is locally stored and corresponds to each query type according to the second version information;
and generating a version iteration report matched with the query condition according to the query data matched with the second version information in the query data table.
4. The method of claim 3, wherein the query type comprises: the second version information corresponding to the demand query comprises a plurality of demand data items, and each demand data item is distinguished through a demand identifier;
the updating the query data table corresponding to each query type stored locally according to the second version information includes:
matching and searching in a locally stored requirement data table;
if a stored data item consistent with the requirement identification of a first target requirement data item is stored in the requirement data table, updating the data value of the stored data item by using the first target requirement data item;
and if the demand data table does not store the stored data item consistent with the demand identification of the second target demand data item, adding the second target demand data item to the query data table.
5. The method of claim 4, wherein the adding the second target demand data item to the lookup data table comprises:
if the second target demand data item is determined to comprise a demand detail page, acquiring a domain name path of the demand detail page;
generating a corresponding jump link of the demand detail page according to the demand identification of the second target demand data item and the domain name path of the demand detail page;
and adding the jump link to a corresponding row of the second target demand data item in a demand data table.
6. The method of claim 3, wherein the query type comprises: the second version information corresponding to the defect query and/or the test case query comprises a plurality of data tables;
the updating the query data table corresponding to each query type stored locally according to the second version information includes:
identifying the file format of each data table, acquiring a target data table meeting the requirement of a preset format, and adding the target data table to a local storage;
searching matched data in a first row with data in the target data table according to a preset column name, and if the matched data is searched in the first row with data in the target data table according to the preset column name, acquiring position information of the matched data in the target data table;
generating an index in a key-value pair form corresponding to the target data table according to the preset column name and the position information;
and acquiring the matched defect data item and/or test case data item in the target data table according to the index, and updating the locally stored defect data table and/or test case data table according to the defect data item and/or test case data item.
7. The method according to claim 3, further comprising, after updating the locally stored query data table corresponding to each of the query types according to the second version information:
acquiring version identifications corresponding to currently updated demand data items in a demand data table, and adding the version identifications to corresponding rows of matched demand data items;
acquiring a requirement identifier corresponding to each currently updated defect data item and/or test case data item in a defect data table and/or a test case data table, and adding the requirement identifier to a corresponding row of the matched defect data item and/or test case data item;
generating a version iteration report matched with the query condition according to the query data matched with the second version information in the query data table, wherein the generation comprises the following steps:
searching matched demand data items in a demand data table according to the version identification in the query condition, and searching matched defect data items and test case data items in a defect data table and a test case data table according to the demand identification of the demand data items;
and generating a version iteration report matched with the query condition according to the demand data item, the defect data item and the test case data item.
8. An apparatus for generating version information, comprising:
the access path acquisition module is used for responding to a query instruction of the version information and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction;
the first version information acquisition module is used for calling a database interface of at least one target application program corresponding to the operation subject according to the access path and acquiring the first version information of the target application program recorded in real time;
the query type determining module is used for determining the corresponding query type according to the query instruction; the query type includes at least one of: the method comprises the following steps of demand query, version iteration query, defect query and test case query;
and the second version information acquisition module is used for screening the first version information according to the query conditions and outputting second version information corresponding to the query type.
9. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of generating version information as claimed in any one of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of generating version information according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110469150.7A CN113010208B (en) | 2021-04-28 | 2021-04-28 | Version information generation method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110469150.7A CN113010208B (en) | 2021-04-28 | 2021-04-28 | Version information generation method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113010208A true CN113010208A (en) | 2021-06-22 |
| CN113010208B CN113010208B (en) | 2023-12-19 |
Family
ID=76380436
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110469150.7A Active CN113010208B (en) | 2021-04-28 | 2021-04-28 | Version information generation method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113010208B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113918209A (en) * | 2021-12-16 | 2022-01-11 | 深圳市明源云科技有限公司 | Method and device for generating upgrade list and readable storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5504879A (en) * | 1992-07-16 | 1996-04-02 | International Business Machines Corporation | Resolution of relationship source and target in a versioned database management system |
| CN107657171A (en) * | 2017-09-11 | 2018-02-02 | 郑州云海信息技术有限公司 | A kind of method in SSR centralized management platform management application programs |
| CN108279924A (en) * | 2018-01-30 | 2018-07-13 | 北京小米移动软件有限公司 | Program dissemination method and device |
| CN111124474A (en) * | 2018-10-31 | 2020-05-08 | 北京数聚鑫云信息技术有限公司 | API version control method and device |
| CN111428117A (en) * | 2019-01-09 | 2020-07-17 | 百度在线网络技术（北京）有限公司 | Data acquisition method and device for application program |
| CN112307515A (en) * | 2020-11-27 | 2021-02-02 | 北京锐安科技有限公司 | Database-based data processing method and device, electronic equipment and medium |
| US20210081217A1 (en) * | 2018-03-27 | 2021-03-18 | Huawei Technologies Co., Ltd. | Resource permission processing method and apparatus, storage medium, and chip |
| CN112685474A (en) * | 2020-12-30 | 2021-04-20 | 北京联创信安科技股份有限公司 | Application management method, device, equipment and storage medium |
-
2021
- 2021-04-28 CN CN202110469150.7A patent/CN113010208B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5504879A (en) * | 1992-07-16 | 1996-04-02 | International Business Machines Corporation | Resolution of relationship source and target in a versioned database management system |
| CN107657171A (en) * | 2017-09-11 | 2018-02-02 | 郑州云海信息技术有限公司 | A kind of method in SSR centralized management platform management application programs |
| CN108279924A (en) * | 2018-01-30 | 2018-07-13 | 北京小米移动软件有限公司 | Program dissemination method and device |
| US20210081217A1 (en) * | 2018-03-27 | 2021-03-18 | Huawei Technologies Co., Ltd. | Resource permission processing method and apparatus, storage medium, and chip |
| CN111124474A (en) * | 2018-10-31 | 2020-05-08 | 北京数聚鑫云信息技术有限公司 | API version control method and device |
| CN111428117A (en) * | 2019-01-09 | 2020-07-17 | 百度在线网络技术（北京）有限公司 | Data acquisition method and device for application program |
| CN112307515A (en) * | 2020-11-27 | 2021-02-02 | 北京锐安科技有限公司 | Database-based data processing method and device, electronic equipment and medium |
| CN112685474A (en) * | 2020-12-30 | 2021-04-20 | 北京联创信安科技股份有限公司 | Application management method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 孙德刚;: "基于SVN版本控制的教务信息管理系统开发与实现", 现代信息科技, no. 11, pages 106 - 108 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113918209A (en) * | 2021-12-16 | 2022-01-11 | 深圳市明源云科技有限公司 | Method and device for generating upgrade list and readable storage medium |
| CN113918209B (en) * | 2021-12-16 | 2022-04-15 | 深圳市明源云科技有限公司 | Method and device for generating upgrade list and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113010208B (en) | 2023-12-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108959564B (en) | Data warehouse metadata management method, readable storage medium and computer device | |
| US20200201699A1 (en) | Unified error monitoring, alerting, and debugging of distributed systems | |
| US20070234306A1 (en) | Tracing performance of machine-readable instructions | |
| CN113360519B (en) | Data processing method, device, equipment and storage medium | |
| CN114385763A (en) | Data blood margin analysis method, device and system and readable storage medium | |
| CN108345658B (en) | Decomposition processing method of algorithm calculation track, server and storage medium | |
| CN111414410A (en) | Data processing method, device, equipment and storage medium | |
| CN112395333A (en) | Method and device for checking data exception, electronic equipment and storage medium | |
| CN111767574A (en) | User permission determining method and device, electronic equipment and readable storage medium | |
| US20090070743A1 (en) | System and method for analyzing software applications | |
| CN115357590A (en) | Recording method and device for data change, electronic device and storage medium | |
| CN113010208B (en) | Version information generation method, device, equipment and storage medium | |
| CN111737148A (en) | Automatic regression testing method and device, computer equipment and storage medium | |
| US20090063578A1 (en) | Management of data needed to resolve pointer errors in heirarchical database management systems | |
| CN111444099A (en) | Data inconsistency analysis method, system, electronic device and storage medium | |
| CN110889013A (en) | Data association method, device, server and storage medium based on XML | |
| CN112835779A (en) | Test case determination method and device and computer equipment | |
| CN116303427A (en) | Data processing method and device, electronic equipment and storage medium | |
| US10664501B2 (en) | Deriving and interpreting users collective data asset use across analytic software systems | |
| CN112162954B (en) | User operation log generation and path positioning method, device, equipment and medium | |
| CN115033639A (en) | Method and related device for generating relation graph for data sharing among clusters | |
| CN111368039B (en) | Data management system | |
| US9275358B1 (en) | System, method, and computer program for automatically creating and submitting defect information associated with defects identified during a software development lifecycle to a defect tracking system | |
| CN109977104B (en) | Data management method and device | |
| CN113138906A (en) | Call chain data acquisition 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |