110 likes | 187 Views
Conformance Testing with State Mapping. Vadim Mutilin ISP RAS. Conformance Testing. Implementation. Specification. Sys. M. conforms-to?. Test suite. Test case. T. t. *. Sys passes T. T is sound if Sys conforms-to M => Sys passes T
E N D
Conformance Testing with State Mapping Vadim Mutilin ISP RAS
Conformance Testing Implementation Specification Sys M conforms-to? Test suite Test case T t * SyspassesT T is sound if Sysconforms-toM => SyspassesT T is complete if Sysconforms-toM <=> SyspassesT
State Mappings • MAPPINGS: SPECS×IMPLSFUNCS • f=MAPPINGS(M,Sys) • f:SSysSM • In practice: • Reading an implementation state • Converting it into a specification one
Differences from FSM-based Testing • FSM vs. Labelled Transition System (LTS) • Equivalence vs. Conformance relation • Status message vs. State mapping
Test cases • ISO IS-9646 “OSI Conformance Testing Methodology and Framework” • OMG “UML Testing Profile” • Tretmans formalization: • Labelled transition system ‹S, L, T, s0› • Test case ‹St, L, Tt, ν, s0t›, • ν : St → {pass, fail} – verdict function. • Test run – synchronous parallel composition t||Sys (in initial state)
Derived Test Suite T3=Derived(Te3) • SyspassesTe<=> Syspasses Derived(Te)
Time of Test Execution • ρ(Te)<=ρ(Derived(Te)) • In example ρ(Te3) = 20 <=ρ(T3) = 53 • When < • Circles • Non-determination
Conclusions and Future Work • Theory • More efficient way of writing test suites • Practice • UniTESK formalized as FSM-based testing • Future • Conditions for test suite completeness
Thank you!Questions? Vadim Mutilin (ISP RAS) mutilin@ispras.ru