CN110609793A - Software transmitting and testing method, server and system - Google Patents
Software transmitting and testing method, server and system Download PDFInfo
- Publication number
- CN110609793A CN110609793A CN201910856276.2A CN201910856276A CN110609793A CN 110609793 A CN110609793 A CN 110609793A CN 201910856276 A CN201910856276 A CN 201910856276A CN 110609793 A CN110609793 A CN 110609793A
- Authority
- CN
- China
- Prior art keywords
- version
- test
- software
- source code
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 196
- 238000004806 packaging method and process Methods 0.000 claims abstract description 8
- 238000000034 method Methods 0.000 claims description 33
- 230000001960 triggered effect Effects 0.000 claims description 20
- 230000005540 biological transmission Effects 0.000 claims description 19
- 238000012986 modification Methods 0.000 claims description 14
- 230000004048 modification Effects 0.000 claims description 14
- 238000004891 communication Methods 0.000 claims description 9
- 238000011161 development Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 4
- 238000013522 software testing Methods 0.000 description 3
- 238000007689 inspection Methods 0.000 description 2
- 238000010998 test method Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 238000002716 delivery method Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The invention discloses a software transmitting and testing method, which comprises the following steps: acquiring a source code file corresponding to a to-be-tested version of target software from a source code library; determining delta data in the source code file; loading, compiling and packaging are carried out according to the incremental data to obtain sending and testing version data; and sending the transmitted and measured version data to a test terminal, wherein the test terminal upgrades and runs the installed target software according to the transmitted and measured version data, and feeds back the running parameters. The invention also discloses a server and a software transmitting and testing system, which avoid a large number of redundant files in test contents by acquiring the files to be transmitted and tested of the target software, determining the incremental data in the files to be transmitted and tested, transmitting and testing only the incremental data and transmitting and testing by adopting accurate fine granularity, thereby reducing the test workload and improving the test efficiency.
Description
Technical Field
The invention relates to the technical field of software transmission and test, in particular to a software transmission and test method, a server and a system.
Background
When a developer develops and tests software, the development process is usually divided into a plurality of different branches, so that the developer can modify and test different parts of the software respectively. There may be multiple versions of software for different branches at different stages of the development process.
At present, when software is sent, a complete file of a certain version of software is usually sent and tested. However, sending and testing a complete file of a certain version of software results in a large number of redundant files in the test content, which increases unnecessary test workload and deployment workload, thus resulting in lower test efficiency and bringing risks to system operation.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a software transmitting and testing method, a server and a system, aiming at avoiding a large number of redundant files in test contents by acquiring a file to be transmitted and tested of target software, determining incremental data in the file to be transmitted and tested, transmitting and testing only aiming at the incremental data and transmitting and testing with accurate fine granularity, thereby reducing test workload and improving test efficiency.
In order to achieve the above object, the present invention provides a software transmission and test method, which comprises the following steps:
acquiring a source code file corresponding to a to-be-tested version of target software from a source code library;
determining delta data in the source code file;
loading, compiling and packaging are carried out according to the incremental data to obtain sending and testing version data;
and sending the transmitted and measured version data to a test terminal, wherein the test terminal upgrades and runs the installed target software according to the transmitted and measured version data, and feeds back the running parameters.
Optionally, the step of determining the incremental data in the source code file includes:
acquiring a source code file corresponding to the reference version of the target software;
and comparing the source code file corresponding to the version to be tested with the source code file corresponding to the reference version to obtain the incremental data.
Optionally, the step of obtaining the source code file corresponding to the reference version of the target software includes:
acquiring a sending and testing type of the target software;
when the transmission and test type of the target software is full-scale transmission, taking the initial version of the target software as the reference version, and acquiring a source code file corresponding to the initial version;
and when the sending and testing type of the target software is increment sending, taking the adjacent version of the version to be sent and tested as the reference version, and acquiring a source code file corresponding to the adjacent version.
Optionally, before the step of sending the test version data to the test terminal, the method further includes:
obtaining upgrading step information corresponding to the transmitted and measured version data;
outputting the upgrading step information;
and when a modification instruction of the upgrading step information triggered by a user is received, modifying the upgrading step information according to the modification instruction, wherein the test terminal upgrades the installed target software according to the modified upgrading step information and the version data to be tested.
Optionally, before the step of obtaining the source code file corresponding to the version to be tested of the target software from the source code library, the method further includes:
when a test sending instruction triggered by a user is received, acquiring a plurality of version information of the target software from the source code library, generating a version list, and outputting the version list;
and when a selection instruction of the version list triggered by the user is received, taking the version corresponding to the selection instruction as the to-be-tested version of the target software.
Optionally, the step of sending the test version sending data to a test terminal includes:
determining the type of a test terminal corresponding to the transmitted test version data;
and sending the data of the sent test version to a test terminal corresponding to the type of the test terminal.
Optionally, after the step of sending the test version data to the test terminal, the method further includes:
and outputting a test result according to the operation parameters when the operation parameters fed back by the test terminal are received.
Optionally, the software sending and testing method further includes:
when receiving a checking instruction of the test result triggered by a user, sending the checking instruction to the test terminal, wherein when receiving the checking instruction, the test terminal compares the version data to be tested with the upgrade generation file of the target software and feeds back the comparison result;
and when a comparison result fed back by the test terminal is received, outputting a check result according to the comparison result.
In addition, to achieve the above object, the present invention also provides a server, including: the software testing method comprises a memory, a processor and a software testing program stored on the memory and capable of running on the processor, wherein the software testing program realizes the steps of the software testing method according to any one of the above items when being executed by the processor.
In addition, in order to achieve the above object, the present invention further provides a software transmission and test system, including:
a server, the server being as any one of the above;
and the test terminal is in network communication with the server.
According to the software sending and testing method, the server and the system, the source code file corresponding to the version to be sent and tested of the target software is obtained, the incremental data in the source code file is determined, the loading, the compiling and the packaging are carried out according to the incremental data, the version sending and testing data are obtained, the version sending and testing data are sent to the test terminal, the test terminal upgrades and runs the installed target software according to the version sending and testing data, and the running parameters are fed back. According to the invention, the files to be tested of the target software are obtained, the incremental data in the files to be tested are determined, the incremental data are only tested, and the accurate fine granularity is adopted for testing, so that a large number of redundant files in the test content are avoided, the test workload is reduced, and the test efficiency is improved.
Drawings
Fig. 1 is a schematic terminal structure diagram of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart diagram illustrating an embodiment of a transmission testing method of software according to the present invention;
FIG. 3 is a detailed flowchart of step S20 in FIG. 2;
FIG. 4 is a schematic flow chart diagram illustrating a test delivery method of software according to yet another embodiment of the present invention;
FIG. 5 is a flowchart illustrating a transmitting and testing method of software according to another embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The main solution of the embodiment of the invention is as follows:
acquiring a source code file corresponding to a to-be-transmitted version of target software;
determining delta data in the source code file;
loading, compiling and packaging are carried out according to the incremental data to obtain sending and testing version data;
and sending the transmitted and measured version data to a test terminal, wherein the test terminal upgrades and runs the installed target software according to the transmitted and measured version data, and feeds back the running parameters.
In the prior art, when software is sent, a complete file of a certain version of software is usually sent and tested. However, sending and testing a complete file of a certain version of software results in a large number of redundant files in the test content, which increases unnecessary test workload and deployment workload, thus resulting in lower test efficiency and bringing risks to system operation.
The invention provides a solution, which avoids a large number of redundant files in test contents by acquiring the files to be tested of the target software, determining the incremental data in the files to be tested, and only transmitting and testing the incremental data and adopting accurate fine granularity to transmit and test, thereby reducing the test workload and improving the test efficiency.
As shown in fig. 1, fig. 1 is a schematic terminal structure diagram of a hardware operating environment according to an embodiment of the present invention.
The terminal of the embodiment of the invention can be a server.
As shown in fig. 1, the terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include an operating system, a network communication module, a user interface module, and a test program of software therein.
In the terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and the processor 1001 may be configured to invoke a test program of the software stored in the memory 1005 and perform the following operations:
acquiring a source code file corresponding to a to-be-tested version of target software from a source code library;
determining delta data in the source code file;
loading, compiling and packaging are carried out according to the incremental data to obtain sending and testing version data;
and sending the transmitted and measured version data to a test terminal, wherein the test terminal upgrades and runs the installed target software according to the transmitted and measured version data, and feeds back the running parameters.
Further, the processor 1001 may call a test program of the software stored in the memory 1005, and further perform the following operations:
acquiring a source code file corresponding to the reference version of the target software;
and comparing the source code file corresponding to the version to be tested with the source code file corresponding to the reference version to obtain the incremental data.
Further, the processor 1001 may call a test program of the software stored in the memory 1005, and further perform the following operations:
acquiring a sending and testing type of the target software;
when the transmission and test type of the target software is full-scale transmission, taking the initial version of the target software as the reference version, and acquiring a source code file corresponding to the initial version;
and when the sending and testing type of the target software is increment sending, taking the adjacent version of the version to be sent and tested as the reference version, and acquiring a source code file corresponding to the adjacent version.
Further, the processor 1001 may call a test program of the software stored in the memory 1005, and further perform the following operations:
obtaining upgrading step information corresponding to the transmitted and measured version data;
outputting the upgrading step information;
and when a modification instruction of the upgrading step information triggered by a user is received, modifying the upgrading step information according to the modification instruction, wherein the test terminal upgrades the installed target software according to the modified upgrading step information and the version data to be tested.
Further, the processor 1001 may call a test program of the software stored in the memory 1005, and further perform the following operations:
when a test sending instruction triggered by a user is received, acquiring a plurality of version information of the target software from the source code library, generating a version list, and outputting the version list;
and when a selection instruction of the version list triggered by the user is received, taking the version corresponding to the selection instruction as the to-be-tested version of the target software.
Further, the processor 1001 may call a test program of the software stored in the memory 1005, and further perform the following operations:
determining the type of a test terminal corresponding to the transmitted test version data;
and sending the data of the sent test version to a test terminal corresponding to the type of the test terminal.
Further, the processor 1001 may call a test program of the software stored in the memory 1005, and further perform the following operations:
and outputting a test result according to the operation parameters when the operation parameters fed back by the test terminal are received.
Further, the processor 1001 may call a test program of the software stored in the memory 1005, and further perform the following operations:
when receiving a checking instruction of the test result triggered by a user, sending the checking instruction to the test terminal, wherein when receiving the checking instruction, the test terminal compares the version data to be tested with the upgrade generation file of the target software and feeds back the comparison result;
and when a comparison result fed back by the test terminal is received, outputting a check result according to the comparison result.
Referring to fig. 2, in an embodiment, the software testing method includes the following steps:
step S10, acquiring a source code file corresponding to the version to be tested of the target software from the source code library;
in this embodiment, in the development and improvement process of the target software, different portions of the target software are generally divided into different development branches, and different software versions are generated according to different stages of each development branch. Thus, different versions of software typically exist when delivering target software. And after the version to be tested of the target software is determined, acquiring a source code file corresponding to the version to be tested from the source code library. The source code files corresponding to a plurality of versions are usually stored in a source code library of a file server, and are read from the source code library of the file server when the source code files corresponding to a certain version are needed. The version to be tested of the target software can be determined according to the creation time or the modification time of a plurality of software versions of the target software in the file server, the software version with the shortest creation time or the modification time and the current time is used as the version to be tested of the target software, or the version to be tested is determined according to the selection of a user by displaying a list corresponding to the plurality of software versions of the target software. The user can trigger the selection instruction at the server side or remotely access the server through the client side or the browser webpage to trigger the selection instruction. Correspondingly, the list corresponding to the multiple software versions of the target software can be correspondingly displayed on the server side, or the client side, the browser webpage and other terminals.
Step S20, determining the incremental data in the source code file;
s30, loading, compiling and packaging according to the incremental data to obtain sending and testing version data;
in this embodiment, the source code files corresponding to the software versions are all files corresponding to the whole software, including source code files modified by developers and source code files unmodified. After a source code file corresponding to the version to be tested is obtained, incremental data in the source code file is determined. The incremental data is a modified source code file and belongs to a part of the whole source code file. The source code file of each version is correspondingly provided with upgrading step information, when the test terminal upgrades the target software according to the source code file, the target software is upgraded according to the upgrading step information, therefore, after the incremental data in the source code file is determined and the version data to be tested is obtained, the upgrading step information corresponding to the version data to be tested can be generated according to the content of the version data to be tested and the upgrading step information corresponding to the content in the source code file, and, after the upgrade step information of the version data to be tested is generated, the upgrade step information of the version data to be tested can be output, so that the user can modify, add, delete and replace the information of the upgrading step of the transmitted version data, namely, when receiving the modification instruction of the upgrading step information triggered by the user, modifying the upgrading step information according to the modification instruction, and the test terminal upgrades the target software according to the modified upgrading step information and the transmitted test version data. In addition, because the incremental data is generally a source code, after the incremental data in the source code file is determined, the operations such as loading, compiling and packaging, generating a compiling item and the like are performed on the incremental data, so that the source code is converted into a target program in a machine language format, and the version data to be tested is obtained.
And step S40, sending the version sending and testing data to a test terminal, wherein the test terminal upgrades and runs the installed target software according to the version sending and testing data, and feeds back the running parameters.
In this embodiment, the test terminal is a terminal adapted to the version to be tested of the target software, and may be a server or other intelligent terminal. After the transmitted test version data is determined, the type of the test terminal corresponding to the transmitted test version data can be obtained, and the transmitted test version data is transmitted to the test terminal corresponding to the type of the test terminal. For example, when the test terminal is a server, if the test terminal type corresponding to the transmitted test version data is a web server, the transmitted test version data is transmitted to the web server communicated with the server for testing, and if the test terminal type corresponding to the transmitted test version data is a DataBase (DB) server, the transmitted test version data is transmitted to the DataBase server communicated with the server for testing; when the test terminal is a smart phone, if the type of the test terminal corresponding to the sent test version data is an android terminal, the sent test version data is sent to the android terminal communicated with the server for testing. Of course, the sending and testing version data in the source code file of the version to be sent and tested corresponding to the type of the testing terminal selected by the user can be obtained according to the sending and testing version data corresponding to the type of the testing terminal, and the sending and testing version data is sent to the testing terminal for testing. The test terminal upgrades the installed target software according to the received version data to be tested and runs for a period of time, and feeds back the running parameters of the target software in the period of time, so as to form a test result, wherein the upgrading of the target software generally replaces the file content corresponding to the target software in the test terminal with the file content in the version data to be tested.
In the technical scheme disclosed in this embodiment, a large number of redundant files in test contents are avoided by acquiring the to-be-transmitted file of the target software, determining the incremental data in the to-be-transmitted file, transmitting and testing only the incremental data, and transmitting and testing with accurate fine granularity, so that the test workload is reduced, and the test efficiency is improved.
In another embodiment, as shown in fig. 3, on the basis of the embodiment shown in fig. 2, the step S20 includes:
step S21, acquiring a source code file corresponding to the reference version of the target software;
in this embodiment, after the source code file corresponding to the to-be-tested version of the target software is obtained, the source code file corresponding to the reference version of the target software is obtained. The reference version of the target software is an unmodified version, e.g., an initial version of the target software. The reference version of the target software may be determined based on the type of transmission test of the target software. For example, when the delivery type of the target software is full delivery, the initial version of the target software or the initial version of a certain development branch of the target software may be used as the reference version of the target software, and when the delivery type of the target software is incremental delivery, the adjacent version of the to-be-delivered version of the target software may be used as the reference version of the target software, where the initial version of the target software refers to the version of the target software when the target software is first operated online, the initial version of a certain development branch refers to the version of the target software when the development branch corresponding to the to-be-delivered version is formed, and the adjacent version of the to-be-delivered version refers to the version that is last delivered and tested in the whole development process, or the version that is last delivered and tested in the development branch corresponding to the to-be-delivered version. If the last version does not exist, the reference version of the target software can only be determined according to full-scale measurement. As another determination method of the reference version, according to a time point input by the user, the first version after the time point may be used as the reference version, or a version selected by the user may be used as the reference version. Correspondingly, when the full-scale transmission is carried out, the source code file corresponding to the initial version is used as the source code file corresponding to the reference version, and when the full-scale transmission is carried out, the source code file corresponding to the adjacent version is used as the source code file corresponding to the reference version. In addition, after the source code file corresponding to the to-be-tested version of the target software is obtained, a configuration option interface can be displayed so that a user can select the testing type of the target software, namely the testing type is determined according to the selection of the user. The configuration option interface can also comprise options of information such as compiler version, base framework version and the like.
Step S22, comparing the source code file corresponding to the to-be-tested version with the source code file corresponding to the reference version to obtain the incremental data.
In this embodiment, after the source code file corresponding to the reference version is obtained, the source code file corresponding to the version to be tested is compared with the source code file corresponding to the reference version to obtain incremental data. For example, if a certain file exists in the source code file corresponding to the version to be tested but does not exist in the corresponding position in the source code file corresponding to the reference version, the certain file is used as the added data in the incremental data, and if a certain file exists in the source code file corresponding to the reference version but does not exist in the corresponding position in the source code file corresponding to the version to be tested, the certain file is used as the deleted data in the incremental data. And integrating the newly added data and the deleted data to obtain the incremental data. Correspondingly, when the upgrading step information corresponding to the version data to be transmitted and measured is generated, the upgrading step information corresponding to the newly added data is generated according to the upgrading step information corresponding to the source code file of the version to be transmitted and measured, the upgrading step information corresponding to the deleted data is generated according to the upgrading step information corresponding to the source code file of the reference version, and the upgrading step information corresponding to the version data to be transmitted and measured can be obtained through integration.
In the technical scheme disclosed in this embodiment, the source code file corresponding to the reference version is acquired, and the source code file corresponding to the version to be transmitted and tested is compared with the source code file corresponding to the reference version to obtain the incremental data, so that the purpose of acquiring the modified file in the source code file corresponding to the version to be transmitted and tested is achieved.
In another embodiment, as shown in fig. 4, on the basis of any one of the embodiments shown in fig. 2 to 3, before the step S10, the method further includes:
step S01, when a test sending instruction triggered by a user is received, acquiring multiple version information of the target software from the source code library, generating a version list, and outputting the version list;
in this embodiment, the user may trigger the sending instruction at the server, or remotely access the server through the client or the browser webpage to trigger the sending instruction. When a sending and testing instruction triggered by a user is received, acquiring information of multiple versions of target software from a source code library of a file server local to the server or communicated with the server, generating a version list according to the information of the multiple versions, and outputting the version list to prompt the user of the versions which can be sent and tested, wherein the version list can be sorted according to the creation time or modification time of the multiple versions of the target software, and the user can input a specified time period after the server outputs the version list to display the multiple versions in a certain time period.
Step S02, when receiving the selection instruction of the version list triggered by the user, taking the version corresponding to the selection instruction as the to-be-tested version of the target software.
In this embodiment, after the version list is output, if a selection instruction of the version list triggered by a user is received, a version corresponding to the selection instruction is used as a to-be-tested version of the target software. And moreover, a preset time can be set, and if a selection instruction of the version list triggered by the user is not received within the preset time, the version with the shortest creating time or modifying time and the current time is used as the version to be transmitted and tested of the target software.
In the technical scheme disclosed in this embodiment, when a sending and testing instruction triggered by a user is received, the version list is displayed, and the version corresponding to the selection instruction of the version list of the user is used as the to-be-sent and tested version of the target software, so that the purpose of determining the to-be-sent and tested version according to the selection of the user is achieved.
In another embodiment, as shown in fig. 5, on the basis of the embodiment shown in any one of fig. 2 to 4, after step S40, the method further includes:
and step S50, outputting a test result according to the operation parameters when the operation parameters fed back by the test terminal are received.
In this embodiment, after the data of the version to be tested is sent to the test terminal, if the operation parameters fed back by the test terminal are received, the test result is output to the user according to the operation parameters. And after receiving the operation parameters fed back by the test terminal, the server side judges whether the operation parameters meet the expected operation parameter standard, if so, outputs a test result with normal operation, and if not, outputs a test result with abnormal operation. Further, after the test result is output to the user, if an inspection instruction of the test result triggered by the user is received, the inspection instruction is sent to the test terminal, when the test terminal receives the test instruction, the received version sending and testing data and a file generated when the target software is upgraded according to the version sending and testing data are compared according to a preset strategy, and the comparison result is fed back to the server side, wherein the preset strategy can be the number of the files, the size of the files, the modification date and the like. If the server receives the comparison result fed back by the test terminal, the server outputs a check result according to the comparison result, namely, which files are wrongly updated or abnormally operated are displayed. The checking result may include types of "success", "error", "warning", etc., and different font colors are displayed according to the different types to more clearly prompt the user. The user can analyze according to the checking result, and then pertinently improve the data of the version to be tested or the source code file corresponding to the version to be tested, thereby realizing the modification and optimization of the target software.
In the technical scheme disclosed in this embodiment, when the operation parameters fed back by the test terminal are received, the test result is output according to the operation parameters, so that a user can know the test result of the to-be-tested version of the software, and the user can modify and optimize the software conveniently.
In addition, an embodiment of the present invention further provides a server, where the server includes: the test system comprises a memory, a processor and a software test program stored on the memory and capable of running on the processor, wherein the software test program realizes the steps of the software test method according to the embodiment when being executed by the processor.
In addition, an embodiment of the present invention further provides a software transmission and test system, where the software transmission and test system includes:
a server, the server being the server of the above embodiment;
and the test terminal is in network communication with the server.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. The software transmitting and testing method is characterized by comprising the following steps of:
acquiring a source code file corresponding to a to-be-tested version of target software from a source code library;
determining delta data in the source code file;
loading, compiling and packaging are carried out according to the incremental data to obtain sending and testing version data;
and sending the transmitted and measured version data to a test terminal, wherein the test terminal upgrades and runs the installed target software according to the transmitted and measured version data, and feeds back the running parameters.
2. The method of claim 1, wherein the step of determining delta data in the source code file comprises:
acquiring a source code file corresponding to the reference version of the target software;
and comparing the source code file corresponding to the version to be tested with the source code file corresponding to the reference version to obtain the incremental data.
3. The method for transmitting and testing software according to claim 2, wherein the step of obtaining the source code file corresponding to the reference version of the target software comprises:
acquiring a sending and testing type of the target software;
when the transmission and test type of the target software is full-scale transmission, taking the initial version of the target software as the reference version, and acquiring a source code file corresponding to the initial version;
and when the sending and testing type of the target software is increment sending, taking the adjacent version of the version to be sent and tested as the reference version, and acquiring a source code file corresponding to the adjacent version.
4. The method for transmitting software according to claim 1, wherein before the step of transmitting the transmission test version data to a test terminal, the method further comprises:
obtaining upgrading step information corresponding to the transmitted and measured version data;
outputting the upgrading step information;
and when a modification instruction of the upgrading step information triggered by a user is received, modifying the upgrading step information according to the modification instruction, wherein the test terminal upgrades the installed target software according to the modified upgrading step information and the version data to be tested.
5. The method for delivering and testing software according to claim 1, wherein before the step of obtaining the source code file corresponding to the version to be delivered and tested of the target software from the source code library, the method further comprises:
when a test sending instruction triggered by a user is received, acquiring a plurality of version information of the target software from the source code library, generating a version list, and outputting the version list;
and when a selection instruction of the version list triggered by the user is received, taking the version corresponding to the selection instruction as the to-be-tested version of the target software.
6. The method for transmitting software according to claim 1, wherein the step of transmitting the transmission test version data to a test terminal comprises:
determining the type of a test terminal corresponding to the transmitted test version data;
and sending the data of the sent test version to a test terminal corresponding to the type of the test terminal.
7. The method for transmitting software according to claim 1, wherein after the step of transmitting the transmission test version data to a test terminal, the method further comprises:
and outputting a test result according to the operation parameters when the operation parameters fed back by the test terminal are received.
8. The method for transmitting and testing software of claim 7, wherein the method for transmitting and testing software further comprises:
when receiving a checking instruction of the test result triggered by a user, sending the checking instruction to the test terminal, wherein when receiving the checking instruction, the test terminal compares the version data to be tested with the upgrade generation file of the target software and feeds back the comparison result;
and when a comparison result fed back by the test terminal is received, outputting a check result according to the comparison result.
9. A server, characterized in that the server comprises: memory, processor and software test program stored on the memory and executable on the processor, the software test program, when executed by the processor, implementing the steps of the method of testing software according to any one of claims 1 to 8.
10. A system for transmitting and testing software, the system comprising:
a server, the server of claim 9;
and the test terminal is in network communication with the server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910856276.2A CN110609793A (en) | 2019-09-10 | 2019-09-10 | Software transmitting and testing method, server and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910856276.2A CN110609793A (en) | 2019-09-10 | 2019-09-10 | Software transmitting and testing method, server and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110609793A true CN110609793A (en) | 2019-12-24 |
Family
ID=68892626
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910856276.2A Pending CN110609793A (en) | 2019-09-10 | 2019-09-10 | Software transmitting and testing method, server and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110609793A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160378462A1 (en) * | 2015-05-22 | 2016-12-29 | Huawei Technologies Co., Ltd. | Method, Apparatus, and System for Implementing JAVA Application Installation by Means of Cloud Compilation |
| CN106919378A (en) * | 2016-08-24 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Application based on increment updates and method of testing and system, server and client |
| CN107153540A (en) * | 2017-04-19 | 2017-09-12 | 畅捷通信息技术股份有限公司 | Incremental build method and device |
| CN109902005A (en) * | 2019-02-19 | 2019-06-18 | 广州云测信息技术有限公司 | A kind of method and system of automatic test |
| US20190220262A1 (en) * | 2016-06-08 | 2019-07-18 | Veriversion Labs Ltd. | Methods and systems of software testing, distribution, installation and deployment |
-
2019
- 2019-09-10 CN CN201910856276.2A patent/CN110609793A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160378462A1 (en) * | 2015-05-22 | 2016-12-29 | Huawei Technologies Co., Ltd. | Method, Apparatus, and System for Implementing JAVA Application Installation by Means of Cloud Compilation |
| US20190220262A1 (en) * | 2016-06-08 | 2019-07-18 | Veriversion Labs Ltd. | Methods and systems of software testing, distribution, installation and deployment |
| CN106919378A (en) * | 2016-08-24 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Application based on increment updates and method of testing and system, server and client |
| CN107153540A (en) * | 2017-04-19 | 2017-09-12 | 畅捷通信息技术股份有限公司 | Incremental build method and device |
| CN109902005A (en) * | 2019-02-19 | 2019-06-18 | 广州云测信息技术有限公司 | A kind of method and system of automatic test |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8612947B2 (en) | System and method for remotely compiling multi-platform native applications for mobile devices | |
| US9608893B2 (en) | Methods and systems for parsing data objects | |
| CN109840206B (en) | Data testing method, device, terminal and storage medium | |
| CN108920359B (en) | Application program testing method and device, storage medium and electronic device | |
| CN111045944A (en) | Regression testing method, device and system and computer readable storage medium | |
| CN112559354A (en) | Front-end code specification detection method and device, computer equipment and storage medium | |
| US10866803B2 (en) | Generating interaction libraries | |
| CN113568839A (en) | Method, device, equipment and medium for software testing and statistical test coverage rate | |
| CN110908702A (en) | Version switching method, version switching device, computer equipment and storage medium | |
| CN113064630A (en) | Mobile terminal APP automatic packaging method and system, electronic device and storage medium | |
| CN110851151B (en) | Method, device, terminal, server and storage medium for pre-installing application | |
| CN108804315B (en) | Test method and device applied to dynamic development, electronic equipment and storage medium | |
| CN112770108B (en) | Performance test method, device and system and computer readable storage medium | |
| CN107729043B (en) | Method and device for checking increment upgrade package and computer readable storage medium | |
| CN112965731B (en) | Method, device, equipment and storage medium for Flutter hot update based on Tinker | |
| CN107678969B (en) | Test version release method and device, version control equipment and test machine | |
| CN112988578A (en) | Automatic testing method and device | |
| CN116643761A (en) | Customized mirror image manufacturing and deploying method, device, terminal and medium | |
| CN110609793A (en) | Software transmitting and testing method, server and system | |
| CN115145825A (en) | Single-chip microcomputer software parameter adjusting method and system | |
| CN112947943A (en) | Software configuration compiling method, electronic device and readable storage medium | |
| CN115604307A (en) | Processing method and device for upgrading log, terminal equipment and computer medium | |
| CN114003257A (en) | Upgrading method and device | |
| CN111427795A (en) | Code test control method and device, storage medium and electronic equipment | |
| CN111045724A (en) | Query method and device for call chain information and 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191224 |
|
| RJ01 | Rejection of invention patent application after publication |