Your SlideShare is downloading. ×
Iswim for testing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Iswim for testing

184
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
184
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. ISWIM For Testing – A Model Driven Approach Tony Clark Xactium [email_address] www.xactium.com
  • 2. Overview
    • A Requirement for Constraints:
      • Telecomms
      • Aerospace
      • Business Migration
      • Information Systems, SOA
    • ISWIM Constraint Representation
    • ISWIM for testing
    • Conclusion
  • 3. Modelling with Constraints
  • 4. Telecomms
  • 5. Network Models Check configurations based on properties of devices and network components.
  • 6. Aerospace Message Bus Integrated Modular Avionics (IMA)
  • 7. IMA Models Check configurations of IMA components that must satisfy requirements of navigation modes.
  • 8. Payload Configurations
  • 9. Business Processes
  • 10. Restructuring A Company Check sequences of company snapshots – do they satisfy the business goals? Restructure Company Produce Plans Implement Plans Produce BizRep Develop Plans Produce Restructuring Plan Produce Operating Plan Ditch Unprofitable Customers Reorganize products
  • 11. Web Services and SOA
  • 12. Information Systems
  • 13. ISWIM Constraint Representation
  • 14. Constraints
    • What not to be: OCL, Java.
    • Visual language (why?), with examples:
      • Simple state.
      • Variables.
      • And/Or/Not
      • Quantification
      • Predicates.
  • 15. Snapshots
    • Objects, slots and links.
    • Context must be given:
      • Parameters
      • Root object
      • Self in state machine.
      • Observations in goals.
    • Conjunction of contents.
    • Negation.
  • 16. Snapshots as Constraints not c.business_report.terminal and c.restructuring_plan.addresses = c.business_report
  • 17. Sharing via Identifiers (separation of concerns)
  • 18. Negation … but not ...
  • 19. Unknowns Tied Together … same as …
  • 20. Links Over Collections
  • 21. Universal Quantification
  • 22. Existential Quantification
  • 23. Snapshot Checking Machine
  • 24. Syntax Model
  • 25. An Execution Machine
  • 26. Machine Transitions
  • 27. Auxiliary Machine Defs
  • 28. An Implementation – ISWIM for Model Driven Testing
  • 29. Testing Architecture Program Testing Engine Interface (XML) Program Display Test Reports (HTML) Display Test Cases (HTML) Model (XMF-Mosaic)
    • Test cases include:
    • Static Scenarios
    • Dynamic Scenarios
    • Invariants
    • Pre/Post Conditions
    • State Machines
    C B A D E F G H I Test Cases (XML) Test Reports (XML)
  • 30. A sales system keeps info on customers, their accounts and their orders. Customer ids (CID) are unique, but customer information may be distributed.
  • 31. Model Browser A model is constructed that shows the structure and behaviour of the application. The model could be extracted from an implementation or could be constructed by hand or could be constructed from another modelling tool. The example shows the classes extracted from a Java application.
  • 32. Test Specification
    • Each class may have:
    • Static scenarios defining typical configurations of instances. These may be positive and negative examples.
    • Invariants defining conditions that must hold true at all times.
    • Each operation may have specifications defining:
    • Precondition defining an expectation of the method.
    • Postcondition defining a corresponding guarantee if the precondition is satisfied.
  • 33. Static Scenarios A static scenario defines a collection of objects that conforms to the model. The tool will support the construction of the scenarios by completing slots and links where possible. Types of values can be checked by the tool. The scenario represents an implementation independent definition of application data. It might represent a correct, or an illegal, configuration. The scenario can be exported in XML and recreated as implementation data. SomeContacts
  • 34. Example Invariant For any sales system, With a contacts database, For each known person p, It is not the case, That the customer id value is EMPTY. NoEmptyCID
  • 35. Another Invariant For any sales system, With a contacts database, For each known person p1, With an id x, It is not the case that, There is a known person p2, With the id x, Where p1 and p2 are different people. AllCIDsUnique
  • 36. addContact(String id,String info) Pre-condition Post-condition
  • 37. placeOrder(String id,int items) post-condition
  • 38. Export as XML
  • 39. Modify Source (or use class loader)
    • public class SalesSystem {
    • ContactsDB contactsDB = new ContactsDB();
    • OrderSystem orderSystem = new OrderSystem();
    • public void addContact(String CID,String info) {
    • JTest test = JTest. startCall ( "test/SalesSystem" , "addContact" , this ,CID,info);
    • if (legal(CID)) contactsDB .addContact(CID,info);
    • test.endCall( null );
    • }
    • public void placeOrder(String CID, int amount) {
    • JTest test = JTest. startCall ( "test/SalesSystem" , "placeOrder" , this ,CID,amount);
    • orderSystem .placeOrder(CID,amount);
    • test.endCall( null );
    • }
    • }
  • 40. A Test Harness
    • public static void main(String[] args) {
    • SalesSystem sales = (SalesSystem)JTest. build ( "test/SalesSystem" , "SomeContacts" );
    • JTest. startRecording ( "C:/testResults.xml" );
    • JTest. checkInv ( "test/SalesSystem" , sales);
    • sales.addContact( "PERSON1" , "Fred is a sales manager." );
    • System. out .println();
    • sales.placeOrder( "PERSON1" ,10);
    • JTest. stopRecording ();
    • }
  • 41. Test Results
  • 42. Conclusion
    • Constraints occur everywhere in modelling
    • Constraints can be expressed as snapshots (ISWIM).
    • Constraints can be executed in various ways to suit the solution.
    • ISWIM-constraints can be implemented as a tool for model driven testing.

×