CN108038057A - A kind of embedded software test method - Google Patents

A kind of embedded software test method Download PDF

Info

Publication number
CN108038057A
CN108038057A CN201711381552.1A CN201711381552A CN108038057A CN 108038057 A CN108038057 A CN 108038057A CN 201711381552 A CN201711381552 A CN 201711381552A CN 108038057 A CN108038057 A CN 108038057A
Authority
CN
China
Prior art keywords
embedded software
configuration data
data
test method
simulator
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
Application number
CN201711381552.1A
Other languages
Chinese (zh)
Inventor
周涵
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xuancheng New Maintenance Network Technology Co Ltd
Original Assignee
Xuancheng New Maintenance Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Xuancheng New Maintenance Network Technology Co Ltd filed Critical Xuancheng New Maintenance Network Technology Co Ltd
Priority to CN201711381552.1A priority Critical patent/CN108038057A/en
Publication of CN108038057A publication Critical patent/CN108038057A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/362Software debugging
    • G06F11/3644Software debugging by instrumenting at runtime

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)
  • Debugging And Monitoring (AREA)

Abstract

The present invention provides a kind of embedded software test method, is related to software testing technology field, a kind of embedded software test method, comprises the following steps:S1:The embedded software editted is burnt in memory;S2:Run the embedded software;S3:Using simulator write error configuration data to embedded software, whether observation embedded software continues to run with, if embedded software continues to run with, embedded software is unqualified;Otherwise, step S4 is performed;S4:Write correct configuration data to embedded software using simulator, observation embedded software whether normal operation, if embedded software normal operation, embedded software is qualification;Otherwise embedded software is unqualified.Whether a kind of embedded software test method of the present invention can qualified with Validity Test embedded software, and simple to operation, testing cost is low.

Description

