CN113434415B - Resource package testing method and device, electronic equipment and storage medium - Google Patents

Resource package testing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113434415B
CN113434415B CN202110721735.3A CN202110721735A CN113434415B CN 113434415 B CN113434415 B CN 113434415B CN 202110721735 A CN202110721735 A CN 202110721735A CN 113434415 B CN113434415 B CN 113434415B
Authority
CN
China
Prior art keywords
test
version
issue
construction
resource package
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
Application number
CN202110721735.3A
Other languages
Chinese (zh)
Other versions
CN113434415A (en
Inventor
华彩娟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qingdao Haier Technology Co Ltd
Haier Smart Home Co Ltd
Original Assignee
Qingdao Haier Technology Co Ltd
Haier Smart Home Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qingdao Haier Technology Co Ltd, Haier Smart Home Co Ltd filed Critical Qingdao Haier Technology Co Ltd
Priority to CN202110721735.3A priority Critical patent/CN113434415B/en
Publication of CN113434415A publication Critical patent/CN113434415A/en
Application granted granted Critical
Publication of CN113434415B publication Critical patent/CN113434415B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention provides a resource package testing method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: responding to a request of a front-end page of a construction system, and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system; after receiving the test information input by the user and sent by the front-end page of the construction system, locking the test information and inquiring the construction information of the resource package; after determining that the test order can be generated based on the construction information, creating a blank test order, filling test basic information and memory list information, and generating the test order. By the resource package testing method, the resource package testing device, the electronic equipment and the storage medium, development efficiency can be greatly improved.

Description

Resource package testing method and device, electronic equipment and storage medium
Technical Field
The present invention relates to the field of application development technologies, and in particular, to a method and apparatus for resource package measurement, an electronic device, and a storage medium.
Background
Along with the maturity of agile development and the rapid iterative realization of product functions, in order to meet the requirement of rapid development and iteration, more and more APP (APPlication) adopts a hybrid development mode, the service logic is not complicated to display the service, the development is changed into H5, and the hybrid development mode can rapidly update the service requirement and can thermally update.
However, most of the existing methods adopt a simple oral communication or document mail communication mode, which is inefficient. Therefore, how to rapidly test and release the H5 resource package becomes a technical problem to be solved.
Disclosure of Invention
Aiming at the problems existing in the prior art, the invention provides a resource package testing method, a device, electronic equipment and a storage medium.
In a first aspect, the present invention provides a method for resource package measurement, including:
responding to a request of a front-end page of a construction system, and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system;
after receiving the test information input by the user and sent by the front-end page of the construction system, locking the test information and inquiring the construction information of the resource package;
after determining that the test order can be generated based on the construction information, creating a blank test order, filling test basic information and memory list information, and generating the test order.
Optionally, the determining, based on the build information, that the test order can be generated includes:
if it is determined that the construction of the resource package is packaged and not tested, and no task is being constructed, it is determined that a test order can be generated.
Optionally, the method further comprises:
if the dependency construction of the current resource package construction exists, inquiring the dependency construction, traversing and comparing the setting items of the current resource package construction and the dependency construction, and determining a newly added module, a deleted module and a version modified module;
and for the version modification module, calling a Git client to acquire the submitted difference information of the Git Tag corresponding to the constructed version, and filling the difference information into the test sheet.
Optionally, the method further comprises:
invoking the jira interface to create an issue of the proposed version and an issue of the desired version in the jira system.
Optionally, the creating the extracted version of the issue and the desired version of the issue in the jira system includes:
if the current test is the first test of the large version of the target APP, the target APP is subjected to the last test, and the last test is not cancelled, taking the issue of the last expected version as the issue of the current test version, and creating a new expected version as the issue of the current expected version;
if the current test is the first test of the large version of the target APP, the target APP is subjected to the last test, and the last test is cancelled, taking the issue of the last test version as the issue of the current test version, and taking the issue of the last expected version as the issue of the current expected version;
if the current test is the first test of the large version of the target APP and the target APP is not tested last time, the issue of the current test version and the issue of the current expected version are directly created.
Optionally, the creating the extracted version of the issue and the desired version of the issue in the jira system includes:
if the current test is the first test of the small version of the target APP, the issue of the current test version and the issue of the current expected version are directly created.
Optionally, the creating the extracted version of the issue and the desired version of the issue in the jira system includes:
if the target APP exists in the last test and the last test is not canceled, taking the last expected version of the isue as the current test version of the isue, and creating a new expected version of the isue as the current expected version of the isue;
if the target APP exists in the last test and the last test is canceled, taking the last test version of the issue as the current test version of the issue, and taking the last expected version of the issue as the current expected version of the issue.
In a second aspect, the present invention further provides a resource packet measurement device, including:
the response module is used for responding to a request of constructing a front-end page of the system and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system;
the query module is used for locking the test information after receiving the test information input by the user and sent by the front-end page of the construction system, and querying the construction information of the resource package;
and the generation module is used for creating a blank test list and filling test basic information and memory list information after determining that the test list can be generated based on the construction information, so as to generate the test list.
In a third aspect, the present invention also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the resource package testing method according to the first aspect as described above when executing the program.
In a fourth aspect, the present invention also provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the resource package testing method of the first aspect as described above.
According to the resource package testing method, the device, the electronic equipment and the storage medium, the version iteration of the H5 resource package is electronized and simplified through the platform of the construction system, after the development of related requirements is completed, H5 developers can complete the primary version testing through a simple interface operation, and the interface operation only needs to input the related information of the current version by a user, and a testing list is automatically generated by combining a gerrit code system and a jira project management system, so that the development efficiency can be greatly improved.
Drawings
In order to more clearly illustrate the invention or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of a resource package testing method provided by the invention;
FIG. 2 is a timing diagram of resource packet extraction according to the present invention;
FIG. 3 is a schematic diagram of a resource package testing device according to the present invention;
fig. 4 is a schematic structural diagram of an electronic device provided by the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
With the rapid development of the software industry and the rapid iteration requirements of development demands and development cycles, simple oral communication or document mail communication is inefficient due to the existence of multiple developments, and cannot be rapidly obtained for development test of responses of each party, and the like.
Aiming at the problems, the invention provides a solution, the platform of the application construction system is used for iterating and electronizing and simplifying the version of the H5 resource package, providing a list for the extracted version, managing and browsing version events, automatically correlating data of gerit and jira, establishing a system tie, and facilitating the use of each role in the extracting and testing process.
Fig. 1 is a flow chart of a resource package testing method provided by the present invention, as shown in fig. 1, the method includes the following steps:
step 100, responding to a request of a front-end page of a construction system, and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system;
specifically, the APP end H5 is used more and more frequently, in order that after the H5 developer finishes the development of the related requirement, the developer can finish the carrying out of one version through a simple interface operation, and the interface operation only needs the user to input the related information of the current version, and combines the gerit code system and the jira project management system, personnel such as development, test and the like are tied together, and a carrying list is automatically generated, so that the development efficiency is greatly improved. The resource package storage list can be obtained by requesting the jira system from a construction system server.
Step 101, locking the test information after receiving the test information input by the user and sent by the front-end page of the construction system, and inquiring the construction information of the resource package;
specifically, after the server side of the building system returns the memory list and the building list to the front-end page of the building system, the front-end page of the building system may pop up a prompt box for inputting the measurement information to a developer, for example pop up the measurement box to the developer, so that the developer may input the measurement information of the resource package to be measured, for example, a measurement APP (i.e., the APP corresponding to the current measurement of the resource package), an affected version (i.e., an affected APP version), a measurement-associated memory, a measurement-related description, and so on, which are not limited herein.
The front end page of the construction system requests the test interface to the server end of the construction system based on the test information input by the developer, after the server end of the construction system receives the test information input by the user and sent by the front end page of the construction system, the test information can be locked, for example, an APP test lock is added, and the construction information of the resource package is queried, namely, the APP construction information of the resource package is tested, for example, whether the APP construction is tested, whether the package is packaged, whether a self-test package exists, whether a task being constructed exists (namely, whether the APP construction is in progress) and the like.
Step 102, after determining that the test order can be generated based on the construction information, creating a blank test order, filling test basic information and memory list information, and generating the test order.
Specifically, after the query resource package construction information determines that the test report can be generated, the construction system server end can execute the test report generation logic, create a blank test report, fill test base information, store list information and the like, and generate the test report. The basic information of the extraction and measurement can be related APP, APP version, APP construction, extraction and measurement person, extraction and measurement time and the like.
According to the resource package testing method provided by the embodiment of the invention, the version iteration of the H5 resource package is electronized and simplified through the platform of the construction system, after the development of related requirements is completed by H5 developers, the primary version test can be completed through a simple interface operation, and the interface operation only needs to input the related information of the current version by a user, and the testing list is automatically generated by combining a gerrit code system and a jira project management system, so that the development efficiency can be greatly improved.
Optionally, the determining, based on the build information, that the test order can be generated includes:
if it is determined that the construction of the resource package is packaged and not being tested, and no task is being constructed, it is determined that a test order can be generated.
Specifically, after inquiring the construction information of the resource package, if the construction system server determines that the construction of the resource package is packaged and not tested, and no construction task is being performed, which indicates that the construction of the resource package is completed and is in a state to be tested, and the construction system server can perform the test, the construction system server can determine that a test list can be generated at the moment.
Optionally, the method further comprises:
if the dependency construction of the current resource package construction exists, inquiring the dependency construction, traversing setting items for comparing the current resource package construction and the dependency construction, and determining a newly added module, a deleted module and a version modified module;
and for the version modification module, calling the Git client to acquire the submitted difference information of the Git Tag corresponding to the constructed version, and filling the difference information into the submitted list.
Specifically, in the process of executing the test list generating logic by the construction system server, if it is determined that a dependency relationship exists between the current resource package construction and the resource package construction which is tested in advance, that is, the current resource package construction is updated in version on the basis of the resource package construction which is tested in advance, which indicates that the dependency construction of the current resource package construction exists, the dependency construction is queried, setting items of the current resource package construction and the dependency construction are compared in a traversing manner, and a newly added module, a deleted module and a module with a modified version are determined.
For the version modified module, the construction system server can call the Git client (namely the gerrit system) to acquire the submitted difference information of the Git tags corresponding to two construction versions (namely the current resource package construction and the dependent construction) respectively, and fill the difference information into the submitted list, so that development and testing personnel are helped to quickly master the difference of each version.
Optionally, the method further comprises:
invoking the jira interface to create an issue of the proposed version and an issue of the desired version in the jira system.
Specifically, in the embodiment of the invention, the server end of the construction system can also execute the jira related logic, call the jira interface and create the issue (problem) of the tested version and the issue (problem) of the expected version in the jira system. The extracted version of the isulfe can be the isulfe corresponding to the extraction, the expected version of the isulfe can be the isulfe corresponding to the stage target, and the extracted version of the isulfe can be a subset of the expected version of the isulfe because multiple extraction is needed to realize the stage target.
Specifically, the server end of the system is constructed to execute jira related logic, and when the issue of the extracted version and the issue of the expected version are created in the jira system, different creation strategies can be executed based on the historical extracted condition of the target APP (i.e. the APP corresponding to the extracted version).
Optionally, the creating the extracted version of the issue and the desired version of the issue in the jira system includes:
if the current test is the first test of the large version of the target APP, the target APP is subjected to the last test, and the last test is not cancelled, taking the issue of the last expected version as the issue of the current test version, and creating a new expected version as the issue of the current expected version;
if the current test is the first test of the large version of the target APP, the target APP is subjected to the last test, and the last test is cancelled, taking the issue of the last test version as the issue of the current test version, and taking the issue of the last expected version as the issue of the current expected version;
if the current test is the first test of the large version of the target APP and the target APP is not tested last time, the issue of the current test version and the issue of the current expected version are directly created.
Specifically, if the current test is the first test of the large version of the target APP, firstly determining whether the target APP has the last test, if the target APP has the last test and the last test is not cancelled, taking the issue of the last expected version as the issue of the current test version, and creating a new issue of the expected version as the issue of the current expected version; if the last test is performed, but the last test is cancelled, the last test version of the isu can be used as the current test version of the isu, and the last expected version of the isu can be used as the current expected version of the isu.
If the target APP is determined not to be submitted last time, the issue of the current submitted version and the issue of the current expected version can be directly created.
Optionally, the creating the extracted version of the issue and the desired version of the issue in the jira system includes:
if the current test is the first test of the small version of the target APP, the issue of the current test version and the issue of the current expected version are directly created.
Specifically, if the current test is the first test of the small version of the target APP, the issue of the current test version and the issue of the current expected version can be directly created to maintain independence.
Optionally, the creating the extracted version of the issue and the desired version of the issue in the jira system includes:
if the target APP exists in the last test and the last test is not canceled, taking the last expected version of the isue as the current test version of the isue, and creating a new expected version of the isue as the current expected version of the isue;
if the target APP exists in the last test and the last test is canceled, taking the last test version of the issue as the current test version of the issue, and taking the last expected version of the issue as the current expected version of the issue.
Specifically, if the current test is not the first test of the target APP, after determining that the last test of the target APP is not canceled, the last desired version of the isue is used as the current test version of the isue, and a new desired version of the isue is created as the current desired version of the isue; if the last test of the target APP is canceled, the last test version of the issue can be used as the current test version of the issue, and the last expected version of the issue can be used as the current expected version of the issue.
Fig. 2 is a timing chart of resource package extraction and measurement provided in the present invention, as shown in fig. 2, a user (e.g. H5 developer) implements interaction among a building system, a project management system jira and a code management system gerit by operating on the building system, and implements resource package extraction and measurement functions, where the main flow includes the following parts:
1. the developer clicks the "test" button on the front end of the building system (i.e., the front page in fig. 2), the front end requests the resource package storage list from the server end of the building system (i.e., the building system in fig. 2), and the server end returns the storage list. The front end requests a building list (APPName) of the latest test of each version of the APP, and the server end returns the building list of the latest test. The front end pops up the test frame to the developer.
2. The developer inputs the test APP, the influence version, the test associated memory, the test description and the like, and the front end requests the test interface (building id, APPName, story, the influence version, the test related description and the like) from the server end.
3. And adding an APP test lock at a server end of the construction system, locking the information of the test, inquiring the target APP to construct, and checking whether the Check is packaged or not, whether the Check is a self-test package or not, and whether the Check has a task under construction or not. Calculating the number of the extraction rounds according to the Check result, generating an extraction list, and generating logic of the extraction list as follows:
creating an empty test order;
filling basic information such as associated resource packages, resource package versions, resource package tags, associated APP, APP versions, APP construction, person to be tested, time to be tested and the like;
filling storage list information;
if the dependency relationship exists, inquiring the dependency construction, traversing and comparing the two constructed setting items, and finding out a newly added module, a deleted module and a version modified module; for a version modification module, calling a Git client to acquire the submitted difference information of the Git Tag corresponding to the constructed version, and filling the difference information into a test sheet;
and saving the bill of lading data.
4. Executing the Jira related logic, calling the Jira interface, and creating a test issue:
1) And if the target APP is the 1 st extraction of the large version of the target APP.
a) If the last extraction test exists:
if the last test is not canceled, the test version inherits the last expected version and creates a new expected version.
If the last test is canceled, directly inheriting the two last versions.
b) If there is no last test, then a test version and a desired version are created.
2) If the target APP small version is the 1 st time of the extraction, an extraction version and an expected version are created, and the independence is maintained.
3) If not the 1 st test.
If the last test is not canceled, the test version inherits the last expected version and creates a new expected version.
If the last test is canceled, directly inheriting the two last versions.
It should be noted that if the target version is found to be not already present (possibly manually deleted) in the process of modifying the name of the target version to the version name corresponding to the current test (e.g., inheriting the situation of the last version), the new version is created as compensation.
5. And marking the target APP construction as tested, recording the test times, updating the test times of the target APP version, and updating the testability of the target Story.
6. Recording an "APP mention" event, the content comprising: the list id, the storage list and the number of the extraction rounds are used for storing the event.
7. And the system returns an operation result. After receiving the success message returned by the server, the front-end page closes the test frame, requests the server to update the resource package construction list, the version list and the store list, and after the server returns corresponding information, the front-end page displays the updated construction list, the version list, the store list and other updated information (such as update test times, update store testability and the like) for viewing by developers and the like.
The resource package testing device provided by the invention is described below, and the resource package testing device and the resource package testing method described below can be correspondingly referred to each other.
Fig. 3 is a schematic structural diagram of a resource package testing device provided by the present invention, as shown in fig. 3, the device includes:
the response module 300 is configured to respond to a request for building a front-end page of the system, and return a memory list and a building list of a resource package to be tested to the front-end page of the system;
the query module 310 is configured to lock the measurement information after receiving the measurement information entered by the user and sent by the front-end page of the building system, and query the building information of the resource package;
and the generating module 320 is configured to create a blank test report and fill the test base information and the memory list information to generate the test report after determining that the test report can be generated based on the construction information.
Optionally, the generating module 320 is configured to: if it is determined that the construction of the resource package is packaged and not being tested, and no task is being constructed, it is determined that a test order can be generated.
Optionally, the generating module 320 is further configured to: if the dependency construction of the current resource package construction exists, inquiring the dependency construction, traversing setting items for comparing the current resource package construction and the dependency construction, and determining a newly added module, a deleted module and a version modified module; and for the version modification module, calling the Git client to acquire the submitted difference information of the Git Tag corresponding to the constructed version, and filling the difference information into the submitted list.
Optionally, the apparatus further comprises:
the creating module 330 is configured to call the jira interface and create the test version of the issue and the desired version of the issue in the jira system.
Optionally, the creating module 330 is configured to: if the current test is the first test of the large version of the target APP, the target APP is subjected to the last test, and the last test is not cancelled, taking the issue of the last expected version as the issue of the current test version, and creating a new expected version as the issue of the current expected version; if the current test is the first test of the large version of the target APP, the target APP is subjected to the last test, and the last test is cancelled, taking the issue of the last test version as the issue of the current test version, and taking the issue of the last expected version as the issue of the current expected version; if the current test is the first test of the large version of the target APP and the target APP is not tested last time, the issue of the current test version and the issue of the current expected version are directly created.
Optionally, the creating module 330 is configured to: if the current test is the first test of the small version of the target APP, the issue of the current test version and the issue of the current expected version are directly created.
Optionally, the creating module 330 is configured to: if the target APP exists in the last test and the last test is not canceled, taking the last expected version of the isue as the current test version of the isue, and creating a new expected version of the isue as the current expected version of the isue; if the target APP exists in the last test and the last test is canceled, taking the last test version of the issue as the current test version of the issue, and taking the last expected version of the issue as the current expected version of the issue.
It should be noted that, the device provided by the present invention can implement all the method steps implemented by the method embodiment and achieve the same technical effects, and the parts and beneficial effects that are the same as those of the method embodiment in the present embodiment are not described in detail herein.
Fig. 4 is a schematic structural diagram of an electronic device according to the present invention, as shown in fig. 4, the electronic device may include: processor 410, communication interface (Communications Interface) 420, memory 430 and communication bus 440, wherein processor 410, communication interface 420 and memory 430 communicate with each other via communication bus 440. The processor 410 may invoke logic instructions in the memory 430 to perform the steps of any of the resource package extraction methods provided in the embodiments described above, such as: responding to a request of a front-end page of a construction system, and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system; after receiving the test information input by the user and sent by the front-end page of the construction system, locking the test information and inquiring the construction information of the resource package; after determining that the test order can be generated based on the construction information, creating a blank test order, filling test basic information and memory list information, and generating the test order.
Further, the logic instructions in the memory 430 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In another aspect, the present invention also provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, are capable of performing the steps of any of the resource package extraction methods provided by the above embodiments, for example: responding to a request of a front-end page of a construction system, and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system; after receiving the test information input by the user and sent by the front-end page of the construction system, locking the test information and inquiring the construction information of the resource package; after determining that the test order can be generated based on the construction information, creating a blank test order, filling test basic information and memory list information, and generating the test order.
In yet another aspect, the present invention further provides a non-transitory computer readable storage medium, on which a computer program is stored, which when executed by a processor is implemented to perform the steps of any of the resource package extraction methods provided in the above embodiments, for example: responding to a request of a front-end page of a construction system, and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system; after receiving the test information input by the user and sent by the front-end page of the construction system, locking the test information and inquiring the construction information of the resource package; after determining that the test order can be generated based on the construction information, creating a blank test order, filling test basic information and memory list information, and generating the test order.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (9)

