![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();
}
40](https://image.slidesharecdn.com/iswimfortesting-110806075353-phpapp02/85/Iswim-for-testing-40-320.jpg)
Iswim for testing
- 1. ISWIM For Testing – A Model Driven Approach Tony Clark [email protected] http://itcentre.tvu.ac.uk/~clark 1
- 2. Overview • A Requirement for Constraints: – Telecomms – Aerospace – Business Migration – Information Systems, SOA • ISWIM Constraint Representation • ISWIM for testing • Conclusion 2
- 4. Telecomms 4
- 5. Network Models Check configurations based on properties of devices and network components. 5
- 6. Aerospace Message Bus Integrated Modular Avionics (IMA) 6
- 7. IMA Models Check configurations of IMA components that must satisfy requirements of navigation modes. 7
- 9. Business Processes 9
- 10. Restructuring A Company Restructure Company Produce Implement Plans Plans Develop Ditch Produce Reorganize Plans Unprofitable BizRep products Produce Produce Customers Restructuring Operating Plan Plan Check sequences of company snapshots – do they satisfy the business goals? © Xactium Ltd. 2007 10
- 11. Web Services and SOA © Ltd. 2007 11
- 12. Information Systems © Xactium Ltd. 2007 12
- 14. Constraints • What not to be: OCL, Java. • Visual language (why?), with examples: – Simple state. – Variables. – And/Or/Not – Quantification – Predicates. 14
- 15. Snapshots • Objects, slots and links. • Context must be given: – Parameters – Root object – Self in state machine. – Observations in goals. • Conjunction of contents. • Negation. 15
- 16. Snapshots as Constraints not c.business_report.terminal and c.restructuring_plan.addresses = c.business_report 16
- 17. Sharing via Identifiers (separation of concerns) 17
- 18. Negation … but not ... 18
- 19. Unknowns Tied Together … same as … 19
- 20. Links Over Collections 20
- 21. Universal Quantification 21
- 22. Existential Quantification 22
- 23. Snapshot Checking Machine 23
- 24. Syntax Model 24
- 25. An Execution Machine © Xactium Ltd. 2007 25
- 26. Machine Transitions 26
- 27. Auxiliary Machine Defs 27
- 28. An Implementation – ISWIM for Model Driven Testing 28
- 29. Testing Architecture C A Model Interface Program (XMF-Mosaic) (XML) B E D Display Test Testing Test Cases Cases Engine (XML) (HTML) G H Test cases include: F • Static Scenarios Test Display • Dynamic Scenarios Test Reports (XML) Program • Invariants Reports • Pre/Post Conditions (HTML) • State Machines 29 I
- 30. A sales system keeps info on customers, accounts and their orders. 30 Customer ids (CID) are unique, but custotheir mer 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. 31
- 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. 32
- 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, SomeContacts configuration. The scenario can be exported in XML and recreated as implementation data. 33
- 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 34
- 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 35 AllCIDsUnique different people.
- 36. addContact(String id,String info) Pre-condition Post-condition 36
- 37. placeOrder(String id,int items) post-condition 37
- 38. Export as XML © Xactium Ltd. 2007 38
- 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); } } 39
- 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(); } 40
- 41. Test Results © Xactium Ltd. 2007 41
- 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. 42