A kind of embedded software test method
Technical field
The present invention relates to software testing technology field,
Especially, the present invention relates to a kind of embedded software test method.
Background technology
With the development of the society, the development of science and technology, diversification product is also with rapid changepl. never-ending changes and improvements, and user also carries embedded product Gone out the requirement of higher, it is desirable to be able to provide complete function, safely, quickly, it is stable, easy to operate the advantages that embedded product, Complete and perfect function must need a set of complete administrative mechanism, and small and special system is referred to as embedded system.
Embedded system relatively common at present has Linux, WinCE, VxWorks, UC/OS, Nucleus, each system There is its advantage and disadvantage, each embedded system is different in the period of and different applications needs and is promoted, due to insertion Formula product is in great demand, and the development to embedded system provides good opportunity.
Due to embedded software have the characteristics that it is soft combination of hardware it is close, in test process often using simulation method Tested, to improve testing adequacy and validity.But simulation test process is usually required according to different tested soft Part establishes substantial amounts of simulation model to support to test, and test process is time-consuming and laborious and tests inefficient.
The content of the invention
It is an object of the invention to overcome the deficiencies of the prior art and provide a kind of simple possible, can be embedded in Validity Test The whether qualified embedded software test method of formula software.
The purpose of the present invention is be achieved through the following technical solutions:
A kind of embedded software test method, comprises the following steps:
S1:The embedded software editted is burnt in memory;
S2:Run the embedded software;
S3:Using simulator write error configuration data to embedded software, whether observation embedded software continues to run with, if Embedded software continues to run with, then embedded software is unqualified;Otherwise, step S4 is performed;
S4:Write correct configuration data to embedded software using simulator, observation embedded software whether normal operation, if Embedded software normal operation, then embedded software is qualification;Otherwise embedded software is unqualified.
Preferably, before performing step S1, data on memory are all wiped.
Preferably, when performing step S2, embedded software running environment is detected.
Preferably, before performing step S3, the configuration data of Edit Error.
Preferably, the configuration data of mistake includes:The configuration data of data length mistake, the configuration number of data encoding mistake According to, the configuration data of data exception, the configuration data of data type mistake and the configuration data that can not be read.
Preferably, step S3 is specially:
S31:Use simulator write error configuration data to embedded software;
S32:Simulator stops write-in data;
S33:Whether observation embedded software continues to run with, if embedded software continues to run with, embedded software is unqualified; Otherwise, step S4 is performed.
Preferably, when performing step S3, step S31 to step S33 is repeated, until the vicious configuration data of institute is equal After testing, embedded software does not continue to run with, then performs step S4.
Preferably, before performing step S31, the error configurations data that simulator is write to embedded software empty.
Preferably, step S4 is specially:
S41:Correct configuration data is write to embedded software using simulator;
S42:Simulator stops write-in data;
S43:Observe embedded software whether normal operation, if embedded software normal operation, embedded software for qualification; Otherwise embedded software is unqualified.
Preferably, measuring the requirement of embedded software qualification is:Simulator write error configuration data, embedded software is not It is further continued for running;And simulator writes correct configuration data, embedded software normal operation.
A kind of embedded software test method beneficial effect of the present invention is:Whether can be closed with Validity Test embedded software Lattice, simple to operation, testing cost is low.
Brief description of the drawings
Fig. 1 is the flow diagram of one embodiment of the invention.
Embodiment
It is the specific embodiment of the present invention below, technical scheme is further described, but the present invention is simultaneously It is not limited to these embodiments.
Carry out the various exemplary embodiments of detailed description of the present invention now with reference to attached drawing.It should be noted that:Unless in addition have Body illustrates that the module and the positioned opposite and step of step otherwise illustrated in these embodiments does not limit the scope of the invention.
At the same time, it should be appreciated that for the ease of description, the flow in attached drawing is not merely individually to carry out, but multiple steps The rapid progress that intersects.
Due to embedded software have the characteristics that it is soft combination of hardware it is close, in test process often using simulation method carry out Test, to improve testing adequacy and validity.But simulation test process usually requires to be built according to different tested softwares Substantial amounts of simulation model is found to support to test, in existing test method, test process is time-consuming and laborious and tests inefficient.
Embodiment one:
As shown in Figure 1, it is only one of embodiment of the present invention, in order to more convenient more simply to test embedded software Qualification is tested, and the present invention proposes a kind of embedded software test method, comprises the following steps:
S1:The embedded software editted is burnt in memory;
Substantial amounts of simulation model need not be established to support to test, by embedded software direct burning into memory, you can effectively Embedded software is read out and is tested.
Certainly, before step S1 is performed, data on memory is all wiped, prevent other data to embedded software The test of part impacts.
S2:Run the embedded software;
Trial operation embedded software, it is complete to show embedded software, and the performance for also demonstrating that memory is the available of qualification, It can use what the memory was tested for the embedded software, certainly, if during trial operation, embedded software can not be transported Row is, it is necessary to replace memory, if repeatedly replacement may not operate, it is underproof that can directly prove embedded software.
The step for just for the sake of detection embedded software running environment.
S3:Using simulator write error configuration data to embedded software, whether observation embedded software continues to run with, If embedded software continues to run with, embedded software is unqualified;Otherwise, step S4 is performed;
It is more multiple in progress even if embedded software can not represent embedded software as certified products with normal operation yet under trial operation During miscellaneous operation, it would still be possible to failure occurs.
Embedded software has the ability of processing data, then the configuration data of one end mistake is write using simulator, is allowed Embedded software is handled, simulate its wrong resolution capability and operation whether specification, if being written with the configuration data of mistake, Embedded software remains to run, and illustrates that its wrong resolution capability is low, or its traffic direction is incorrect, can be shown that embedded Software is underproof.
Conversely, embedded software cannot handle the configuration data of mistake, then it is probably qualification to illustrate embedded software, into The test of row next step, performs step S4.
Certainly, before step S3 is performed, the configuration data of Edit Error.Edit the configuration data of a few class mistakes more, survey Test result is more accurate.
S4:Write correct configuration data to embedded software using simulator, observation embedded software whether normal operation, If embedded software normal operation, embedded software is qualification;Otherwise embedded software is unqualified.
In step s3, even if embedded software can differentiate the configuration data of mistake, embedded software is not also represented One is set to qualification, need to further be simulated.
Correct configuration data is write using simulator, if embedded software cannot be handled, or is not normally functioning Draw correct output parameter, then illustrate the incorrect accurately data-handling capacity of embedded software, be still unqualified 's.
Conversely, embedded software can run and can normally handle correct configuration data draw correctly output as a result, Then illustrate embedded software for qualification.
Generally speaking:Test show that the requirement of embedded software qualification is:It is embedding when simulator write error configuration data Enter formula software not continuing to run;And when simulator writes correct configuration data, embedded software normal operation, and can be normal Processing draws correctly output result.
Embodiment two:
A kind of above-mentioned embedded software test method can conveniently test whether a kind of embedded software is qualified Product, but test result be not once test can draw, it is necessary to carry out multiple test.
Also mention above, in the configuration data of Edit Error, edit the configuration data of a few class mistakes, test result more It is more accurate.
Can rule of thumb have, the configuration data of mistake includes:Configuration data, the data encoding mistake of data length mistake Configuration data, the configuration data of data exception, the configuration data of data type mistake and the configuration data that can not be read.
On this basis, step S3 is specially:
S31:Use simulator write error configuration data to embedded software;
S32:Simulator stops write-in data;
S33:Whether observation embedded software continues to run with, if embedded software continues to run with, embedded software is unqualified; Otherwise, step S4 is performed.
And when performing step S3, step S31 to step S33 is repeated, until the vicious configuration data of institute is equal After testing, embedded software does not continue to run with, then performs step S4.
Test must namely be repeated, after all wrong data all test once, if embedded software Part is not run, then illustrates that processing of the embedded software for wrong data with discrimination is normal, can just carry out down like that Face is further tested.
Above as can be seen that after write-in data, it is necessary to first stop write-in, represent that data write activity is completed, Yi Mianhou The data influence test result of continuous input.
But importantly, before performing step S31, simulator is write to the error configurations data of embedded software Empty.
Accomplish the rigorous accurate of test, be that the error configurations data of write-in cause shadow to test result below before avoiding Ring.
The test of embedded software also has a step, carries out step S4, and step S4 is specially:
S41:Correct configuration data is write to embedded software using simulator;
S42:Simulator stops write-in data;
S43:Observe embedded software whether normal operation, if embedded software normal operation, embedded software for qualification; Otherwise embedded software is unqualified.
Certainly, then before carrying out step S41, it is also desirable to the configuration data that will be write before using simulator is all removed, Avoid disturbing.
Subsequently, the correct configuration data of input is complicated as far as possible or representative, and such aptitude test goes out Embedded software data-handling capacity, if in the case of configuration data is complicated as far as possible or representative, embedded software Part remains to normal operation and can normally handle show that correctly output is as a result, it is qualified that can then measure embedded software.
Whether a kind of embedded software test method of the present invention can qualified with Validity Test embedded software, simple easily behaviour Make, testing cost is low.
The present invention is not limited to above-mentioned specific embodiment, and the invention may be variously modified and varied.Every foundation The technical spirit of the present invention should be included in the present invention to embodiment of above any modification, equivalent replacement, improvement and so on Protection domain.