1. The resource package testing method is characterized by comprising the following steps:
responding to a request of a front-end page of a construction system, and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system;
after receiving the test information input by the user and sent by the front-end page of the construction system, locking the test information and inquiring the construction information of the resource package;
after determining that the test order can be generated based on the construction information, creating a blank test order, filling test basic information and memory list information, and generating the test order, wherein the method further comprises the following steps:
if the dependency construction of the current resource package construction exists, inquiring the dependency construction, traversing and comparing the setting items of the current resource package construction and the dependency construction, and determining a newly added module, a deleted module and a version modified module;
and for the version modification module, calling a Git client to acquire the submitted difference information of the Git Tag corresponding to the constructed version, and filling the difference information into the test sheet.
2. The resource package extraction method of claim 1, wherein the determining that an extraction order can be generated based on the construction information comprises:
if it is determined that the construction of the resource package is packaged and not tested, and no task is being constructed, it is determined that a test order can be generated.
3. The resource package extraction method of claim 1, wherein the method further comprises:
invoking the jira interface to create an issue of the proposed version and an issue of the desired version in the jira system.
4. The resource package extraction method of claim 3, wherein creating an extracted version of the issue and a desired version of the issue in the jira system comprises:
if the current test is the first test of the large version of the target APP, the target APP is subjected to the last test, and the last test is not cancelled, taking the issue of the last expected version as the issue of the current test version, and creating a new expected version as the issue of the current expected version;
if the current test is the first test of the large version of the target APP, the target APP is subjected to the last test, and the last test is cancelled, taking the issue of the last test version as the issue of the current test version, and taking the issue of the last expected version as the issue of the current expected version;
if the current test is the first test of the large version of the target APP and the target APP is not tested last time, the issue of the current test version and the issue of the current expected version are directly created.
5. The resource package extraction method of claim 3, wherein creating an extracted version of the issue and a desired version of the issue in the jira system comprises:
if the current test is the first test of the small version of the target APP, the issue of the current test version and the issue of the current expected version are directly created.
6. The resource package extraction method of claim 3, wherein creating an extracted version of the issue and a desired version of the issue in the jira system comprises:
if the target APP exists in the last test and the last test is not canceled, taking the last expected version of the isue as the current test version of the isue, and creating a new expected version of the isue as the current expected version of the isue;
if the target APP exists in the last test and the last test is canceled, taking the last test version of the issue as the current test version of the issue, and taking the last expected version of the issue as the current expected version of the issue.
7. A resource pack testing device, comprising:
the response module is used for responding to a request of constructing a front-end page of the system and returning a memory list and a construction list of a resource package to be tested to the front-end page of the construction system;
the query module is used for locking the test information after receiving the test information input by the user and sent by the front-end page of the construction system, and querying the construction information of the resource package;
the generation module is used for creating a blank test list and filling test basic information and memory list information after determining that the test list can be generated based on the construction information, and generating the test list, wherein the generation module is further used for: if the dependency construction of the current resource package construction exists, inquiring the dependency construction, traversing and comparing the setting items of the current resource package construction and the dependency construction, and determining a newly added module, a deleted module and a version modified module; and for the version modification module, calling a Git client to acquire the submitted difference information of the Git Tag corresponding to the constructed version, and filling the difference information into the test sheet.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the resource package extraction method of any one of claims 1 to 6 when the program is executed by the processor.
9. A non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the steps of the resource package extraction method of any of claims 1 to 6.
CN202110721735.3A 2021-06-28 2021-06-28 Resource package testing method and device, electronic equipment and storage medium Active CN113434415B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110721735.3A CN113434415B (en) 2021-06-28 2021-06-28 Resource package testing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110721735.3A CN113434415B (en) 2021-06-28 2021-06-28 Resource package testing method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113434415A CN113434415A (en) 2021-09-24
CN113434415B true CN113434415B (en) 2023-07-21

