1 / 15

Test Generation towards TTCN-3

Test Generation towards TTCN-3. Paul Baker. Background. Model-Driven Development (MDD) Motorola’s is a maturity MDD company Mature software company: SEI CMM & CMMI levels range between 3-5 Standards Participation ITU-T/ETSI: MSC, SDL, TTCN-3 (GFT),

rigel-pennington
Download Presentation

Test Generation towards TTCN-3

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test Generation towards TTCN-3 Paul Baker

  2. Background • Model-Driven Development (MDD) • Motorola’s is a maturity MDD company • Mature software company: • SEI CMM & CMMI levels range between 3-5 • Standards Participation • ITU-T/ETSI: MSC, SDL, TTCN-3 (GFT), • OMG: UML 2.0 & UML 2.0 testing profile • Requirements-based Test Generation & Verification • MSC2000 and UML 2.0 test generation and verification

  3. Test 1 Test 2 Send x Send y TEST SCRIPTS Receive w Receive z Pass Test Pass Test Typical Test Process • Test scripts manually prepared • Time consuming • Incomplete • Informal • Opportunity to introduce defects Test Development Automated Test System Test Scripts Test Execution PASS FAIL Test System System Under Test

  4. z B D Test 1 w y Test 2 x A C Test 1 Test 2 Send x Send y TEST SCRIPTS Receive w Receive z Pass Test Pass Test Auto Test Generation Process Formal Test Model System Implements Model Test Generation Test System Test Scripts Test Execution PASS FAIL Test System System Under Test

  5. z B D w y x A C Formal Test Models - Benefits Formal Test Model SIMULATION RESULTS • Verification and validation – simulation • Higher level of abstraction • Test model maintained only • Model may form part or all of the requirements

  6. Reduced Cost Benefits of Auto Test Generation • Reduced Cost of Producing Test Suites • Hand-written tests normally lead to ‘representative’ tests. • Greater get off the ground cost to set up test model • Reported reduction factors of up to 3x • Greater Test Coverage • Exhaustive nature of auto-testing tools • Improved Test Quality • All possible scenarios are explored thereby generating unexpected or obscure tests • Easier Test Suite Maintenance • Only the test model needs to be maintained, rather than the test suite

  7. ! Some Test Generation Considerations • Abstraction • Complexity • Constraint mechanisms • Selection strategies • Test strategies/coverage • Data • Static and dynamic • Data Pools • Model/test correctness • Valid tests • Test configuration • Traceability

  8. TTCN-3 Landscape UML 2.0, MSC, & SDL Application of test generation techniques possible UML 2.0Testing Profile Abstraction GFT/TTCN-3 1-to-1 Mapping TTCN-3 TRI/TCI

  9. Abstraction (1) UML 2.0, MSC, & SDL • The user does not need to be concerned with specifying: • test cases • test configuration • verdict handling • exception handling • test control • At this level of abstraction the user is concerned with: • the behaviour definition of the system with its environment • test coverage & strategies • model correctness UML 2.0Testing Profile GFT/TTCN-3 1-to-1 Mapping TTCN-3 TRI/TCI

  10. Data language also needs to be considered. In this case MSC is parameterised with TTCN-3. Simple TTCN-3 Example msc call_accept msc call_setup (x,y) system mobile1 mobile2 call_request call_request (called(x,y)) call_accept (call(x,y)) call_accept (call(x,y)) call_reject call_accept

  11. ptk Example: Test Generation Process Abstract MSC/test graphs Graphical Viewers HMSC, MSCs, TTCN-3 Data HMSC & MSCs Graphical Models + Data Model Correctness TTCN-3 & Data Analysis Syntax & semanticanalysis Semanticanalysis Pathology Analysis TTCN-3 Code or TTCN-3 ETS Test Analysis/ Generation TTCN-3 Test Strategy/Coverage, Selection Information, Optimisation etc Generation Directives

  12. Example: Model Correctness/Test Analysis • Model semantics are represented in terms of traces • Semantic analysis = 26 traces • Test analysis = 5 test traces • Model correctness identifies potential errors in the specification that can lead to invalid tests.

  13. Example: TTCN-3 Test Generation • Depending upon test generation directives a complete TTCN-3 suite can be generated. • In this case we: • Trade off path coverage vs no of test cases => 2 test cases • Only one test case may need to be executed => test control strategy • Useful tests produced • Generate TTCN-3 code • Conformance tests • Concurrent test scripts • Load tests

  14. Abstraction (2) UML 2.0, MSC, & SDL • At this level of abstraction the user is usually concerned with: • test cases • test configuration • verdict handling • exception handling • test control • specification correctness • However, the level of definition can vary. For example, it could be that only a partial test suite is defined containing a test configuration only. This means that test generation techniques can be applied for missing aspects. UML 2.0Testing Profile GFT/TTCN-3 1-to-1 Mapping TTCN-3 TRI/TCI

  15. Thank you Almost lunch time… – Questions?

More Related