Claims (10)

  1. A kind of 1. embedded software test method, it is characterised in that comprise the following steps:
    S1:The embedded software editted is burnt in memory;
    S2:Run the embedded software;
    S3:Using simulator write error configuration data to embedded software, whether observation embedded software continues to run with, if Embedded software continues to run with, then embedded software is unqualified;Otherwise, step S4 is performed;
    S4:Write correct configuration data to embedded software using simulator, observation embedded software whether normal operation, if Embedded software normal operation, then embedded software is qualification;Otherwise embedded software is unqualified.
  2. A kind of 2. embedded software test method according to claim 1, it is characterised in that:, will before performing step S1 Data are all wiped on memory.
  3. A kind of 3. embedded software test method according to claim 1, it is characterised in that:When performing step S2, detection Embedded software running environment.
  4. A kind of 4. embedded software test method according to claim 1, it is characterised in that:Before performing step S3, compile Collect the configuration data of mistake.
  5. A kind of 5. embedded software test method according to claim 1, it is characterised in that the configuration data bag of mistake Include:The configuration data of data length mistake, the configuration data of data encoding mistake, configuration data, the data type of data exception The configuration data of mistake and the configuration data that can not be read.
  6. 6. a kind of embedded software test method according to claim 5, it is characterised in that step S3 is specially:
    S31:Use simulator write error configuration data to embedded software;
    S32:Simulator stops write-in data;
    S33:Whether observation embedded software continues to run with, if embedded software continues to run with, embedded software is unqualified; Otherwise, step S4 is performed.
  7. A kind of 7. embedded software test method according to claim 6, it is characterised in that:When performing step S3, repeat Step S31 to step S33 is performed, until after the vicious configuration data of institute is tested, embedded software is not after reforwarding OK, then step S4 is performed.
  8. A kind of 8. embedded software test method according to claim 7, it is characterised in that:, will before performing step S31 Simulator writes to the error configurations data of embedded software and empties.
  9. 9. a kind of embedded software test method according to claim 1, it is characterised in that step S4 is specially:
    S41:Correct configuration data is write to embedded software using simulator;
    S42:Simulator stops write-in data;
    S43:Observe embedded software whether normal operation, if embedded software normal operation, embedded software for qualification; Otherwise embedded software is unqualified.
  10. 10. a kind of embedded software test method according to claim 1, it is characterised in that measure embedded software conjunction The requirement of lattice is:Simulator write error configuration data, embedded software do not continue to run;And the correct configuration of simulator write-in Data, embedded software normal operation.
