Test Patterns: A New Concept for Testing

Transcription

1 Europe s Premier Software Testing Event World Forum Convention Centre, The Hague, Netherlands The Future of Software Testing Test Patterns: A New Concept for Testing Henk Doornbos, SIOG & Rix Groenboom, Parasoft, The Netherlands

2 Test Patterns -- a new concept for testing -- Henk Doornbos Rix Groenboom Research sponsored by

3 Overview Testing challenge Current testing techniques New approaches Towards Test Patterns Conclusions

4 Testing is Difficult SOA in particular Heterogeneous interfaces: Web, Gui, WS, JMS, JDBC Many dependencies Many re-configurations SOA Mesh: Mash up: Mess: Spaghetti oriented architecture

5 Testing is Difficult Architecture is heterogeneous TestTool ebxml / ebms AQ AQ DB link HTTP / SOAP GUI J U B E S CJIB B2B ERS BPEL EBS Advanced Queues VIP B2BG IPEX JDS B2BG

6 Testing is Difficult Many different interfaces: TestTool ebxml / ebms AQ AQ DB link HTTP / SOAP GUI J U B E S CJIB B2B ERS BPEL EBS Advanced Queues VIP B2BG IPEX JDS B2BG

7 Testing is Difficult Tester performs manual steps, eg: Enter user-data via website (with IE) Check database status (with TOAD) Submit XML message (with SOAPui) Check database status (with TOAD) Therefore, current process is tedious: hence error propone Not repeatable

8 Current testing tools Currently, there is a portfolio of testing tools with a focus on automation: Test management tools Individual tools for testing (GUI, Web, Load, DB) Main problem: Semantic gap, the tester is the glue between the different tools

9 Current testing tools Example: TestFrame Excel based technology Separation between logical and physical test cases Ad-hoc engine implementation for test automation No clear semantics

10 Current testing tools

11 Current testing tools Example: SOAtest Platform for testing SOA implementations Supports of multiple protocols (HTTP / JDBC etc) Test flow over multiple interfaces is possible Example CRUD operations: Search service call Retrieve service call Update service call Validate Database

12 Current testing tools

13 Towards solution More powerful tools allow automation of testing often for single interfaces Solves the technical interaction and provides repeatability We still need an integrated framework to drive the testing and to process the results (orchestration) Provides the flexibility to handle overall architecture

14 Towards solution IDEA 1: Use structure of architecture for testing Architecture is most stable part of applications Clearly defined interfaces Legacy Application Logic Thin Client Web Site Database Server Application Server Presentation Layer Web Services

15 Towards solution IDEA 2: Regard testing as a business process Make basic steps executable: call the relevant testing tools using a web-service interface BPEL for Test Orchestration

16 BPEL: Advantages BPEL: Web standard Direct execution of webservices Programming language, so you can define patterns (recurring structures) There are semantics so you can reason about processes BPEL for testing: Provide test-tool with web-service interface, so we can communicate with them directly from BPEL

17 BPEL: Example Drive SOAtest from BPEL

18 BPEL: Example Example integration: SOAtest & WebKing

19 BPEL: Provides also semantics Requires mathematical solution : Parallelism, non deterministic, asynchronous Testing will have mathematic laws: T1 + T2 = T2 + T1 T1 T2 = T2 T1 T1 + ( T2 T3 ) = (T1 T2) + (T1 T3) Use process algebra like CSP: Provides a framework to compose operations

20 Example pattern (0) CRUD operations CREATE READ UPDATE DELETE

21 Example pattern (1) Standard ESB structure: Basic services Integrated services Business services User layer: GUI Which test pattern?

22 Diagram: Example pattern (2)

23 Example pattern (1) Proposed test pattern: Unit testing of basic services Integration test: no new logic, therefore nothing to test Business process testing: Web submission

24 Diagram: Example pattern (2)

25 Example pattern (2) Database application with WS front-end B2B communication Legacy backend communication (mailboxes)

26 Diagram: Example pattern (2)

27 Example pattern (2) Special Web-services implementation for encapsulation of legacy protocol

28 Conclusions Testing of SOA is becoming increasingly complex Requires more mathematical approach BPEL can be used to model the test process Higher level of abstraction Better defined semantics Will lead to a library of test-patterns: Using proper automation, this gives reuse of test effort

29 About us Windesheim: University of Applied Sciences Parasoft: Provider of software test solutions for SOA and BPEL SIOG: St. ICT Onderzoek & Ontwikkeling Groningen Knowledge valorization Joint projects Groningen, Oldenburg, Bremen