CN113010208B - Version information generation method, device, equipment and storage medium - Google Patents
Version information generation method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113010208B CN113010208B CN202110469150.7A CN202110469150A CN113010208B CN 113010208 B CN113010208 B CN 113010208B CN 202110469150 A CN202110469150 A CN 202110469150A CN 113010208 B CN113010208 B CN 113010208B
- Authority
- CN
- China
- Prior art keywords
- query
- version information
- data
- data table
- version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
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 inquiry instruction of the version information, and acquiring an access path corresponding to the inquiry instruction; according to the access path, calling a database interface of at least one target application program corresponding to the operation main body, and acquiring first version information of the target application program recorded in real time; confirming the 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 realized, the situation that users access the database of the operation main body one by one to collect and summarize the version information is avoided, the time spent for 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 quick iterative products, when the research and development capability of enterprises cannot meet the current project requirements in consideration of factors such as update period, labor cost and technical reasons, the corresponding technical service needs to be purchased to generate new versions of iterative products so as to support the updating of the products and the maintenance of user groups.
When a large platform system iterates for one version, a plurality of projects are involved for common iteration release, a project management tool is used for management in a research and development process, and different projects are researched and developed by personnel of different companies, so that each project is provided with an independent project management tool, authority data are independent of each other, and record and summary of cross-company and cross-project version information cannot be realized. For 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 realizing the invention, the inventor finds that: the existing project management tools for version iteration divide authorities according to companies and projects, record, check and summarize one by one project manually, time and cost are wasted seriously, efficiency is low, and a unified iteration progress report cannot be generated at the same time so as to know the iteration progress of each project 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 so as to realize automatic acquisition of 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, including:
responding to a query instruction of version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction;
according to the access path, calling a database interface of at least one target application program corresponding to an operation main body, and acquiring first version information of the target application program recorded in real time;
according to the query instruction, confirming a corresponding query type; the query types include at least one of: demand query, version iteration query, defect query, and test case query;
and screening the first version information according to the query conditions, and outputting second version information corresponding to the query type.
In a second aspect, an embodiment of the present invention provides a version information generating apparatus, including:
the access path acquisition module is used for responding to the inquiry instruction of the version information and acquiring an access path corresponding to the inquiry 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 main body according to the access path to acquire 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 types include at least one 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 types.
In a third aspect, an embodiment of the present invention further provides an electronic device, including:
one or more processors;
a 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 method for generating version information according to any embodiment of the present invention.
In a fourth aspect, an embodiment of the present invention further provides a computer readable storage medium, where a computer program is stored, where the program when executed by a processor implements a 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 inquiry instruction is obtained in response to the inquiry instruction of the version information; according to the access path, invoking a database interface of at least one target application program corresponding to the operation main body 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; according to the query conditions in the query instruction, the first version information is screened, the second version information corresponding to the query type is output, automatic acquisition of version information of the cross-operation main body and the cross-target application program is realized, acquisition and summarization of version information by users accessing the database of the operation main body one by one are avoided, the time spent is reduced, and the version information acquisition efficiency is improved; meanwhile, the first version information recorded in real time is obtained, and then the second version information is obtained through screening, so that the real-time updating of the second version information is realized.
Drawings
Fig. 1A is a flowchart of a method for generating version information according to a first 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 version information display diagram showing intent provided in accordance with one embodiment of the present invention;
FIG. 1D is a schematic diagram of an iteration schedule report according to a first embodiment of the present invention;
FIG. 1E is a diagram illustrating a data detail page jump provided in accordance with a first embodiment of the present invention;
FIG. 1F is a diagram of a table for obtaining iteration information data according to a first embodiment of the present invention;
FIG. 1G is a schematic diagram of a target mail according to a first embodiment of the present invention;
fig. 2A is a flowchart of a method for generating version information according to a second embodiment of the present invention;
fig. 2B is a flowchart of a method for generating version information according to a second embodiment of the present invention;
fig. 3 is a block diagram of a version information generating 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 have been shown in the accompanying 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 are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present 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. Furthermore, 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 "including" and variations thereof as used herein are intended to be 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. Related definitions of other terms will be given in the description below.
It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.
It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.
The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.
Example 1
Fig. 1A is a flowchart of a version information generation method according to a first embodiment of the present invention, where the embodiment may be adapted to automatically query and summarize version information of a cross-operator and a cross-application in a version iteration process; the method may be performed by version information generating means, which may be implemented in software and/or hardware and integrated on an electronic device, typically in a server and a terminal device, the method comprising in particular the steps of:
s110, responding to a query instruction of version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction.
Version information, which is data information submitted by each participating developer aiming at different application programs in a version iteration process, can comprise a functional test case, discovered defects, performance test results, issued legacy problems, online risks and the like; the problems existing in the version iteration process of the current application program and the corresponding processing modes can be obtained through the version information; furthermore, version iteration progress corresponding to the current application program can be known in real time by counting and summarizing version information of each company corresponding to the current application program, and further, the version iteration of the current application program can be controlled and adjusted according to the current progress and development cycle.
The version iteration is to upgrade and update the version of the application program according to a fixed development period; the iteration is a fixed-cycle development rhythm, and the version is the yield actually delivered to the user. In practice, a version delivered to a user may include multiple iterations, i.e., generating an upgraded version over multiple development cycles for submission to the user; an iteration may also include multiple versions, i.e., multiple upgraded versions are submitted to the user during a development cycle; for the two cases, 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. Embodiments of the present invention are not particularly limited with respect to the relationship of version and iteration.
The query instruction is a data query command aiming at version information and consists of a plurality of query conditions; by acquiring the query instruction of the user, iteration information of different companies aiming at different application programs is automatically searched, and then version information meeting query conditions is automatically returned, so that automatic acquisition of the version information corresponding to the specific application program can be realized. The query condition is condition information for searching version information, and may include an operation subject, a target application program, a data type and creation information (such as creation date and creator) of the data to be queried; in particular, the user may input different query conditions on 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 implement query and acquisition of version information according to multiple query conditions. In the embodiment of the present invention, the content of the query condition is not particularly limited.
An access path is an access path of a database where query data corresponding to the query instruction are located; optionally, in an embodiment of the present invention, the obtaining, in response to a query instruction of version information, an access path corresponding to the query instruction may include: extracting 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. The operation main body is a company participating in the iteration of the current application program version; the target application program is an application program needing to inquire the corresponding version information, and comprises an identification of the application program and a version identification. Specifically, after a query instruction input by a user is obtained, the query instruction is analyzed to obtain an operation main body and a target application program corresponding to the current operation main body; searching matched storage data in a local database according to an operation main body and a 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 among an operation main body, an application program and an access path is obtained in advance, and the mapping relationship is stored in a local database; one operation main body corresponds to a plurality of application programs, and version iteration data corresponding to each application program is stored in a separate database; through a pre-configured mapping relation, the matched access path can be quickly acquired according to the query condition, and further the efficiency of version information acquisition 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" and the identifier of the operation subject in the mapping relationship in the local database is "hua is a technical company, then a comparison relationship between the operation subject in the local database and the common name or the abbreviated name thereof can be pre-established, so as to realize the acquisition of the access path corresponding to the current operation subject name when the incomplete operation subject name in the query condition is acquired.
S120, calling a database interface of at least one target application program corresponding to the operation main body according to the access path, and acquiring the first version information of the target application program recorded in real time.
The method comprises the steps that a management platform is adopted to monitor and manage version iterations of different application programs for different operation subjects; the management platform may specifically include a Tencentrated agile product development platform (Tencent Agile Product Development, TAPD); the TAPD platform is used for acquiring version information of different application programs uploaded by developers of each operation main body, so that tracking of iteration progress of each application program version, management of task man-hour and tracking management of defect problems can be realized. In particular, different companies participating in the iteration of the current version can correspond to different management platforms, further, different application programs in charge of the same operation main body correspond to different groups in the management platforms, and version information of the different operation main bodies aiming at the different application programs is stored in independent databases; version information among different management platforms and among different groups of the same management platform cannot be shared, so that grouping management of different application programs can be realized, and leakage of the version information is avoided. As shown in fig. 1B, according to the obtained query conditions, the first version information corresponding to the multiple target applications can be obtained through the matched access paths, so that the simultaneous query and obtaining of the first version information corresponding to the multiple target applications can be realized, and the obtaining efficiency of the version information is improved.
A database interface, an access interface for a database; typically, the database interface may specifically include an application program interface (Application Programming Interface, API) which is a convention for the engagement of the various components of the software system, through which an application developer may access a set of routines without having to access their source code and understand the details of the internal operating 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 the RestTemplite 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 main body and the target application program in the database can be automatically obtained, the normal version iteration work of each target application program is not influenced, and the influence of version information query on the version iteration process is avoided. Wherein, the RestTemplite is a data request tool based on a hypertext transfer protocol.
The first version information is all data iteratively related to the version of the target application program; specifically, after the access path corresponding to the query instruction is obtained, the database corresponding to the target application program is accessed through the obtained access path, and all stored data matched with the version identification of the target application program in the database is searched through an interface of the database, so that the first version information is obtained, and the cross-operation main body and cross-application program version information is obtained. Meanwhile, by acquiring the first version information recorded in real time in the database, the first version information can be updated in real time, namely, the matched version information newly submitted by a developer can be acquired in real time, and further, the iteration progress of the target application program can be acquired in real time.
S130, confirming a corresponding query type according to the query instruction; the query types include at least one of: a requirement query, a version iteration query, a defect query, and a test case query.
Specifically, after the first version information of the target application program is obtained, the user may input a corresponding query condition (for example, date) on the new query interface, and send a corresponding query instruction according to the query condition, so as to determine the current query type; the query types comprise a demand query, a version iteration query, a defect query and a test case query; and screening the first version information updated in real time according to the query type in the query instruction to obtain screening data matched with the query type.
And 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 obtained by screening the first version information according to the query condition; specifically, after determining the query type according to the query instruction, screening the acquired first version information updated in real time according to the query type to acquire the first version information matched with the query type as second version information; further, after the second version information corresponding to the query type is obtained, displaying the obtained second version information 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 realize the acquisition of the version information matched with the query instruction, simultaneously update the version information in real time according to the change of the iteration progress, ensure the real-time acquisition of the version information corresponding to the target application program, and further realize the real-time monitoring of the iteration progress.
As shown in fig. 1C, optionally, in the embodiment of the present invention, after the second version information is acquired, the acquired second version information may be displayed in a chart form, and by displaying each data item of the second version information in a chart form, it is known that the version iteration progress is more intuitively checked; meanwhile, when the second version information generates the update, the corresponding update is synchronized to the display chart.
Optionally, in an embodiment of the present invention, after screening the first version information according to the query condition and outputting the second version information corresponding to the query type, the method further includes: updating a query data table corresponding to each query type stored locally 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 query data in a table form stored in the local database; specifically, after the corresponding second version information is obtained according to the query instruction, the obtained second version information is stored in the local database according to a table form to generate a corresponding query data table, and the query data table corresponds to the query types one by one.
Specifically, when the second version information is stored, the currently latest acquired second version information is adopted to update the locally stored historical query data corresponding to the current query type so as to acquire a query data table corresponding to each updated query type; further, query data matched with the query condition, namely, query data matched with an operation main body, a target application program and a query type in the query condition are obtained in the updated query data table, and the obtained query data are classified and summarized according to the query type so as to generate a version iteration report matched with the query condition, so that a user can more intuitively check the current iteration progress. FIG. 1D is a schematic diagram of a version of an iteration report provided by an embodiment of the present invention. Optionally, in an embodiment of the present invention, before generating the version iteration report, the method may further include: the method comprises the steps of obtaining remark information adding instructions corresponding to a current application program version, obtaining remark information to be added according to the remark information adding instructions, and adding the remark information to a version iteration report according to a matched export sequence; the remark information may include, among other things, potential risks and reporting issues. By adding remark information, version information which cannot be obtained through inquiry can be added to the version iteration report, and the content of the version iteration report is enriched.
Optionally, in an embodiment of the present invention, the query types may include: the second version information corresponding to the demand inquiry comprises a plurality of demand data items, and each demand data item is distinguished by a demand identifier; correspondingly, 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 demand data table; if the stored data item consistent with the requirement identification of the 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 stored data item consistent with the requirement identification of the second target requirement data item is not stored in the requirement data table, adding the second target requirement data item into the query data table.
The demand data table is a locally stored query data table corresponding 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 refers to the required data item contained in the 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, searching in a stored demand data table according to the demand identifiers of the acquired demand data items before the demand data items are stored in order to avoid the storage of repeated data; if the stored data item consistent with the demand identifier of the first target demand data item is found, the current demand identifier and the corresponding data value exist in the current demand data table, and the stored data value is replaced by the data value of the demand data item to be stored at the moment so as to acquire the latest data value information; 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, the demand identification of the second target demand data item and the corresponding data value are directly extracted and added into the local query data table. By updating the stored data item by adopting the currently acquired demand data item, the situation that the same demand identifier corresponds to different data values is avoided, and the redundancy of the stored data is reduced.
Optionally, in an embodiment of the present invention, adding the second target requirement data item to the lookup data table may include: if the second target requirement data item comprises a requirement detail page, acquiring a domain name path of the requirement detail page; generating a corresponding jump link with the requirement detail page according to the requirement identification of the second target requirement data item and the domain name path of the requirement detail page; and adding the jump link to a corresponding row of the second target demand data item in the demand data table. Specifically, if a consistent stored data item is not found in the locally stored demand data table according to the demand identifier of the second target demand data item, and meanwhile, a demand detail page is determined to be included in the current second target demand data item, a domain name path of the data detail page and the demand identifier of the current second target demand data item are obtained, splicing the domain name path and the demand identifier according with a uniform resource locator (Uniform Resource Locator, URL) is performed 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 acquiring the jump link of the requirement detail page, when the corresponding second target requirement data item is displayed, by clicking the requirement identifier, the user can jump to the corresponding requirement detail page through the jump link corresponding to the second target requirement data item, so as to realize the view of the requirement detail page; meanwhile, recording of specific demand data of the demand detail page is avoided, and data needing to be stored is reduced.
Optionally, in an embodiment of the present invention, the query types may include: the second version information corresponding to the defect inquiry and/or the test case inquiry comprises a plurality of data tables; correspondingly, 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, obtaining 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 the position information of the matched data in the target data table; generating an index in the form of a key value pair corresponding to the target data table according to the preset column name and the position information; and according to the index, acquiring the matched defect data item and/or test case data item from the target data table, 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.
When the query type is a defect query and/or a test case query, as shown in fig. 1F, the second version information obtained by the query 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 names of all data tables, and intercepting the 'number' to the last character content to obtain the file format of the data table, carrying out matching comparison on the obtained file format and the preset format requirement, and taking the data table passing the matching comparison as a target data table; wherein the preset format requirements include XLS and XLSX.
Further, after the target data table is obtained, the target data table is stored in a local database, a blank MAP MAP is established, and a preset column name is added into the blank MAP MAP as a key value; searching whether form data matched with a preset column name exist in a first row of data in a target data table sequentially 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 occupation of the local storage space by the invalid data table 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, in which data exists in key/value key pairs. Taking the obtained MAP mapping as an index of a current target data table, and obtaining matched table data at a corresponding position in the target data table according to the index when the current target data table is required to be read in the follow-up process; 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 the table data matched with the preset column name is obtained, updating a query data table corresponding to the query type stored locally according to the obtained table data so as to obtain an updated defect data table and a test case data table; the method for updating the query data table corresponding to the local storage according to the table data is consistent with the method for updating the stored data item according to the first target demand data item, which is not described herein.
Optionally, in an 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: the method comprises the steps of obtaining version identifiers corresponding to all currently updated demand data items in a demand data table, and adding all the version identifiers to corresponding rows of matched demand data items; and obtaining the requirement identifiers corresponding to the defect data items and/or the test case data items which are updated currently in the defect data table and/or the test case data table, and adding the requirement identifiers to the corresponding rows of the matched defect data items and/or the test case data items.
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 requirement data item, the defect data item and the test case data item.
Specifically, after updating each query data table stored locally according to the second version information, the version identification of the target application program corresponding to each demand data item in the demand data table is obtained, and the version identification is added to the corresponding row of each demand data item; and simultaneously acquiring the requirement identifiers 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 identifiers to the corresponding rows of each data item. Further, when generating the version iteration report, searching a matched requirement data item in a locally stored requirement data table according to the version identification of the target application program; according to the requirement identification of the matched requirement data item, respectively acquiring the matched defect data item and test case data item from the defect data table and the test case data table; and further, classifying and counting the obtained data items to obtain a version iteration report corresponding to the current version identifier, so that the automatic acquisition of the version iteration report corresponding to the current query version of the target application program is realized, and meanwhile, the version iteration report can be automatically updated according to the update of the queried version information, and the acquisition of the latest version iteration progress is ensured.
Carrying out classified statistics on each data item to obtain corresponding statistical parameters of each query type, wherein the statistical parameters corresponding to different query types can be consistent or inconsistent; typically, statistics are performed according to the data states of the defect data items, and the defect data are classified into closed data and non-closed data; further, the defect data are further divided into deadly, serious, general, prompt and suggestion according to the severity of the defect, and the corresponding quantity of the defect data of each type is counted respectively; and classifying according to the execution result of the test case data, dividing the test case data into pass, fail and unexecuted, and respectively counting the quantity of the test case data of various types. 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 an embodiment of the present invention, after generating a version iteration report matching the query condition according to the query data matching the second version information in the query data table, the method further includes: 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 checking in a mail mode; the target user may include a version iteration developer, a demand person, a product person, and a tester, among others. Typically, fig. 1G is a schematic diagram of a target mail provided by the embodiment of the present invention, where a preset mail template and user information of a target user are obtained in a local database, and the obtained version iteration report is combined to generate a target mail, and the target mail is sent to the target user, so that the target user obtains the iteration progress report.
According to the technical scheme provided by the embodiment of the invention, the access path corresponding to the inquiry instruction is obtained in response to the inquiry instruction of the version information; according to the access path, invoking a database interface of at least one target application program corresponding to the operation main body 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; according to the query conditions in the query instruction, the first version information is screened, the second version information corresponding to the query type is output, automatic acquisition of version information of the cross-operation main body and the cross-target application program is realized, acquisition and summarization of version information by users accessing the database of the operation main body one by one are avoided, the time spent is reduced, and the version information acquisition efficiency is improved; meanwhile, the first version information recorded in real time is obtained, and then the second version information is obtained through 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, where the embodiment is implemented on the basis of the foregoing embodiment, and in this embodiment, a query data table is updated according to the 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 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 main body according to the access path, and acquiring the first version information of the target application program recorded in real time.
S230, confirming the corresponding query type according to the query instruction; the query types include at least one of: a requirement query, a version iteration query, a defect query, and a test case query.
S240, screening the first version information according to the query conditions, and outputting second version information corresponding to the query types.
S250, updating a query data table corresponding to each query type stored locally according to the second version information.
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 of a method for generating version information according to an embodiment of the present invention; the method comprises the steps of obtaining version identification information, such as date, name and the like, of a target application program, obtaining a database access path of the target application program according to a query instruction, and further obtaining demand data corresponding to the target application program by calling an interface of a database; the requirement data can come from databases of corresponding management platforms (e.g., TAPD and Buddhist channels) of each operation subject, specifically, the requirement identification and the jump link of the requirement data are obtained, and the corresponding requirement detail page can be jumped to through the current jump link; meanwhile, version information corresponding to defect inquiry and test case inquiry is obtained, information such as column names of tables to be uploaded is configured for the obtained data tables, a target data table with matching data is stored in a local database, and the matching data is associated and stored under a matched requirement identifier; after the acquisition of the demand 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, main body and recipient information, can be preconfigured, and the mail is 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 locally stored query data table 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; and meanwhile, a corresponding version iteration report is generated according to the acquired version information, so that a user can more intuitively check the iteration progress corresponding to each target application program, and the iteration progress can be conveniently monitored and adjusted.
Example III
Fig. 3 is a block diagram of a version information generating apparatus according to a third embodiment of the present invention, where the apparatus specifically includes: an access path acquisition module 310, a first version information acquisition module 320, a query type determination module 330, and a second version information acquisition module 340;
an access path obtaining module 310, configured to obtain an access path corresponding to a query instruction of version information in response to the query instruction; at least one query condition included in the query instruction;
a first version information obtaining module 320, configured to invoke a database interface of at least one target application program corresponding to an operation subject according to the access path, to obtain first version information of the target application program recorded in real time;
A query type determining module 330, configured to confirm a corresponding query type according to the query instruction; the query types include at least one of: demand query, version iteration query, defect query, and test case query;
and 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 inquiry instruction is obtained in response to the inquiry instruction of the version information; according to the access path, invoking a database interface of at least one target application program corresponding to the operation main body 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; according to the query conditions in the query instruction, the first version information is screened, the second version information corresponding to the query type is output, automatic acquisition of version information of the cross-operation main body and the cross-target application program is realized, acquisition and summarization of version information by users accessing the database of the operation main body one by one are avoided, the time spent is reduced, and the version information acquisition efficiency is improved; meanwhile, the first version information recorded in real time is obtained, and then the second version information is obtained through screening, so that the real-time updating of the second version information is realized.
Optionally, based on the above 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 above technical solution, the device for generating version information further includes:
the data table updating module is used for updating the query data table which is stored locally and corresponds to each query type 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 types include: the second version information corresponding to the demand inquiry comprises a plurality of demand data items, and each demand data item is distinguished by a demand identifier; a data table update module comprising:
the data table searching unit is used for carrying out matching searching in a locally stored requirement 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 stored data item consistent with a demand identifier of the first target demand data item is stored in the demand data table;
and the data item adding unit is used for adding the second target demand data item into the query data table if the stored data item consistent with the demand identification of the second target demand data item is not stored in the demand data table.
Optionally, based on the above technical solution, the data item adding unit is specifically configured to obtain a domain name path of the requirement details page if it is determined that the requirement details page is included in the second target requirement data item; generating a corresponding jump link with the requirement detail page according to the requirement identification of the second target requirement data item and the domain name path of the requirement detail page; and adding the jump link to a corresponding row of the second target demand data item in the demand data table.
Optionally, on the basis of the above technical solution, the query types include: the second version information corresponding to the defect inquiry and/or the test case inquiry 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 the local storage;
a location information obtaining unit, configured to find matched data in a first row where data exists in the target data table according to a preset column name, and if the matched data is found in the first row where data exists in the target data table according to the preset column name, obtain location information of the matched data in the target data table;
an index generating unit, configured to generate 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 matched data item acquisition unit is used for acquiring matched defect data items and/or test case data items from the target data table according to the index, and updating a locally stored defect data table and/or test case data table according to the defect data items and/or test case data items.
Optionally, on the basis of the above technical solution, the device for generating version information further includes:
the version identifier acquisition module is used for acquiring version identifiers corresponding to the current updated demand data items in the demand data table and adding the version identifiers to corresponding rows of the matched demand data items;
The requirement identification acquisition module is used for acquiring requirement identifications corresponding to the defect data items and/or test case data items which are updated currently in the defect data table and/or the test case data table, and adding the requirement identifications 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 matched data item acquisition unit is used for searching matched required data items in a required 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 required identification of the required data items;
and the report generating unit is used for generating a version iteration report matched with the query condition according to the requirement data item, the defect data item and the test case data item.
The device can execute the version information generation method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method. Technical details not described in detail in this embodiment may be found in the method provided by any embodiment of the present invention.
Example IV
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 merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 4, the electronic device 12 is in the form of a general purpose computing device. Components of the 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 connects the various system components, including the memory 28 and the processing unit 16.
Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Electronic device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
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 or write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, commonly referred to as a "hard disk drive"). Although not shown in fig. 4, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules 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 in, for example, 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 or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the embodiments described herein.
The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the electronic device 12, and/or any devices (e.g., network card, modem, etc.) that enable the electronic device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 over the bus 18. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 16 executes various functional applications and data processing by running a program stored in the memory 28, for example, implementing a version information generation method provided by any embodiment of the present invention. Namely: responding to a query instruction of version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction; according to the access path, calling a database interface of at least one target application program corresponding to an operation main body, and acquiring first version information of the target application program recorded in real time; according to the query instruction, confirming a corresponding query type; the query types include at least one of: demand query, version iteration query, defect query, and test case query; and screening the first version information according to the query conditions, and outputting second version information corresponding to the query type.
Example five
The fifth embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements a version information generating method according to any embodiment of the present invention; the method comprises the following steps:
responding to a query instruction of version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction;
according to the access path, calling a database interface of at least one target application program corresponding to an operation main body, and acquiring first version information of the target application program recorded in real time;
according to the query instruction, confirming a corresponding query type; the query types include at least one of: demand query, version iteration query, defect query, and test case query;
and screening the first version information according to the query conditions, and outputting second version information corresponding to the query type.
The computer storage media of embodiments of the invention may take the form of 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. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any 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 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.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 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 ++ 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 kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. 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, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (9)
1. A version information generation method, characterized by comprising:
responding to a query instruction of version information, and acquiring an access path corresponding to the query instruction; at least one query condition included in the query instruction;
according to the access path, calling a database interface of at least one target application program corresponding to an operation main body, and acquiring first version information of the target application program recorded in real time;
according to the query instruction, confirming a corresponding query type; the query types include at least one of: demand query, version iteration query, defect query, and test case query;
Screening the first version information according to the query conditions, and outputting second version information corresponding to the query type;
the responding to the inquiry instruction of the version information, obtaining the access path corresponding to the inquiry instruction, includes:
extracting 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.
2. The method of claim 1, wherein after filtering the first version information according to the query conditions and outputting the second version information corresponding to the query type, further comprising:
updating a query data table corresponding to each query type stored locally 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.
3. The method of claim 2, wherein the query types include: the second version information corresponding to the demand inquiry comprises a plurality of demand data items, and each demand data item is distinguished by a demand identifier;
The updating the locally stored query data table corresponding to each query type according to the second version information comprises the following steps:
matching and searching in a locally stored demand data table;
if the stored data item consistent with the requirement identification of the 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 stored data item consistent with the requirement identification of the second target requirement data item is not stored in the requirement data table, adding the second target requirement data item into the query data table.
4. A method according to claim 3, wherein said adding said second target demand data item to said look-up data table comprises:
if the second target requirement data item comprises a requirement detail page, acquiring a domain name path of the requirement detail page;
generating a corresponding jump link with the requirement detail page according to the requirement identification of the second target requirement data item and the domain name path of the requirement detail page;
and adding the jump link to a corresponding row of the second target demand data item in the demand data table.
5. The method of claim 2, wherein the query types include: the second version information corresponding to the defect inquiry and/or the test case inquiry comprises a plurality of data tables;
the updating the locally stored query data table corresponding to each query type according to the second version information comprises the following steps:
identifying the file format of each data table, obtaining 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 the position information of the matched data in the target data table;
generating an index in the form of a key value pair corresponding to the target data table according to the preset column name and the position information;
and according to the index, acquiring the matched defect data item and/or test case data item from the target data table, 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.
6. The method of claim 2, further comprising, after updating the locally stored query data table corresponding to each of the query types according to the second version information:
the method comprises the steps of obtaining version identifiers corresponding to all currently updated demand data items in a demand data table, and adding all the version identifiers to corresponding rows of matched demand data items;
acquiring a requirement identifier corresponding to each defect data item and/or test case data item which are updated currently 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;
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 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 requirement data item, the defect data item and the test case data item.
7. A version information generating apparatus, comprising:
the access path acquisition module is used for responding to the inquiry instruction of the version information and acquiring an access path corresponding to the inquiry 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 main body according to the access path to acquire 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 types include at least one of: demand query, version iteration query, defect query, and test case query;
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 types;
an access path obtaining module 310, configured to specifically 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.
8. An electronic device, comprising:
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 are caused to implement the method of generating version information as claimed in any one of claims 1-6.
9. A computer-readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements a version information generation method according to any one of claims 1-6.
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 CN113010208A (en) | 2021-06-22 |
| CN113010208B true 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) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114168579B (en) * | 2021-12-10 | 2025-10-03 | 中国建设银行股份有限公司 | Comprehensive query method and system |
| CN113918209B (en) * | 2021-12-16 | 2022-04-15 | 深圳市明源云科技有限公司 | Method and device for generating upgrade list and readable storage medium |
| CN114466026B (en) * | 2022-01-05 | 2024-05-14 | 杭州网易云音乐科技有限公司 | Update method and device of application program interface, storage medium and computing device |
| CN114443126A (en) * | 2022-02-08 | 2022-05-06 | 北京沃东天骏信息技术有限公司 | Multi-version image processing method, information push method, device and electronic device |
| CN114625411A (en) * | 2022-03-14 | 2022-06-14 | 北京字跳网络技术有限公司 | A software version information management method, system, device and storage medium |
Citations (7)
| 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 |
| CN112685474A (en) * | 2020-12-30 | 2021-04-20 | 北京联创信安科技股份有限公司 | Application management method, device, equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11995451B2 (en) * | 2018-03-27 | 2024-05-28 | Huawei Technologies Co., Ltd. | Resource permission processing method and apparatus, storage medium, and chip |
-
2021
- 2021-04-28 CN CN202110469150.7A patent/CN113010208B/en active Active
Patent Citations (7)
| 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 |
| CN112685474A (en) * | 2020-12-30 | 2021-04-20 | 北京联创信安科技股份有限公司 | Application management method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 基于SVN版本控制的教务信息管理系统开发与实现;孙德刚;;现代信息科技(第11期);106-108 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113010208A (en) | 2021-06-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113010208B (en) | Version information generation method, device, equipment and storage medium | |
| CN110162544B (en) | Heterogeneous data source data acquisition method and device | |
| CN102279737B (en) | System and method for analytic process design | |
| CN111061733B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| US20100306590A1 (en) | Automated Testing Platform for Event Driven Systems | |
| CN108460068B (en) | Method, device, storage medium and terminal for importing and exporting report | |
| US11676345B1 (en) | Automated adaptive workflows in an extended reality environment | |
| CN113360519B (en) | Data processing method, device, equipment and storage medium | |
| US20070250520A1 (en) | System and method for managing web applications | |
| CN114564930B (en) | Document information integration method, device, equipment, medium and program product | |
| US20070234306A1 (en) | Tracing performance of machine-readable instructions | |
| CN111813804A (en) | Data query method and device, electronic equipment and storage medium | |
| US12117981B2 (en) | Automatic discovery of executed processes | |
| CN112162954B (en) | User operation log generation and path positioning method, device, equipment and medium | |
| CN112000687A (en) | Business account table generation method and device, computer equipment and storage medium | |
| CN110990346A (en) | File data processing method, device, equipment and storage medium based on block chain | |
| CN112905635A (en) | Service processing method, device, equipment and storage medium | |
| CN110347573B (en) | Application program analysis method, device, electronic device, and computer-readable medium | |
| CN111414410A (en) | Data processing method, device, equipment and storage medium | |
| CN110677307B (en) | Service monitoring method, device, equipment and storage medium | |
| CN112416713A (en) | Operation auditing system and method, computer readable storage medium and electronic equipment | |
| US20090063578A1 (en) | Management of data needed to resolve pointer errors in heirarchical database management systems | |
| CN113138906A (en) | Call chain data acquisition method, device, equipment and storage medium | |
| US10664501B2 (en) | Deriving and interpreting users collective data asset use across analytic software systems | |
| CN116361251A (en) | Log processing method, log processing device, computer program and computer readable 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 |