CN201711381552.1A 2017-12-20 2017-12-20 A kind of embedded software test method Pending CN108038057A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711381552.1A CN108038057A (en) 2017-12-20 2017-12-20 A kind of embedded software test method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711381552.1A CN108038057A (en) 2017-12-20 2017-12-20 A kind of embedded software test method

Publications (1)

Publication Number Publication Date
CN108038057A true CN108038057A (en) 2018-05-15

Family

ID=62099939

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711381552.1A Pending CN108038057A (en) 2017-12-20 2017-12-20 A kind of embedded software test method

Country Status (1)

Country Link
CN (1) CN108038057A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11270777B2 (en) 2019-04-30 2022-03-08 Yangtze Memory Technologies Co., Ltd. Memory system capable of reducing the reading time

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160070637A1 (en) * 2014-09-04 2016-03-10 Home Box Office, Inc. Documents for human readable documentation and runtime validation
CN105718375A (en) * 2016-01-27 2016-06-29 惠州市德赛西威汽车电子股份有限公司 Restorability testing method of embedded system
CN107357696A (en) * 2017-06-22 2017-11-17 上海斐讯数据通信技术有限公司 A kind of bad block method of testing of nonvolatile storage and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160070637A1 (en) * 2014-09-04 2016-03-10 Home Box Office, Inc. Documents for human readable documentation and runtime validation
CN105718375A (en) * 2016-01-27 2016-06-29 惠州市德赛西威汽车电子股份有限公司 Restorability testing method of embedded system
CN107357696A (en) * 2017-06-22 2017-11-17 上海斐讯数据通信技术有限公司 A kind of bad block method of testing of nonvolatile storage and system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11270777B2 (en) 2019-04-30 2022-03-08 Yangtze Memory Technologies Co., Ltd. Memory system capable of reducing the reading time
US11670384B2 (en) 2019-04-30 2023-06-06 Yangtze Memory Technologies Co., Ltd. Memory system capable of reducing the reading time

Similar Documents

Publication Publication Date Title
CN102169846B (en) Method for writing multi-dimensional variable password in parallel in process of testing integrated circuit wafer
CN101692351B (en) Method and device for testing memory
US7246333B2 (en) Apparatus and method for unified debug for simulation
TW201216048A (en) Test system
CN102495926B (en) Test method and device of three-dimensional original model
WO2021109367A1 (en) Simulation signal viewing method for digital product, and system
US20200074040A1 (en) Hierarchical expression coverage clustering for design verification
CN114548031A (en) Signal detection method and device
CN108122596A (en) The test method and device of a kind of memory
CN111680463A (en) File checking method and device
CN105183641A (en) Data consistency check method and system for kernel module
CN108038057A (en) A kind of embedded software test method
CN110347595A (en) A kind of FPGA internal resource is screened and localization method and system
CN108985379A (en) Performance estimating method, device and the computer readable storage medium of classifier
CN109726063A (en) A kind of automation evaluation method of behavior based on instruction to the Verilog MIPS processor realized
CN106892134B (en) Virtual instrument testing method and device
CN109582513A (en) A kind of JBOD test method and system based on generic server
WO2021109365A1 (en) Simulation signal viewing method and system for digital product
CN107679266A (en) The emulation mode and simulator of flash memory circuit
WO2021109366A1 (en) Method and system for viewing simulation signals of digital product
Hillston Performance Modelling—Lecture 16: Model Validation and Verification
CN112613185A (en) Modeling method for noise of composite current source
CN105955879A (en) Method and device for testing two-dimensional code generation algorithm
CN109918256A (en) A kind of register testing method and system
US10060976B1 (en) Method and apparatus for automatic diagnosis of mis-compares

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
RJ01 Rejection of invention patent application after publication

Application publication date: 20180515