CN105868101A - Software testing method - Google Patents
Software testing method Download PDFInfo
- Publication number
- CN105868101A CN105868101A CN201610164884.3A CN201610164884A CN105868101A CN 105868101 A CN105868101 A CN 105868101A CN 201610164884 A CN201610164884 A CN 201610164884A CN 105868101 A CN105868101 A CN 105868101A
- Authority
- CN
- China
- Prior art keywords
- software
- upgrading
- aku
- version
- upgrading configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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/368—Test management for test version control, e.g. updating test cases to a new software version
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a software testing method, and especially relates to a method of automatically testing the software compatibility. The method has the steps of operating an update configuration file, wherein the update configuration file includes an update configuration file path, an update configuration file name, and an update strategy; updating to-be-updated software in a device according to the update configuration file; restarting the device after the update; detecting whether the device can operation normally or not; and detecting whether all the update packets in the update strategy have updated or not.
Description
Technical field
The present invention relates to a kind of method for testing software, be specifically related to the side of a kind of automatic test software compatibility
Method.
Background technology
During software version is issued, software test department is required for testing new software version with old software
With this, compatibility between version, ensures that all legacy version software can after being upgraded to new version software
Normal work.
At present, existing method of testing needs connect host computer or AKU is put into USB flash disk upgrading.Test
Personnel are when test is compatible, and often one version of upgrading is required for manpower intervention, until all versions are all tested
Complete.There is problems in that during it
1. inefficiency.Starting to test to terminate from test, each link is required for manpower intervention.
2. escalation policy coverage rate is inadequate.Manual testing the most only can test from minimum version to highest version,
Or randomly draw version test, and test from highest version to minimum version, owing to testing efficiency reason is past
Toward not covering.
3. escalation policy can not be fixed very well, and anthropic factor is the biggest.During reality is tested, tester
It is possible that maloperation or the phenomenon of test leakage.
Summary of the invention
The application provides a kind of method automatically improving test software compatibility efficiency.
Technical scheme disclosed by the invention includes:
Run upgrading configuration, described upgrading configuration include the path of upgrading configuration and title with
And escalation policy；
According to software to be upgraded in described upgrading configuration updating apparatus；Restart described after upgrading completes
Equipment；
Whether detection equipment can be properly functioning；All AKUs in detection escalation policy are the most all upgraded.
The raising of this method is: improves the efficiency of software compatibility test, utilizes this method to have only to a little
Hit testing results script, it is possible to be automatically performed whole test process；
Software kit required in test can preserve with the form of configuration file, so can avoid test
Cover incomplete problem；
Software kit required in test can preserve with the form of configuration file, it is possible to the most fixing survey
Examination flow process, so can avoid the maloperation mistake artificially caused in test process.
Accompanying drawing explanation
Fig. 1 is the flow chart of software compatibility method of testing.
Detailed description of the invention
Combine accompanying drawing below by detailed description of the invention the present invention is described in further detail.
Fig. 1 is the flow chart of software compatibility method of testing.
Step 1: starting device, equipment energising after, software enter initialization step, terminate initialization step it
After initially enter software compatibility testing process.
Step 2: after software enters flow process, software starts to read corresponding upgrading configuration.Wherein should
Upgrading configuration can include the AKU path of all software versions and name and escalation policy.
On the one hand, owing to AKU containing all of software version, when software is performing upgrading when,
Corresponding AKU software can be addressed to according to the AKU path of this version software, thus perform AKU
Software program carries out the upgrade actions of software；On the other hand, the escalation policy in configuration file can include as
Lower use-case: 1) from minimum version to highest version；2) from highest version to minimum version；3) randomly draw
Version；4) test case of above three steps is comprised；5) particular version formulated.Each software upgrading is moved
Make to select corresponding test case according to the requirement of test.
Step 3: after software reads corresponding configuration file, according to AKU corresponding in corresponding configuration file
With escalation policy, software is upgraded.First, software can read the AKU of respective version, AKU
Version is with software version one to one, and software is capable of identify that the version coding of AKU such that it is able to
Automatically run AKU script file, perform upgrade actions；Secondly, according to the escalation policy being determined in advance,
Software can read the use-case of escalation policy corresponding in configuration file, and automatically performs use-case therein,
Test case can be one or more, and when there being multiple test case, software will install predetermined use-case
Put in order and carry out one by one, thus the situation avoided test case to obscure or omit.
Step 4: whether software detection completes upgrading.If software discovery still has AKU to be upgraded or does not has
The escalation policy use-case performed, then explanation software does not complete upgrading, then proceed software upgrading.If institute
With AKU and escalation policy use-case be all performed, then explanation software upgrading complete, then enter next step
Suddenly.
Step 5: when software completes upgrading, software can send remote command restarting equipment at hardware layer.The most just
It is to say when software completes upgrading, control command can be sent by software scripts to the central processing unit of equipment, in
After central processor receives the control command of software scripts, make equipment by the level of hardware circuit is changed
Hardware circuit carry out restarting action.
Step 6: after equipment has been restarted, in physical layer, software can send whether remote command detects equipment
Can normally work.Equipment normally works and refers to: the hardware and software in equipment can realize it should be had
Function, lose its relevant function without the change due to software version or the disappearance of function occur.
If equipment can normally work, then enter next step step.If equipment cisco unity malfunction, then software is people
Miscue frame, and generation error daily record is ejected on machine interactive interface.This error log have recorded the liter of software
The failed relevant information of level, including update time, software version, the corresponding error code of staging error, and
Occur in the form of text on human-computer interaction interface, such as display.
Step 7: whether equipment Inspection is so AKU to be upgraded has all been tested.When all of AKU is complete
After becoming upgrading, software should reach desired software version.If there being AKU not complete, then jump to step
Rapid 3, continue to read corresponding configuration file according to step 3, and rise accordingly according in corresponding configuration file
Software is upgraded by level bag and escalation policy, then repeats the step 4 process to step 7.If all liters
Level bag all completes test, and the test of the most whole software compatibility terminates.
It will be understood by those skilled in the art that in above-mentioned embodiment, all or part of step of various methods can
Completing instructing related hardware by program, this program can be stored in a computer-readable recording medium,
Storage medium may include that read only memory, random access memory, disk or CD etc..
The present invention is illustrated by use above specific case, is only intended to help and understands the present invention, not
In order to limit the present invention.For those skilled in the art, according to the thought of the present invention,
Some simple deductions can also be made, deform or replace.
Claims (7)
1. a software compatibility method of testing, it is characterised in that including:
Run upgrading configuration, described upgrading configuration include the path of upgrading configuration and title with
And escalation policy；
According to software in described upgrading configuration updating apparatus；
Described equipment is restarted after upgrading completes；
Whether detection equipment can be properly functioning；
All AKUs in detection escalation policy are the most all upgraded.
2. the method for claim 1, it is characterised in that described escalation policy includes upgrading as follows
Use-case: from minimum version to highest version AKU, take out at random to minimum version AKU from highest version
Take the comprehensive of upgrade edition upgrade pack, particular version AKU and above-mentioned AKU.
3. the method for claim 1, it is characterised in that described escalation policy also includes that each rises
The ordering of level bag.
4. the method for claim 1, it is characterised in that described upgrading configuration is computer
Script file.
5. method as claimed in claim 4, it is characterised in that described computer script file is transported automatically
OK.
6. the method for claim 1, it is characterised in that when equipment is not normally functioning, bullet
Make mistake prompting frame and generation error daily record.
7. the method for claim 1, it is characterised in that when there being AKU to be not fully complete, then
Running upgrading configuration, described upgrading configuration includes the path of upgrading configuration and title and liter
Level strategy；
According to software to be upgraded in described upgrading configuration updating apparatus；
Described equipment is restarted after upgrading completes；
Detection equipment is the most properly functioning；
All AKUs in detection escalation policy are the most all upgraded.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610164884.3A CN105868101B (en) | 2016-03-22 | 2016-03-22 | A kind of method for testing software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610164884.3A CN105868101B (en) | 2016-03-22 | 2016-03-22 | A kind of method for testing software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105868101A true CN105868101A (en) | 2016-08-17 |
| CN105868101B CN105868101B (en) | 2018-11-09 |
Family
ID=56625606
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610164884.3A Active CN105868101B (en) | 2016-03-22 | 2016-03-22 | A kind of method for testing software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105868101B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108415825A (en) * | 2017-10-27 | 2018-08-17 | 平安科技（深圳）有限公司 | electronic device, test method and storage medium |
| CN110703726A (en) * | 2019-09-26 | 2020-01-17 | 上海赫千电子科技有限公司 | Automatic upgrading test method applied to locomotive |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101042651A (en) * | 2006-03-22 | 2007-09-26 | 华为技术有限公司 | Software updating method and system thereof |
| WO2010148742A1 (en) * | 2009-06-23 | 2010-12-29 | 中兴通讯股份有限公司 | Method device and system for on-line upgrading software |
| CN103064715A (en) * | 2013-01-09 | 2013-04-24 | 上海大唐移动通信设备有限公司 | Remote upgrade method and system for automatic drive test systems |
| CN104978271A (en) * | 2015-07-06 | 2015-10-14 | Tcl集团股份有限公司 | Automatic upgrade pressure measurement method and system for Android system |
-
2016
- 2016-03-22 CN CN201610164884.3A patent/CN105868101B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101042651A (en) * | 2006-03-22 | 2007-09-26 | 华为技术有限公司 | Software updating method and system thereof |
| WO2010148742A1 (en) * | 2009-06-23 | 2010-12-29 | 中兴通讯股份有限公司 | Method device and system for on-line upgrading software |
| CN103064715A (en) * | 2013-01-09 | 2013-04-24 | 上海大唐移动通信设备有限公司 | Remote upgrade method and system for automatic drive test systems |
| CN104978271A (en) * | 2015-07-06 | 2015-10-14 | Tcl集团股份有限公司 | Automatic upgrade pressure measurement method and system for Android system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108415825A (en) * | 2017-10-27 | 2018-08-17 | 平安科技（深圳）有限公司 | electronic device, test method and storage medium |
| CN108415825B (en) * | 2017-10-27 | 2021-01-19 | 平安科技（深圳）有限公司 | Electronic device, test method, and storage medium |
| CN110703726A (en) * | 2019-09-26 | 2020-01-17 | 上海赫千电子科技有限公司 | Automatic upgrading test method applied to locomotive |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105868101B (en) | 2018-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102629206B (en) | A kind of method for updating embedded system software and system | |
| CN106445591A (en) | Automatic and batched RAID card FW refreshing method of servers | |
| CN109726107A (en) | Test method, device, equipment and storage medium | |
| CN102117660A (en) | Data storage device tester | |
| CN102637144B (en) | System fault processing method and device | |
| CN102157176A (en) | Data storage device tester | |
| CN110750396B (en) | Server operating system compatibility testing method and device and storage medium | |
| US8055948B2 (en) | Resilient software-controlled redundant array of independent disks (RAID) | |
| CN104834575A (en) | Firmware recovery method and device | |
| CN104978223B (en) | The method for realizing Web mode updating apparatus firmwares | |
| CN104125504B (en) | Deployment method, device and system based on continuous integration | |
| US20160371173A1 (en) | Diagnosis of test failures in software programs | |
| CN102447732A (en) | Method for intelligent configuration of host computer embedded environment during BMC (Baseboard Management Controller) development | |
| US20130139129A1 (en) | Test method for handheld electronic device application | |
| CN105760191A (en) | Embedded system equipment programming mass production method | |
| US20150254169A1 (en) | Method and system for creating reference data | |
| CN106681783A (en) | Detection method and system for SVN code | |
| CN102479121A (en) | Method for realizing and testing redundant array of independent disks (RAID) | |
| CN105868101A (en) | Software testing method | |
| CN105700903A (en) | User terminal upgrading method and user terminal | |
| CN105824649B (en) | Determine driver application installation whether successful method, apparatus and electronic equipment | |
| CN100361075C (en) | Method and device for quickly developing embedded system using automatic compilation frame | |
| CN105094684A (en) | Reuse method and system for problematic disks in disk array system | |
| CN104459515A (en) | Mainboard production testing method | |
| CN105278993B (en) | A kind of drive module upgrade method and device based on linux system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 518000 Guangdong Province, Baoan District, Baoan District, Xin'an Street, Xingdong Community, 68 District, Antongda Industrial Factory Area, 4 factories, 3 floors, 5 office buildings, 1-3 floors Patentee after: Shenzhen dingyang Technology Co., Ltd Address before: Shenzhen City, Guangdong province Baoan District 518000 District 68 road left three Antongda Industrial Park, 4 floor Patentee before: Shenzhen Siglent Technologies Co., Ltd. |
|
| CP03 | Change of name, title or address |