Family

ID=77755132

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110721735.3A Active CN113434415B (en) 2021-06-28 2021-06-28 Resource package testing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113434415B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108829399A (en) * 2018-04-13 2018-11-16 杭州朗和科技有限公司 A kind of test method of application, test device, medium and calculate equipment
CN109491663A (en) * 2018-11-01 2019-03-19 北京车和家信息技术有限公司 Code inspection method and device
CN109725906A (en) * 2018-12-30 2019-05-07 上海创功通讯技术有限公司 A kind of code compiling method and corresponding continuous integration system
CN110580216A (en) * 2018-06-08 2019-12-17 北京京东尚科信息技术有限公司 application extraction and detection method and device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180322035A1 (en) * 2017-05-04 2018-11-08 Hcl Technologies Limited Automation testing platform for facilitating automatic testing of an information technology (it) enabled application

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108829399A (en) * 2018-04-13 2018-11-16 杭州朗和科技有限公司 A kind of test method of application, test device, medium and calculate equipment
CN110580216A (en) * 2018-06-08 2019-12-17 北京京东尚科信息技术有限公司 application extraction and detection method and device
CN109491663A (en) * 2018-11-01 2019-03-19 北京车和家信息技术有限公司 Code inspection method and device
CN109725906A (en) * 2018-12-30 2019-05-07 上海创功通讯技术有限公司 A kind of code compiling method and corresponding continuous integration system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Utilising CI environment for efficient and effective testing of NFRs";Liang Yu 等;《Information and Software Technology》;第1-5页 *
"基于持续集成的配置管理系统设计与实现";刘颖;《中国优秀硕士学位论文全文数据库信息科技辑》;第I138-178页 *

