CN103064787A - Embedded assembly modeling and testing method based on expansion interface automata model - Google Patents
Embedded assembly modeling and testing method based on expansion interface automata model Download PDFInfo
- Publication number
- CN103064787A CN103064787A CN201210564499XA CN201210564499A CN103064787A CN 103064787 A CN103064787 A CN 103064787A CN 201210564499X A CN201210564499X A CN 201210564499XA CN 201210564499 A CN201210564499 A CN 201210564499A CN 103064787 A CN103064787 A CN 103064787A
- Authority
- CN
- China
- Prior art keywords
- state
- test
- interface
- testing
- case
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 119
- 238000000034 method Methods 0.000 claims description 36
- 230000007704 transition Effects 0.000 claims description 16
- 238000012546 transfer Methods 0.000 claims description 11
- 238000010586 diagram Methods 0.000 claims description 4
- 230000005856 abnormality Effects 0.000 claims description 3
- 230000000454 anti-cipatory effect Effects 0.000 claims description 3
- 238000011990 functional testing Methods 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 abstract description 9
- 238000013522 software testing Methods 0.000 abstract description 2
- 230000006399 behavior Effects 0.000 abstract 1
- 238000011161 development Methods 0.000 description 5
- 230000018109 developmental process Effects 0.000 description 5
- 238000013459 approach Methods 0.000 description 2
- 235000000332 black box Nutrition 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000010998 test method Methods 0.000 description 2
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 230000003542 behavioural effect Effects 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 230000002068 genetic effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000000275 quality assurance Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000000452 restraining effect Effects 0.000 description 1
- 238000002922 simulated annealing Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
An embedded assembly modeling and testing method based on an expansion interface automata model relates to the field of software testing and testing automation based on a model and is applicable to testing of an embedded assembly. The embedded assembly modeling and testing method is characterized in that the automata model with constraint conditions is used for description aiming at assembly interface operation, data and behaviors, and a testing case set is generated on the basis of the graph searching and constraint solving technology. The embedded assembly modeling and testing method includes: (1) constructing the expansion interface automata model of the embedded assembly and (2) defining a testing coverage rate goal on the basis of the automata model and generating a normal function testing case and a robustness testing case which achieve the testing coverage rate goal.
Description
Technical field:
The present invention relates to computer software fields, particularly the model-based testing automatic field.
Background technology:
Embedded system has been widely used in the every field such as Aeronautics and Astronautics, electronics, machinery.For the development trend that the embedded software scale increases substantially, the construction cycle shortens, quality requirements promotes, in recent years, the development approach of built-in module has been proposed, by the decomposition of function, the encapsulation of component interface, the reuse technology of standard package, improve development efficiency and quality, reduce cost, improve the maintainability of system.
Built-in module is the elementary cell that consists of embedded system, is the base unit of System Construction, exploitation, assembling, checking, assessment and maintenance, and the credibility of assembly is the basis of system credibility.Assembly is the module of stand-alone development, usually adopts the supplying method of black box, has hidden data and implementation method, and inner realization is invisible to the user; External characteristic and behavior with good definition, usually abideing by interface specification externally provides service; Can be integrated by specific mode, interface protocol and other assemblies and the system by standard carries out mutual and cooperates.In embedded system, usually adopt the assembly of software and hardware one, comprise hardware, operating system software and application software.Generally include the parts such as signal processing, network control software such as Intelligent Sensorsystem, by stable standardized communications network interface, provide output signal.Built-in module is being built in the process of complication system, usually need to carrying out in detail time domain and the codomain of CNI interface, precise definition.In new integrated environment, confirm the robustness of precondition to guarantee to operate of assembly, and assembly is fully tested.This accurate interface specification is the foundation of module testing and affirmation.
U.S. University of California, the Luca de Alfaro of Berkeley and Thomas A. Henzinger have proposed a kind of embedded software component interface model of lightweight in calendar year 2001: Interface Automata model (Interface Automata, IA).IA state-based machine model can be described for the combination behavior of component interface, assembly behavior and inter-module, and supports composability and consistency checks between the different component interface models.
In the basic Interface Automata, lack the description to constraint and dependence between the component interface, such as input between two interface operations, export the dependence between the data, and interface operation preposition/postcondition constraint etc.The present invention has expanded the Interface Automata model, introduces interface parameters definition and constraint definition, for description, understanding and analytic unit provide abundanter behavior semantic information, and provides the Test Auto-generation method of the Interface Automata model of extension-based.The present invention is for comprising two parts: the Interface Automata definition of (1) expansion; (2) the test generation method of the Interface Automata model of extension-based.
Test is the important method of built-in module quality assurance, the Interface Automata model of expansion can be assisted the built-in module analysis and understanding, the model-based testing automatic technology can improve efficient and the quality of built-in module test, and is significant to the development approach research of embedded system component-based.
Summary of the invention
The present invention adopts the software testing technology based on model, based on the automaton theory of belt restraining, provides a kind of modeling method of interface operation, data and behavior of built-in module; Based on graph search and constraint theory of solving, provide a kind of model-based testing automatic generation method.Method requires embedded system to meet the following conditions for the embedded system of present widespread use: (1) adopts the embedded system development method of component-based; (1) has clear and definite built-in module interface definition.
The inventive method is carried out modeling and test for built-in module E according to following steps:
Step (1) system initialization
Input: the interface definition of built-in module, comprising: the input/output parameters of interface operation, operation, operation preposition/the anticipatory behavior information of postcondition and assembly.
Step (2) is set up the expansion interface automaton model on the built-in module according to the following steps:
Step (2.1) makes up state set S
E, and definition original state set wherein
, and
Step (2.2) makes up interface operation data and variables collection V
E, and
, wherein,
,
,
Expression is inputted data, is exported data and include the overall situation and the internal data of local variable respectively.
Step (2.3) makes up the interface operation set A
E, and
, wherein,
,
,
Represent respectively input behavior, output behavior and middle behavior, for any interface behavior a ∈ A
E, with a (v) expression interface operation and parameter thereof, v ∈ V
E
Step (2.4) makes up the constrain set C corresponding to the precondition/postcondition of each state
E, precondition adopts logical expression to describe with preCond, postcondition postCond statement, every constraint, is used for judging boolean's value.
Step (2.5) makes up the set τ=S of state transitions relation
E* A
E* S
E, the τ that concerns of any one state transitions is had:
If expression assembly E satisfies precondition preCond, by state s
1Can by operation a (v), transfer to state s
2, and satisfy postcondition postCond, finish again corresponding renewal update and process.
Step (3) is according to the result of step (2), according to the following steps generating test use case:
Step (3.1) defines the test coverage target of expansion interface automaton model with the abundant degree of quantitative measurement software test case set, the coverage rate definition of adopting state-based to shift, and the coverage criterion of testing with total state represents.
Step (3.2) adopts the algorithm of graph search, generates according to the following steps the abstract test use-case set T of above-mentioned test coverage target
E={ tc
i}:
Each test case definition is a group interface sequence of operation, tc
i=＜a
I, 1, a
I, 2..., a
I, k.. 〉, i is the sequence number of test case, the sequence number of each operation of k, k=1,2 ..., k ... K, K is the operation number;
For each the operation a in the described test case
I, k∈ A
E, have two state: s
I, k∈ S
EAnd s
I, k+1∈ S
E, s
I, kFor being the test case tc of i in sequence number
iK operation a
I, kFront system state, s
I, k+1For being the test case tc of i in sequence number
iK operation a
I, kAfter system state, namely satisfy transfer relationship (s
I, k, a
I, k, s
I, k+1);
For any one the continuous operation subsequence＜a in the test case
I, 1, a
I, 2..., a
I, m..., a
I, M, there is one group of state transitions set { (s
I, 1, a
I, 1, s
I, 2), (s
I, 2, a
I, 2, s
I, 3) ... .., (s
I, m, a
I, m, s
I, m+1) ... .., (s
I, M-1, a
I, M, s
I, M), then correspond to the paths that the expansion interface state of automata shifts usefulness, the sequence number that m changes for operation, m=1,2 ..., m ... M, M are the numbers that operates in this sequence.
Step (3.3) makes up each paths in the described state transition diagram from original state, make up one and satisfy the abstract test use-case set that total state covers.
Step (3.4) is extracted the set of the constraint expression formula on all state transitions on this path to resulting each paths of step (3.2), obtains the data set of following two class testing-cases:
For the data that satisfy constraint condition, add described test case set to, consist of the set of functional test use-case;
For the data that do not satisfy constraint condition, add described abstract test use-case set to, consist of abnormality test and be also referred to as the set of robustness test case.
Two class testing-cases that produce in step (4) the root step (3.4) are integrated in the tested system to be carried out, to detect the correctness of tested built-in module interface function.
The method is a kind of Black-box Testing method of component interface test, with the method for testing effective supplement based on code, emphatically from user perspective, detecting built-in module externally provides the correctness of function, can be used for assembly module test and integration testing, is the system detection method that is based upon on the component internal unit testing.The integrating process that is particularly useful for the extensive embedded system of component-based assembling mode exploitation.
Description of drawings
Fig. 1 illustrates primary structure and the step of the inventive method;
Fig. 2 illustrates primary structure and the step of expansion interface automat modeling in the inventive method;
Fig. 3 illustrates primary structure and the step that test case generates in the inventive method;
Fig. 4 illustrates the key step in the inventive method;
Fig. 5 provides an example of the inventive method.
Embodiment
As shown in Figure 1, the present invention is mainly for the Interface Automata model of built-in module foundation with data and constraint, search element and constraint solution technique by state machine diagram, according to the set of model generation interface testing use-case, comprise the normal function test of legal input and the robustness test of unusual input.Described method takes following steps to carry out:
Step (1) initialization
Built-in module is the elementary cell that consists of embedded system, is the relatively complete software module of function, has clear and definite function and communication interface.Initialization procedure obtains the interface definition of built-in module, comprises the input/output parameters of interface operation, operation, the pre-post condition of operation, the information such as anticipatory behavior of assembly.
Step (2) is set up the expansion interface automaton model
As shown in Figure 2, need to make up from the following aspects the expansion interface automaton model of built-in module E:
Step (2.1) makes up state set.In the example, comprise original state as shown in Figure 5, and A, B, C, D one of four states.
Step (2.2) makes up data acquisition.In the example, the identification parameter data comprise input data v as shown in Figure 5
1And v
2, and output data v
3And v
4
Step (2.3) makes up the interface operation set.In the example, comprise two input operation Op as shown in Figure 5
1And Op
2, and two output functions! Op
3With! Op
4Each operation is respectively with input and output parameter, i.e. Op
1(v
1), Op
2(v
2), Op
3(v
3) and Op
4(v
4).
Step (2.4) constrain set.As shown in Figure 5 in the example, the precondition preCond of state B and postcondition postCond.
Step (2.5) makes up the state transitions relation.In the example, there are transfer relationship init → A, init → C, A → B, A → C, C → D and B → D as shown in Figure 5.Further identify operation, data and the constraint condition of transfer relationship, as
Step (3) extension-based Interface Automata model, generating test use case
As shown in Figure 3, the step of generating test use case is as follows:
The test coverage target of step (3.1) definition expansion interface automaton model.
The abundant degree of coverage rate quantitative measurement software test collection.Traditional coverage rate mainly contains coverage rate index and the need-based based on code.Assessment is applicable in the white-box testing based on the adequacy of code, and the implementation status in the statement by observation program in test process, branch, path etc. is assessed the abundant degree of Test coverage.Adequacy assessment based on function is usually used in the Black-box Testing, with the level of coverage of assessment software systems for functional requirement.
Adopt the coverage rate standard based on model in this method, the model coverage criterion is for the characterizing definition of meta-model, and for assessment of one group of rule of the abundant degree of covering of test case set pair model, it can be applied to any example based on meta-model.The model coverage criterion is applied to specific test model, can obtain one group of this model about model element (state, transfer, event etc.) or the test result of model element combination.The typical Test coverage criterion that state machine model uses is as follows:
● total state covers (All-States): test use cases covers each state of state machine.
● total transfer covers (All-Transitions): test use cases covers every kind of state transitions of state machine.
● total event covers (All-Events): test use cases covers the trigger event of each state transitions.
● the n degree of depth covers (Depth-n): from original state, to being not more than arbitrarily the running process of length n, exist at least a test case to comprise sequence take this running process as subset.
● all n degree of depth shift and cover (All-n-Transitions): from any one state s, for each running process that is no more than length n, have at least a test case to comprise sequence take this running process as subset.All 0 degree of depth shift and cover namely is that total state covers.
● complete trails covers (All-Paths): test use cases covers all possible state transitions sequence in the state machine.
Step (3.2) is according to the test coverage target, the path of search condition transition diagram.
This can be converted into typical search problem, and searching algorithm commonly used comprises hill-climbing algorithm, simulated annealing, genetic algorithm and ant group algorithm etc.Can adopt the graph search technology in this method, according to the test coverage target, the objective function of optimization is searched in definition, obtains to satisfy the set of paths of coverage rate target by search procedure.For example, for satisfying the total transfer coverage criteria, can obtain following set of paths:
<(init,?Op
2,A),(A,?Op
1,B),(B,!Op
4,D)>
<(init,?Op
2,A),(A,?Op
2,B),(B,!Op
3,D)>
<(init,?Op
1,C),(C,?Op
3,D)>
Step (3.3) makes up the set of abstract test use-case.
Can correspond to a test case by resulting each paths in the step (3.2), be consisted of by the sequence of operation.For example, the test use cases corresponding with the set of paths that satisfies power transfer covering is combined into:
<?Op
2,?Op
1,!Op
4>
<?Op
2,?Op
2,!Op
3>
<?Op
1,!Op
3>
Step (3.4) constraint solving test data.
As shown in Figure 3, for resulting each path in the step (2), extract the set of the constraint expression formula on all state transitions on this path, by the constraint solving technology, obtain the data set of test case.Test case can be divided into two classes: satisfy the normal function test of constraint condition, and the abnormality test (also becoming the robustness test) of running counter to constraint condition.
For example, suppose that transfer constraint condition is as follows in Fig. 5 example:
Then for path＜(init, Op
2, A), (A, Op
1, B), (B,! Op
4, D)〉test case＜Op
2, Op
1,! Op
4, its input data need satisfy following constraint condition:
Adopt Boundary value method design test data, then produce one group and satisfy constraint test data and test case, for example:
{ v
1=201, v
2=0 }, i.e. test case＜Op
2(0),〉Op
1(201),! Op
4(v
4)
{ v
1=400, v
2=0 }, i.e. test case＜Op
2(0),〉Op
1(400),! Op
4(v
4)
{ v
1=0, v
2=400 }, i.e. test case＜Op
2(400),〉Op
1(0),! Op
4(v
4)
{ v
1=0, v
2=201 }, i.e. test case＜Op
2(201),〉Op
1(0),! Op
4(v
4)
And can produce one group of robustness test data and test case that does not satisfy constraint, for example:
{ v
1=200, v
2=0 }, i.e. test case＜Op
2(0),〉Op
1(200),! Op
4(v
4)
{ v
1=401, v
2=0 }, i.e. test case＜Op
2(0),〉Op
1(401),! Op
4(v
4)
{ v
1=0, v
2=101 }, i.e. test case＜Op
2(401),〉Op
1(0),! Op
4(v
4)
{ v
1=0, v
2=200 }, i.e. test case＜Op
2(200),〉Op
1(0),! Op
4(v
4)
Step (4) is carried out test
The test case that produces in the step (3) is carried out at system under test (SUT), to detect the correctness of tested built-in module interface function.
Above embodiment only is used for explanation the present invention, but not limitation of the present invention.The those of ordinary skill of correlative technology field in the situation that do not break away from the spirit and scope of the present invention, can also make a variety of changes and be out of shape.Therefore, all technical schemes that are equal to also belong to category of the present invention, and scope of patent protection of the present invention should be defined by the claims.
The present invention is directed to the formalized description method of the operational semantics of interface, the accurately interface operation of built-in module, data and behavioural characteristic are for understanding and the test suite functional characteristic provides support.Still lack at present method of testing and technology for component-level in the traditional test, the present invention is on the basis of expansion interface automaton model, but back-up system ground, robotization ground, generating test use case intelligently improve efficient and the validity of built-in module test.Efficient refers to by automatic test, compares with manually designing and developing test case, can reduce the test duration, reduces test originally; Validity refers to, by strictly constraint definition and constraint solution technique generate test data, the Flaw detectability (being the ratio of number of defects/test case number) of raising test case.
Claims (1)
1. built-in module modeling and the method for testing of an extension-based Interface Automata model is characterized in that, are in a computing machine, realize according to the following steps successively:
Step (1) system initialization
Input: the interface definition of built-in module, comprising: the input/output parameters of interface operation, operation, operation preposition/the anticipatory behavior information of postcondition and assembly,
Step (2) is set up the expansion interface automaton model on the built-in module according to the following steps:
Step (2.1) makes up state set S
E, and definition original state set wherein
, and
,
Step (2.2) makes up interface operation data and variables collection V
E, and
, wherein,
,
,
Expression is inputted data, is exported data and include the overall situation and the internal data of local variable respectively,
Step (2.3) makes up the interface operation set A
E, and
, wherein,
,
,
Represent respectively input behavior, output behavior and middle behavior, for any interface behavior a ∈ A
E, with a (v) expression interface operation and parameter thereof, v ∈ V
E,
Step (2.4) makes up the constrain set C corresponding to the precondition/postcondition of each state
E, precondition adopts logical expression to describe with preCond, postcondition postCond statement, every constraint, is used for judging boolean's value,
Step (2.5) makes up the set τ=S of state transitions relation
E* A
E* S
E, the τ that concerns of any one state transitions is had:
If expression assembly E satisfies precondition preCond, by state s
1Can by operation a (v), transfer to state s
2, and satisfy postcondition postCond, finish again corresponding renewal update and process,
Step (3) is according to the result of step (2), according to the following steps generating test use case:
The test coverage target of step (3.1) definition expansion interface automaton model is with the abundant degree of quantitative measurement software test case set, and the coverage rate definition of adopting state-based to shift represents with the coverage criterion of total state test,
Step (3.2) adopts the algorithm of graph search, generates according to the following steps the abstract test use-case set TE={tc of above-mentioned test coverage target
i}:
Each test case definition is a group interface sequence of operation, tc
i=＜a
I, 1, a
I, 2..., a
I, k..., i is the sequence number of test case, the sequence number of each operation of k, and k=1,2 ..., k ... K, K is the operation number,
For each the operation a in the described test case
I, k∈ A
E, have two state: s
I, k∈ S
EAnd s
I, k+1∈ S
E, s
I, kFor being the test case tc of i in sequence number
iK operation a
I, kFront system state, s
I, k+1For being the test case tc of i in sequence number
iK operation a
I, kAfter system state, namely satisfy transfer relationship (s
I, k, a
I, k, s
I, k+1),
For any one the continuous operation subsequence＜a in the test case
I, 1, a
I, 2..., a
I, m..., a
I, M, there is one group of state transitions set { (s
I, 1, a
I, 1, s
I, 2), (s
I, 2, a
I, 2, s
I, 3) ... .., (s
I, m, a
I, m, s
I, m+1) ... .., (s
I, M-1, a
I, M, s
I, M), then correspond to the paths that the expansion interface state of automata shifts usefulness, the sequence number that m changes for operation, m=1,2 ..., m ... M, M are the numbers that operates in this sequence,
Step (3.3) makes up each paths in the described state transition diagram from original state, and make up one and satisfy the abstract test use-case set that total state covers,
Step (3.4) is extracted the set of the constraint expression formula on all state transitions on this path to resulting each paths of step (3.2), obtains the data set of following two class testing-cases:
For the data that satisfy constraint condition, add described test case set to, consist of the set of functional test use-case;
For the data that do not satisfy constraint condition, add described abstract test use-case set to, consist of abnormality test and be also referred to as the set of robustness test case,
Two class testing-cases that produce in step (4) the root step (3.4) are integrated in the tested system to be carried out, to detect the correctness of tested built-in module interface function.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210564499.XA CN103064787B (en) | 2012-12-21 | 2012-12-21 | Embedded assembly modeling and testing method based on expansion interface automata model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210564499.XA CN103064787B (en) | 2012-12-21 | 2012-12-21 | Embedded assembly modeling and testing method based on expansion interface automata model |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103064787A true CN103064787A (en) | 2013-04-24 |
| CN103064787B CN103064787B (en) | 2015-06-10 |
Family
ID=48107420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210564499.XA Active CN103064787B (en) | 2012-12-21 | 2012-12-21 | Embedded assembly modeling and testing method based on expansion interface automata model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103064787B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104714829A (en) * | 2013-12-15 | 2015-06-17 | 中国航空工业集团公司第六三一研究所 | Compiling linkage method for ensuring consistency of object code and source code |
| CN104899136A (en) * | 2015-05-15 | 2015-09-09 | 百度在线网络技术（北京）有限公司 | Method and device used for generating test case |
| WO2016004657A1 (en) * | 2014-07-11 | 2016-01-14 | 电子科技大学 | Device for automatically generating test cases for embedded software and method thereof |
| CN107066382A (en) * | 2017-03-09 | 2017-08-18 | 北京航空航天大学 | A kind of Space Vehicle System automated testing method based on model |
| CN107729010A (en) * | 2017-10-25 | 2018-02-23 | 广州优视网络科技有限公司 | View display methods, device, computing device and storage medium |
| CN108139893A (en) * | 2015-07-16 | 2018-06-08 | 容毅 | Software systems and development approach based on component |
| CN112463578A (en) * | 2019-09-09 | 2021-03-09 | 南华大学 | System test case generation method based on step-by-step solution of component contract |
| CN114385475A (en) * | 2020-10-16 | 2022-04-22 | 腾讯科技（深圳）有限公司 | Test method and related device |
| CN117173431A (en) * | 2023-07-26 | 2023-12-05 | 清华大学 | Visual intelligent detection robustness enhancement method and system based on state machine |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101833498A (en) * | 2009-07-31 | 2010-09-15 | 北京伟晨豪嘉科技有限责任公司 | Automatic detection system of embedded type system based on testing script technique |
-
2012
- 2012-12-21 CN CN201210564499.XA patent/CN103064787B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101833498A (en) * | 2009-07-31 | 2010-09-15 | 北京伟晨豪嘉科技有限责任公司 | Automatic detection system of embedded type system based on testing script technique |
Non-Patent Citations (1)
| Title |
|---|
| 白晓颖等: "Interface-Based Automated Testing for Open Software Architecture", 《COMPUTER SOFTWARE AND APPLICATIONS CONFERENCE WORKSHOPS (COMPSACW), 2011 IEEE 35TH ANNUAL》 * |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104714829A (en) * | 2013-12-15 | 2015-06-17 | 中国航空工业集团公司第六三一研究所 | Compiling linkage method for ensuring consistency of object code and source code |
| CN104714829B (en) * | 2013-12-15 | 2017-11-28 | 中国航空工业集团公司第六三一研究所 | A kind of compiling link method for ensureing object code and source code consistency |
| WO2016004657A1 (en) * | 2014-07-11 | 2016-01-14 | 电子科技大学 | Device for automatically generating test cases for embedded software and method thereof |
| CN104899136A (en) * | 2015-05-15 | 2015-09-09 | 百度在线网络技术（北京）有限公司 | Method and device used for generating test case |
| CN108139893A (en) * | 2015-07-16 | 2018-06-08 | 容毅 | Software systems and development approach based on component |
| CN108139893B (en) * | 2015-07-16 | 2021-08-06 | 山东程序元软件有限公司 | Software system based on component and development method |
| CN107066382A (en) * | 2017-03-09 | 2017-08-18 | 北京航空航天大学 | A kind of Space Vehicle System automated testing method based on model |
| CN107729010A (en) * | 2017-10-25 | 2018-02-23 | 广州优视网络科技有限公司 | View display methods, device, computing device and storage medium |
| CN112463578A (en) * | 2019-09-09 | 2021-03-09 | 南华大学 | System test case generation method based on step-by-step solution of component contract |
| CN112463578B (en) * | 2019-09-09 | 2022-04-22 | 南华大学 | System test case generation method based on step-by-step solution of component contract |
| CN114385475A (en) * | 2020-10-16 | 2022-04-22 | 腾讯科技（深圳）有限公司 | Test method and related device |
| CN114385475B (en) * | 2020-10-16 | 2024-08-06 | 腾讯科技（深圳）有限公司 | Test method and related device |
| CN117173431A (en) * | 2023-07-26 | 2023-12-05 | 清华大学 | Visual intelligent detection robustness enhancement method and system based on state machine |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103064787B (en) | 2015-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103064787A (en) | Embedded assembly modeling and testing method based on expansion interface automata model | |
| Barr et al. | The oracle problem in software testing: A survey | |
| CN107025170A (en) | For the system and method for the test case augmentation of the automation based on covering designed a model | |
| Elkholy et al. | Model checking intelligent avionics systems for test cases generation using multi-agent systems | |
| Filipovikj et al. | Integrating pattern-based formal requirements specification in an industrial tool-chain | |
| Bernaerts et al. | Validating industrial requirements with a contract-based approach | |
| Mian et al. | Model transformation for analyzing dependability of AADL model by using HiP-HOPS | |
| Dressler et al. | A toolbox integrating model-based diagnosability analysis and automated generation of diagnostics | |
| Jetley et al. | Applying software engineering practices for development of industrial automation applications | |
| Filipovikj et al. | Automated SMT-based consistency checking of industrial critical requirements | |
| David et al. | Improving reliability studies with SysML | |
| Boroday et al. | Can a model checker generate tests for non-deterministic systems? | |
| Garro et al. | Modeling of system properties: Research challenges and promising solutions | |
| Tundis et al. | Model‐Based Dependability Analysis of Physical Systems with Modelica | |
| Chen et al. | Ontology based behavior verification for complex systems | |
| CN111881055B (en) | Simulink model design method for military software evaluation specification | |
| Mekki et al. | Validating time-constrained systems using UML statecharts patterns and timed automata observers | |
| Pakonen et al. | Evaluation of visual property specification languages based on practical model-checking experience | |
| MacKenzie et al. | Verification technology potential with different modeling and simulation development and implementation paradigms | |
| Garro et al. | RAMSAS4Modelica: a Simulation-driven Method for System Dependability Analysis centered on the Modelica language and related tools | |
| Kaufmann et al. | A Framework for Integrating Automated Diagnosis into Simulation | |
| Mavridou et al. | Bridging the Gap Between Requirements and Model Analysis: Evaluation on Ten Cyber-Physical Challenge Problems | |
| Gómez-Abajo et al. | Gotten: A Model-Driven Solution to Engineer Domain-specific Metamorphic Testing Environments | |
| Semeráth | Formal Validation and Model Generation for Domain-Specific Languages by Logic Solvers | |
| Sahraoui et al. | Methodology for fast prototyping of distributed real-time systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: AVIATION INDUSTRY GROUP OF CHINA XI AN AVIATION CO Effective date: 20140127 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| C53 | Correction of patent of invention or patent application | ||
| CB03 | Change of inventor or designer information |
Inventor after: Bai Xiaoying Inventor after: Zhang Renwei Inventor after: Niu Wensheng Inventor after: Li Yahui Inventor before: Bai Xiaoying Inventor before: Zhang Renwei |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: INVENTOR; FROM: BAI XIAOYING ZHANG RENWEI TO: BAI XIAOYING ZHANG RENWEI NIU WENSHENG LI YAHUI |
|
| TA01 | Transfer of patent application right |
Effective date of registration: 20140127 Address after: 100084 Beijing Beijing 100084-82 mailbox Applicant after: Tsinghua University Applicant after: AVIC XI'AN AERONAUTICS COMPUTING TECHNIQUE RESEARCH INSTITUTE Address before: 100084 Beijing Beijing 100084-82 mailbox Applicant before: Tsinghua University |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |