Как можно построить универсальный инструмент автоматизации для своих нужд и нужд проекта

1. 1 Our own tool: first steps Presented by: MykolaKolisnyk

2. Why? Too much new knowledge Architecture gaps Inconvenient IDE Internal restrictions Heavy Weight solution Lack of integrity

3. Typical Result 06.02.11

4. I’ll make my own solution 06.02.11

6. Portable to any standard programming language

7. Client/Server architecture

8. Use of standard libraries

10. Architecture 06.02.11 Java client API Ruby client API C# client API Python client API Http server Command processor Command Command Command Command Command Command

11. Client/Server data communication 06.02.11 Code structures XML Request body JAXB Code structures Code structures XML Response body

12. Command Request structure 06.02.11 URL: <host>/<command class canonical name> Example: http://localhost:5000/com.sample.Test Body: XML data representation Example:

13. Sample server code 06.02.11

14. Sample client code 06.02.11

15. Technological expansion 06.02.11 GUI libraries System libraries SOA libraries Client ports

16. How to get the GUI 06.02.11 Find required window by attributes Retrieve window handle Send required messages (use JNA)

17. Typical window attributes 06.02.11 Caption Class Index

18. How to find window 06.02.11 While EnumWindows returns true WinClass matches No Yes Caption matches No Yes Index matches No Yes Get Handle found or null

19. Objects hierarchy 06.02.11 Window MovableWindow Control MainWindow TextField Button List DialogBox CheckBox RadioButton ListBox ComboBox

20. Sample declaration 06.02.11

21. Sample test code 06.02.11

22. Main growth directions 06.02.11 Expand technology support Create wizards as IDE plugins Port client to other languages Extend standard Test engines

23. Questions?

24. 06.02.11