Also Published As

Publication number Publication date
CN113434415A (en) 2021-09-24

Similar Documents

Publication Publication Date Title
US8799907B2 (en) Task management system
US7769821B2 (en) Systems and methods for enhanced meassage support using a generic client proxy
US7921330B2 (en) Data migration manager
US10095483B2 (en) Modularized XML namespaces
US9934229B2 (en) Telemetry file hash and conflict detection
CN107241315B (en) Access method and device of bank gateway interface and computer readable storage medium
US20080052308A1 (en) Method and system for realizing automatic adaptation of data object model
US20200366485A1 (en) Method and apparatus for inter-blockchain transmission of authenticable message
US9697042B2 (en) Extensibility of business process and application logic
US9026557B2 (en) Schema mapping based on data views and database tables
US8862937B2 (en) Method and system for migrating data from multiple sources
CN110287196B (en) Block storage method, parallel chain transaction acquisition method, equipment and storage medium
US20230148285A1 (en) Generating context tree data based on a tailored data model
US20090037453A1 (en) Unified and extensible implementation of a change state id for update services based on a hash calculation
US20130311839A1 (en) Generation of error messages and progress information messages via a common interface
CN112256318B (en) Construction method and equipment for dependent product
CN108139947A (en) For web user interface to be applied the system and method being isolated with engine when bottom persistence framework and operation in integrated service based on cloud
CN113434415B (en) Resource package testing method and device, electronic equipment and storage medium
CN112561690A (en) Method, system, equipment and storage medium for testing credit card staging service interface
CN113485759A (en) Micro-service configuration information management system, method, electronic device and storage medium
CN113301180A (en) Object identifier analysis method, device, equipment and storage medium
US8812350B2 (en) Service evolution approach in SOA
CN116028138B (en) Application publishing method and device
CN112667491A (en) Function test method and device of virtual machine
CN112749176A (en) Synchronous processing method and device of inventory data, storage medium and server

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