CN100501697C - Software version upgrade mounting test system and method thereof - Google Patents
Software version upgrade mounting test system and method thereof Download PDFInfo
- Publication number
- CN100501697C CN100501697C CNB2007101244179A CN200710124417A CN100501697C CN 100501697 C CN100501697 C CN 100501697C CN B2007101244179 A CNB2007101244179 A CN B2007101244179A CN 200710124417 A CN200710124417 A CN 200710124417A CN 100501697 C CN100501697 C CN 100501697C
- Authority
- CN
- China
- Prior art keywords
- software
- version
- installation
- test
- information
- 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.)
- Expired - Fee Related
Links
Images
Abstract
The invention discloses an system and a method of upgrading, installing and testing a software version, the method comprises the steps: 1) software installation and test initialization: a software installation and test initialization module is utilized to input the basic attribute information of the version into a software version attribute information bank, and make a backup of the software installation version into a software installation version bank; 2) software version upgrade test: a test task processing module generates the software installation test task in accordance with the input software version number requiring the test; according to the generated installation and test task, the software shall be downloaded from the software installation version bank and the software operation version backup bank to conduct the test; 3) the test results process module collection and process the software installation result information, so as to output an installation report. The system and the method of upgrading, installing and testing the software version provided by the invention realizes the automatic test on software upgrade installation, improves the software test cover degree, greatly advances the test work efficiency, and improves the ease-of-use on test operation, thereby being helpful to enhance the test quality.
Description
[technical field]
The present invention relates to software upgrading mounting test system and method.
[background technology]
Software is planned from beginning, and ends to withdrawing from the market, and is called software life-cycle.In general, software life-cycle comprises plan, exploitation, moves three periods, can be divided into some littler stages each period again.The main task in plan period is the analysis user requirement, the feasibility of analyzing the main target of new system and developing this system.Exploitation will be finished design period and realize that two main tasks is concrete, specifically is divided into demand analysis, summary design, detailed design, coding, test, and wherein encoding and testing is latter two stage of software development phase.Run time be last period of software life cycle, the peopleware mainly is to carry out software maintenance in the work in this period.
At software maintenance stage,, can research and develop and issue new software version with the renewal of version requirement and the discovery of software bug.The software of issue all can correspondingly be with a software version number, and software version is divided into large paper edition and little version according to the difference of big demand.Large paper edition generally identifies with similar Version1.0,2.0 and so on version.Between two large paper editions, can research and develop the little demand of part, or maintenance software bug, between two large paper editions, have a series of minor release/point release again.Minor release/point release generally adopts the form sign of Service Pack 1, Service Pack 2.
A series of versions of research and development of software issue generally require than the upgrading of higher release requirement support to lowest version.1.0,2.0,3.0 3 large paper editions of Version have been issued as certain software; Version 1.0 Service Pack 1,2 two versions of Version 1.0Service Pack have been issued again respectively at Version 1.0; Version 2.0Service Pack 1,2 two versions of Version 2.0 Service Pack have been issued again respectively at Version 2.0.Be example then, require Version3.0 to support following software function with Version 3.0 versions:
1. support that Version 3.0 initially installs;
2. support " upgrading from Version1.0 to Version3.0 is installed ";
3. support " installing " from the upgrading of Version 1.0 Service Pack 1 to Version3.0;
4. support " installing " from the upgrading of Version 1.0 Service Pack 2 to Version3.0;
5. support " upgrading from Version2.0 to Version3.0 is installed ";
6. support " installing " from the upgrading of Version 2.0 Service Pack 1 to Version3.0;
7. support " installing " from the upgrading of Version 2.0 Service Pack 2 to Version3.0.
Find out that from top upgrading series along with released version is on the increase, edition upgrading installation testing workload is increasing.Carry out the installation testing of a version, all need to be ready to initial software version environment, for example, if test " is supported ' installing from the upgrading of Version 1.0 Service Pack 2 to Version3.0 ' ", then need to be ready to earlier " Version 1.0 Service Pack2 " software environment, just can carry out " supporting ' installing ' " installation testing from the upgrading of Version 1.0 Service Pack 2 to Version3.0, and the approach of preparing " Version 1.0 Service Pack 2 " software environment has several, for increasing the coverage rate of software test, just need all possible approach are all tested, could guarantee the quality of software.
As can be seen from the above analysis, for the software upgrading installation testing, the test job amount is heavy, if by the manual testing, than the situation that is easier to occur omitting test, cause testing insufficient.If test insufficiently, the version that will have Bug software is published on the market, will increase software vendor's adverse product qualities cost.
[summary of the invention]
Fundamental purpose of the present invention is: overcome above-mentioned weak point of the prior art, a kind of software version upgrade mounting test system and method are provided, realize efficient, perfect edition upgrading test.
For achieving the above object, the present invention proposes a kind of software version upgrade mounting test system, comprising:
Software version attribute information storehouse is used to deposit the base attribute information of software version;
Software is installed version repository, is used to back up a series of software version is installed;
Running software version backup library installs software and comes out by version and running environment full backup that software is successfully checked, uses when being used to recover;
Software installation testing initialization module, be used for the typing software version base attribute information, and the judgement information of software successful installation to software version attribute information storehouse, the software of formally issue is installed version backups to software and install in the version repository;
Test task process module, with described software version attribute information storehouse, software version repository is installed, running software version backup library is related, is used for the software version number automatic generating software version installation testing mission bit stream according to input, and according to test assignment information, downloaded software, and installation testing;
The test result processing module, link to each other with described test task process module, running software version backup library respectively, be used for the message file of reading software version property after the software installation, the software installation results is judged, and generate the software Installation Report.
Above-mentioned software version upgrade mounting test system, also comprise software anomaly version backup library, related with described test result processing module, be used for version and running environment full backup that software is installed and fails successfully to check by software, be used to recover fault in-situ, orientation problem is used.Also comprise test analysis or maintenance module, related with described test task process module, running software version backup library, software anomaly version backup library, be used to browse and check software installation testing result, output function is provided, and several tasks in can the designated mounting task re-execute.
Above-mentioned software version upgrade mounting test system, described base attribute information comprise the upgraded version information of software support, the judgement identification information of software successful installation; Each software is installed version and is all had unique identification software version ID, to distinguish different versions.
Described software is installed version repository and is carried out related by software version ID with software version attribute information storehouse.Described running software version backup library is preserved the installation or the upgrading path of running software version, this operation version, and the software Installation Report; This storehouse is carried out related by software version ID with software version attribute information storehouse.In the described running software version backup library, the difference of associated attribute is installed according to different software, expand the environmental information that the operation version is arranged, comprise language environment, the related software of version, the operating system of operating system, operating system version information, and other additional informations of software in more than one.
Described software anomaly version backup library is preserved the installation or the upgrading path of this operation version simultaneously, and the software Installation Report; This storehouse is carried out related by software version ID with software version attribute information storehouse.In the described software anomaly version backup library, the difference of associated attribute is installed according to different software, expand the environmental information that unusual version is arranged, comprise language environment, the related software of version, the operating system of operating system, operating system version information, and other additional informations of software in more than one.
Above-mentioned software version upgrade mounting test system, described test result processing module backs up for the software of successful installation, and the running software version is backuped in the running software version backup library; Back up for unsuccessful software is installed, out of order running software version is backuped in the software anomaly version backup library.
The present invention proposes a kind of software release upgrade installation testing method simultaneously, may further comprise the steps:
1) software installation testing initialization: after each version issue, utilize software installation testing initialization module that the base attribute information of version is entered in the software version attribute information storehouse, and software is installed version backup to software and install in the version repository;
2) software release upgrade test assignment is handled: test task process module is according to the software version number of the needs test of input, automatic generating software installation testing task; According to the installation testing task that generates, downloaded software is tested from software installation version repository and running software version backup library automatically; After a test assignment is finished, notify the test result processing module to handle installation results automatically;
3) test result processing module collection, process software installation results information, the output Installation Report.
Above-mentioned software release upgrade installation testing method in described step 3), for the running software version of successful installation, backups in the running software version backup library automatically; Back up for unsuccessful software is installed, out of order running software version is backuped in the software anomaly version backup library, so that localization of fault is used afterwards.In described step 3), the test result processing module is also added this at running software version backup library or software anomaly version backup library corresponding software installation path information is installed.In described step 3), the content of test result processing module backup includes but not limited to that other and software such as content under the software installation directory, registration table, startup menu, database file installs file associated; In described step 3), the test result processing module is also installed the difference of associated attribute according to different software, expand the environmental information of installation results, comprise language environment, the related software of version, the operating system of operating system, operating system version information, and other additional informations of software in more than one.
Above-mentioned software release upgrade installation testing method, the concrete processing procedure of described step 3) software installation results information comprises:
The test result processing module is obtained the installation checking information of version from task base attribute storehouse;
Whether according to checking information is installed, it is successful to check this to install;
If success according to checking information, generates the installation results report; And installation results backuped to
Running software version backup library, and add installation path information;
If failure is installed,, generate the installation results report according to checking information; Installation results is backed up
To software anomaly version backup library, and add installation path information.
Above-mentioned software release upgrade installation testing method after described step 3), also comprises step 4): by test analysis or maintenance module, check or analyze the installation testing result of each task, and can test again several tasks in the task.After described step 4), also comprise step 5): regularly software anomaly version backup library is cleared up by test analysis or maintenance module, deletion surpasses the software anomaly version backup of regular period, reduces taking storage space.
Above-mentioned software release upgrade installation testing method, described step 1) test initialization flow process comprises: after the formal issue of a software version, start software installation testing initialization module, input released version essential information, the essential information of software is described, and designated software sign ID; The input version is to the legacy version support information of upgrading, and illustrates that this version supports the upgrading of which software version, and this upgrade information provides installation path information for creating the software test task; Whether the input version is installed the authorization information of passing through, be used for passing judgment on after the software installation finishes this software and install successful; Add released version and version repository is installed, software version is preserved in the database convenient search and copy to software.
Above-mentioned software release upgrade installation testing method, described step 2) the software release upgrade test assignment is handled idiographic flow and is comprised:
21) selection needs the software version number of test;
22) generate the tabulation of version test assignment;
23) check in the version test tabulation whether test assignment is arranged, if do not have, then test assignment finishes, if having, continues next step;
24), carry out installation testing according to the installation testing mission bit stream;
25) after this task was installed and finished, notice test result processing module was handled installation results information;
26) current complete task in the tabulation of deletion version test assignment is returned step 23 then, finishes up to test assignment;
Above-mentioned steps 22) generates the method for version test assignment tabulation: by the exhaustive search method, find out the installation path that institute might arrive a certain appointment operation version, form all version test assignments that this appointments moves version and tabulate.
Software version upgrade mounting test system provided by the invention and method, the automatic test that realization is installed software upgrading, improve the coverage of software test, can save manpower, significantly promote the work efficiency of test, improve the test operation ease for use, automatic test has avoided occurring omitting the situation of test, help to promote test mass, guarantee the integrality of test.
[description of drawings]
The structural representation of Fig. 1 software version upgrade mounting test system embodiment;
Fig. 2 has described the software installation testing initialization flow process of embodiment;
Fig. 3 has described the treatment scheme of the software upgrading installation testing task processing module of embodiment;
The test assignment tabulation that Fig. 4 has described embodiment generates the signal situation;
Fig. 5 example " A-〉B-〉C-〉J " software installation testing task executions process;
Fig. 6 represents the processing procedure to the software installation results of embodiment.
[embodiment]
Also the present invention is described in further detail in conjunction with the accompanying drawings below by specific embodiment.
Fig. 1 is the structural representation of software version upgrade mounting test system embodiment of the present invention; Comprise
1) software version attribute information storehouse, be used to deposit the base attribute information of software version, as the upgraded version information of software support, the judgement identification information of software successful installation, each software is installed version and is all carried out unique identification software version ID, to distinguish different versions.
2) software is installed version repository; Software is installed version repository and is used to back up a series of software installation version.This storehouse is carried out related by " software version ID " with software version attribute information storehouse.
3) running software version backup library; Software installed and passed through version and the running environment full backup that software successfully checks and come out, be used for recovering to wait other purposes to use.The running software version has not only been preserved in this storehouse, also preserves the installation/upgrading path of this operation version, and the software Installation Report.This storehouse is carried out related by software version ID with software version attribute information storehouse.
4) software anomaly version backup library; Software installed do not passed through version and running environment full backup that software successfully checks and come out, be used to recover fault in-situ, orientation problem is used.Installation/the upgrading path of this operation version is also preserved in this storehouse simultaneously, and the software Installation Report.This storehouse is carried out related by software version ID with software version attribute information storehouse.
5) software installation testing initialization module: this module is used for the base attribute information of typing software version, and the judgement information of software successful installation, by this module, the software of formally issuing can also be installed version and backup in the software installation version repository.
6) test task process module: Input Software version number, automatic generating software version installation testing mission bit stream, and according to test assignment information, the downloaded software installation testing.
7) test result processing module: after the software installation, the message file in the software installation results processing module reading software version property is judged the software installation results, and generates the software Installation Report.Software for successful installation backs up, and the running software version is backuped in " running software version backup library ".Back up for unsuccessful software is installed, out of order running software version is backuped in " software anomaly version backup library ".The content of backup includes but not limited to that other and software such as content under the software installation directory, registration table, startup menu, database file installs file associated; The difference of associated attribute is installed according to different software, can expand the environmental information of installation results, as: the version information of the version of operating system, operating system, the language environment of operating system (Chinese, English etc.), related software (as the data library software), and other additional informations of software.
8) test analysis/maintenance module: this module is used to browse checks software installation testing result, and printout/functions such as document output are provided, and several tasks in can the designated mounting task re-execute, and strengthens the software installation testing.This module is cleared up " the software anomaly version backup library " that surpass the regular period, avoids taking too many Computer Storage space.
Above-mentioned software is installed version and is meant: the software of the formal issue of version.This software generally can not be directly used in operation, needs the software that just can move behind the executive software fitting operation.
The running software version is meant: software is installed version through installation steps, be installed on the computer system after, by the software that can normally use of check.
The software anomaly version is meant: software is installed version through installation steps, be installed on the computer system after, the out of order software by check.
Fig. 2 has described software release upgrade installation testing initialization flow process.After the formal issue of a software version, start software installation testing initialization module, input released version essential information is described the essential information of software, and is specified software identification ID; The input version is to the legacy version support information of upgrading, and illustrates that this version supports the upgrading of which software version, and this upgrade information provides installation path information for creating the software test task; The input version is installed the authorization information pass through, be used for software install finish after, pass judgment on this software whether success be installed; Add released version and version repository is installed, software version is preserved in the database convenient search and copy to software.Because some software version is huger, can only preserve the directory information that software is installed the version place in the database, also can obtain needed software by catalogue version is installed.
Fig. 3 has described the treatment scheme of software release upgrade test task process module:
27) selection needs the software version number of test;
28) generate the tabulation of version test assignment;
29) check in the tabulation whether test assignment is arranged, if do not have, then test assignment finishes, if having, continues next step;
30), carry out installation testing according to the installation testing mission bit stream;
31) after this task was installed and finished, notice " test result processing module " was handled installation results information;
32) current complete task in the deletion task list is returned step 3 then, finishes up to test assignment;
Version Version 1.0, Version 1.0 Service Pack 1, Version 1.0Service Pack 2, Version 2.0, Version 2.0 Service Pack 1, Version 2.0Service Pack 2, the Version 3.0 of software are used 1 respectively, 2,3, the n sequence number is represented, then can draw the number of times Tn formula that n version need be installed:
In the formula: Tn: the software installation testing number of times that the needs of expression version n carry out; M: the initial installation number of times of expression version n, general value=1 or 0.For large paper edition, general m=1, the expression large paper edition need be supported initial installation; For Service Pack version, general m=0, expression does not need initial installation, only needs to support to install from the benchmark edition upgrading.
Ti: the approach number might be installed by the institute that represents i version.If version n does not support the upgrading from the i version to the n version to install, then Ti=0.That is to say that the installation number of times of version n only need be added up its installation lowest version of supporting, do not support the version of upgrading not need statistics interior.
Fig. 4 has described the test assignment tabulation and has generated the signal situation:
The dicyclo circle represents that this is that a software is installed version, and real ring circle represents that this is one later operation version is installed.
Among the figure, the single line arrow represents that this is a running software version that generation initially is installed by software; Double-lined arrow represents that this is a running software version that generation is installed by software upgrading.
For each software version is installed, or the running software version all uses the letter sign, as shown in the figure: software is installed the alphabetical A of version 1 usefulness and is represented that running software version 1 usefulness letter b represents that running software version 1SP1 shows C and represents that the rest may be inferred for other.Using each state of letter representation is in order to identify the installation path of software, also can to use other modes to substitute.
As shown in the figure: version J has a single solid arrow and six double solid line arrows, and expression version J can obtain by the initial installation of version I, also can support to install from the upgrading of operation version B, C, D, F, G, H.
From an initial software version is installed,, is just represented an installation testing task of this target version to a paths of object run version.
With running software version 3 (J) is example, and the installation path that can reach this version has:
1, I-〉J: expression obtains moving version J by the initial installation of version I;
2, A-〉B-〉J: expression obtains moving version B by the initial installation of version A, is installed to J by upgrading again;
3, A-〉B-〉C-〉J: expression obtains moving version B by the initial installation of version A, is installed to C by upgrading again, is installed to J by upgrading again;
The rest may be inferred, and every kind of possible installation path is represented an installation testing test assignment.Exhaustive search method that can be by program is found out institute and might be arrived the installation path that moves version J, forms all installation testing task lists.
Fig. 5 example " A-〉B-〉C-〉J " software installation testing task executions process:
1) starting the path is A-〉B-〉C-〉the installation testing task of J;
2) check whether to have in the running software version repository that to meet installation path be A-〉B-〉the operating software version C of C;
3) if having, take out running software version C, return in the computer system, enter step 10;
4) whether if do not have, checking has in the running software version repository that to meet installation path be A-〉the operating software version B of B;
5) if having, taking out the software installation path is A-〉B running software version B, return in the computer system, enter step 8;
6), taking-up software installation version 1 installation version the version repository is installed from software if do not have;
7) carrying out A-〉B initially installs;
8) from software taking-up software version 1SP1 installation version the version repository is installed;
9) carry out B-〉the C installation of upgrading;
10) from software taking-up software installation version 3 the version repository is installed;
11) executive software operation version C-〉the J installation of upgrading;
12) installation task is installed and is finished.
Fig. 6 represents the processing procedure to the software installation results:
1) the test result processing module is obtained the installation checking information of version from task base attribute storehouse;
2) whether according to installation check information, it is successful to check this to install;
3) if success according to fox message, generates the installation results report;
4) and with installation results backup to " running software version backup library ", and add installation path information.
5),, generate the installation results report according to fox message if failure is installed;
6) and with installation results backup to " software anomaly version backup library ", and add installation path information.
Regularly software anomaly version backup library is cleared up by test analysis/maintenance module, deletion surpasses the software anomaly version backup of regular period,
Above content be in conjunction with concrete preferred implementation to further describing that the present invention did, can not assert that concrete enforcement of the present invention is confined to these explanations.For the general technical staff of the technical field of the invention, without departing from the inventive concept of the premise, can also make some simple deduction or replace, all should be considered as belonging to protection scope of the present invention.
Claims (11)
1, a kind of software version upgrade mounting test system comprises:
Software version attribute information storehouse is used to deposit the base attribute information of software version;
Software is installed version repository, is used to back up a series of software version is installed;
Running software version backup library installs software and comes out by version and running environment full backup that software is successfully checked, uses when being used to recover;
Software installation testing initialization module, be used for the typing software version base attribute information, and the judgement information of software successful installation to software version attribute information storehouse, the software of formally issue is installed version backups to software and install in the version repository;
Test task process module, with described software version attribute information storehouse, software version repository is installed, running software version backup library is related, is used for the software version number automatic generating software version installation testing mission bit stream according to input, and according to test assignment information, downloaded software, and installation testing;
The test result processing module, link to each other with described test task process module, running software version backup library respectively, be used for the message file of reading software version property after the software installation, the software installation results is judged, and generate the software Installation Report.
2, software version upgrade mounting test system as claimed in claim 1, it is characterized in that: also comprise software anomaly version backup library, related with described test result processing module, be used for version and running environment full backup that software is installed and fails successfully to check by software, be used to recover fault in-situ, orientation problem is used.
3, software version upgrade mounting test system as claimed in claim 2, it is characterized in that: also comprise test analysis or maintenance module, related with described test task process module, running software version backup library, software anomaly version backup library, be used to browse and check software installation testing result, provide output function, and several tasks in can the designated mounting task re-execute.
4, as claim 2 or 3 described software version upgrade mounting test systems, it is characterized in that: described base attribute information comprises the upgraded version information of software support, the judgement identification information of software successful installation; Each software is installed version and is all had unique identification software version ID, to distinguish different versions; Described running software version backup library is preserved the installation or the upgrading path of running software version, this operation version, and the software Installation Report; Described software anomaly version backup library is preserved the installation or the upgrading path of out of order operation version simultaneously, and the software Installation Report; Described software installation version repository, running software version backup library, software anomaly version backup library carry out related by software version ID with software version attribute information storehouse.
5, as claim 2 or 3 described software version upgrade mounting test systems, it is characterized in that: described test result processing module backs up for the software of successful installation, and the running software version is backuped in the running software version backup library; Back up for unsuccessful software is installed, out of order running software version is backuped in the software anomaly version backup library.
6, a kind of software release upgrade installation testing method may further comprise the steps:
1) software installation testing initialization: after each version issue, utilize software installation testing initialization module that the base attribute information of version is entered in the software version attribute information storehouse, and software is installed version backup to software and install in the version repository;
2) software release upgrade test assignment is handled: test task process module is according to the software version number of the needs test of input, automatic generating software installation testing task; According to the installation testing task that generates, downloaded software is tested from software installation version repository and running software version backup library automatically; After a test assignment is finished, notify the test result processing module to handle installation results automatically;
3) test result processing module collection, process software installation results information, the output Installation Report.
7, software release upgrade installation testing method as claimed in claim 6 is characterized in that: in described step 3), for the running software version of successful installation, backup to automatically in the running software version backup library; Back up for unsuccessful software is installed, out of order running software version is backuped in the software anomaly version backup library, so that localization of fault is used afterwards; Add this at running software version backup library or software anomaly version backup library corresponding software installation path information is installed; Backup is added content and is comprised that content under the software installation directory, registration table, startup menu, database file and other and software install file associated; The difference of associated attribute being installed according to different software expands the environmental information of installation results, comprise language environment, the related software of version, the operating system of operating system, operating system version information, and other additional informations of software in more than one.
8, software release upgrade installation testing method as claimed in claim 6, it is characterized in that: after described step 3), also comprise step 4): by test analysis or maintenance module, check or analyze the installation testing result of each task, and several tasks in the task are tested again.
9, software release upgrade installation testing method as claimed in claim 6 is characterized in that, the concrete processing procedure of described step 3) software installation results information comprises:
The test result processing module is obtained the installation checking information of version from task base attribute storehouse;
Whether according to checking information is installed, it is successful to check this to install;
If success according to checking information, generates the installation results report; And installation results backuped to running software version backup library, and add installation path information;
If failure is installed,, generate the installation results report according to checking information; Installation results is backed up
To software anomaly version backup library, and add installation path information.
10, software release upgrade installation testing method as claimed in claim 6, it is characterized in that, described step 1) test initialization flow process comprises: after the formal issue of a software version, start software installation testing initialization module, input released version essential information, the essential information of software is described, and designated software sign ID; Or the input version is to the legacy version support information of upgrading, and illustrates that this version supports the upgrading of which software version, provides installation path information for creating the software test task; Or import version the authorization information of passing through is installed, be used for this software of software installation end back judge and whether successfully install; Or add released version and to software version repository is installed, software version is preserved in the database convenient search and copy.
11, software release upgrade installation testing method as claimed in claim 6 is characterized in that, described step 2) idiographic flow handled of software release upgrade test assignment comprises:
21) selection needs the software version number of test;
22) generate the tabulation of version test assignment;
23) check in the tabulation of version test assignment whether test assignment is arranged, if do not have, then test assignment finishes, if having, continues next step;
24), carry out installation testing according to test assignment information;
25) after this task was installed and finished, notice test result processing module was handled installation results information;
26) current complete task in the deletion task list is returned step 23 then), finish up to test assignment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2007101244179A CN100501697C (en) | 2007-11-09 | 2007-11-09 | Software version upgrade mounting test system and method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2007101244179A CN100501697C (en) | 2007-11-09 | 2007-11-09 | Software version upgrade mounting test system and method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101158917A CN101158917A (en) | 2008-04-09 |
| CN100501697C true CN100501697C (en) | 2009-06-17 |
Family
ID=39307025
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2007101244179A Expired - Fee Related CN100501697C (en) | 2007-11-09 | 2007-11-09 | Software version upgrade mounting test system and method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100501697C (en) |
Families Citing this family (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101789886B (en) * | 2009-01-23 | 2011-12-28 | 中兴通讯股份有限公司 | Environment setup automation system of distribution type environment and method |
| CN101789888B (en) * | 2010-01-12 | 2012-04-11 | 腾讯科技（深圳）有限公司 | Detection method and device for software installation |
| CN102255748B (en) * | 2011-06-27 | 2017-12-29 | 中兴通讯股份有限公司 | Automatization test system and method, version server and terminal |
| CN102799522A (en) * | 2012-06-28 | 2012-11-28 | 浪潮(北京)电子信息产业有限公司 | Managing method and system for software version tracing test |
| CN103516559A (en) * | 2012-12-13 | 2014-01-15 | Tcl集团股份有限公司 | Method and system for testing application compatibility of intelligent terminal |
| CN103279419A (en) * | 2013-06-09 | 2013-09-04 | 浪潮电子信息产业股份有限公司 | Automation version verifying method and system based on B/S structural system |
| CN103336688A (en) * | 2013-06-20 | 2013-10-02 | 中标软件有限公司 | Software integrating method and system oriented to cloud computing software research and development process |
| CN103455418A (en) * | 2013-08-02 | 2013-12-18 | 深圳创维数字技术股份有限公司 | Intelligent terminal testing method and intelligent terminal testing device |
| CN104035799A (en) * | 2014-06-19 | 2014-09-10 | 浪潮电子信息产业股份有限公司 | Method for customizable upgrading of software |
| CN104461866B (en) * | 2014-11-04 | 2017-08-29 | 中国广核电力股份有限公司 | The detection method and its detecting system of a kind of abnormal version of software object |
| CN105740137B (en) * | 2014-12-08 | 2018-07-31 | 阿里巴巴集团控股有限公司 | Divide bucket test method and the method, apparatus and system of configuration information are provided |
| CN105302603A (en) * | 2015-10-26 | 2016-02-03 | 广州视睿电子科技有限公司 | Software upgrade method and apparatus |
| CN105653325A (en) * | 2015-12-29 | 2016-06-08 | 北京金山安全软件有限公司 | Method and device for updating data packet in test environment and electronic equipment |
| CN105893026A (en) * | 2016-03-28 | 2016-08-24 | 乐视控股（北京）有限公司 | Software version management system and method |
| CN106708517A (en) * | 2016-12-09 | 2017-05-24 | 上海斐讯数据通信技术有限公司 | Software automatic upgrading test system and method |
| CN106598741B (en) * | 2016-12-16 | 2024-03-01 | 飞狐信息技术（天津）有限公司 | Distributed A/B test method and system for personalized recommendation system and video recommendation system |
| CN107274933A (en) * | 2017-06-14 | 2017-10-20 | 湖南国科微电子股份有限公司 | A kind of method and device for testing solid state hard disc |
| CN107391154A (en) * | 2017-07-31 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of method of testing and test device of system upgrade function |
| CN109511012B (en) * | 2018-11-30 | 2021-06-08 | 深圳创维数字技术有限公司 | Set top box upgrade test method, device, electronic equipment and medium |
| CN109918287A (en) * | 2019-01-16 | 2019-06-21 | 平安普惠企业管理有限公司 | APP upgrading test method, apparatus, computer equipment and storage medium |
| CN109902006A (en) * | 2019-02-20 | 2019-06-18 | 北京安和瑞福信息技术有限公司 | Automated testing method and device |
| CN110377305B (en) * | 2019-07-18 | 2024-03-01 | 上海擎感智能科技有限公司 | Application software upgrading method, terminal and system |
| CN113190248A (en) * | 2021-04-28 | 2021-07-30 | 绿盟科技集团股份有限公司 | Virtualization-based web system upgrade test method and server |
-
2007
- 2007-11-09 CN CNB2007101244179A patent/CN100501697C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN101158917A (en) | 2008-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100501697C (en) | Software version upgrade mounting test system and method thereof | |
| US10540335B2 (en) | Solution to generate a scriptset for an automated database migration | |
| CN100426298C (en) | Method and system for cleaning garbage files | |
| CN101339532B (en) | Web application system automatized test method and apparatus | |
| CN101876943B (en) | Systems and methods for identifying a relationship between multiple interrelated applications in a mainframe environment | |
| CN103365683B (en) | For end-to-end patch automation and integrated method and system | |
| US8745589B2 (en) | Automatic extraction of test case for a build in testing lifecycle | |
| US7343401B2 (en) | Remote maintenance apparatus, terminal connected to the apparatus and computer readable medium for realizing the apparatus and the terminal | |
| WO1998027489A1 (en) | Software release document process control system and method | |
| Fisher et al. | Utilizing Atlassian JIRA for large-scale software development management | |
| CN109753430B (en) | Interface test method of ground data processing system | |
| CN102025778A (en) | Software version upgrading work method based on Shell | |
| US20140181145A1 (en) | Modular Software System for Use in an Integration Software Technology and Method of Use | |
| CN105955749A (en) | Continuous software project integration method and device | |
| CN103279419A (en) | Automation version verifying method and system based on B/S structural system | |
| CN107688531A (en) | Geo-database integration method of testing, device, computer equipment and storage medium | |
| CN101763258B (en) | Software multiplexing method and system | |
| CN101788908A (en) | Batch data processing method supporting breakpoint reget | |
| CN108776643A (en) | A kind of object code merging control method and system based on Version Control flow | |
| CN112882724A (en) | Method for automatic deployment of OpenStack cloud platform pipeline | |
| CN116089220A (en) | Index inspection method and device based on operating system and electronic equipment | |
| JP2009245380A (en) | Job processing system and job testing method | |
| CN103026337A (en) | Distillation and reconstruction of provisioning components | |
| CN113961570A (en) | Real-time acquisition method applied to MYSQL BINLog change data | |
| US7797334B2 (en) | Automated downloading from mainframe to local area network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090617 Termination date: 20161109 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |