Test Automation: Coded UI Test

2. Test Automation:Coded UI Test Jan 25th 2013

3. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

4. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

5. Automated Testing • Ensures you don’t miss out on running a test • Can actually enforce and drive clean design decisions • Have training value

6. Coded UI Test • Automated tests that drive your application through its user interface (UI) are also known as coded UI tests (CUITs). • These tests include functional testing of the UI controls. They let you verify that the whole application, including its user interface, is functioning correctly. • Coded UI Tests are particularly useful where there is validation or other logic in the user interface, for example in a web page. They are also frequently used to automate an existing manual test.

7. Coding Process with Coded UI Test • Test Cases • Recording the actions • Coding with testing strategies • Auto-compile and run • If tests fail • Fault in test script-> make appropriate modifications • Bug in the application -> report (PFOOTB) • If tests pass -> move ahead They are fun and challenging to write One has to carefully think of design for reusability and coverage

8. Recording the actions Coded UI Test Builder The Coded UI Test builder enables you to record actions and add them into your existing Coded UI Test Generate code Add assertion Show recorded steps Start recording

9. Understanding the tests • Test Window • Test View window • Test List Editor

10. Identify Portal Framework Defects • Bugs can be identified by Coded UI Test Habanero Portal Framework Out Of The Box

11. Identify Portal Framework Defects • Bugs cannot be identified by Coded UI Test Habanero PF Habanero OOTB

12. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

13. UI Map Class • The real work takes place • An assortment of supporting classes are generated • Class diagram helps you to understand the relationships and the classes • involved.

14. Generic Library • Using the auto-generated code in designer.cs Class is very inefficient • Construct an efficient, reusable, beautiful libraries

15. Even More Generic

16. Class Diagram • Document Library • List • Calendar • Page • Asset

17. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

18. The Automated Test Framework

19. Program Pattern

20. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

21. Framework function • These framework functions will be documented in our Habanero QA site or visit QA site: https://h.habaneros.com/teamsites/QA/Lists/Framework%20Functions/AllItems.aspx

22. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

23. Demo I will run the following tests if time permits: • ContentPF • Test Cases: 1. Add content to a page • 2. Edit the content of a page • 3. Apply a markup style to content on a page • 4. Edit the HTML of the content on a page • ListInheritancePF • Test Cases: 1. Break inheritance on a list • 2. Break inheritance on a single list item • ListWorkflowPF • Test Cases: 1. Define a workflow for a list • 2. Perform workflow on a list item • PagePF • Test Cases: 1. Create new page • 2. Modify page properties • 3. Check in/ Check out a page • 4. Delete a page • 5. Email a link to a page

24. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

25. Reliability • Controls & Actions • Ensure the program find the correct controls • Ensure the actions get executed • Unstable Tests • Some tests may wander between Pass and Fail • Use Meaningful name • helps identify the purpose of the method • Limit each recorded method to fewer than 10 actions • Makes it easier to replace a method if the environment changes • Use the data from app.config file instead of hardcoding the data • Increase the reliability of making an assertion

26. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

27. Usability & Reusability • Coded UI Tests are completely reusable • Need to setup a continuous integration server • Create libraries as the codebase • Customize Search Properties • Overwrite Search properties with parameters • Customize Complete Functions • Atomic Tests • Tests are not depend on other tests • Reusable modules (The BaseTest Class) • Common test functions

28. Customized Search Properties

29. Customized Search Properties

30. Customized Functions

31. Customized Methods

32. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

33. Efficiency • Web Page Navigation

34. Efficiency • Eliminate Delay

35. Efficiency • Add Delay Sometimes, the control runs faster than the web browser

36. Introduction • Internal Class Structure (Generic Structure) • Program architecture • Framework function • Demo • Reliability • Usability & Reusability • Efficiency • Build Process in the Future

37. Test Cases Coded UI Test Build Process TFS MTM Client Projects

38. Build Process At this point, we have created numerous Test Cases. We can execute a Coded UI Test Case simply by taking the compiled assembly and executing it with Visual Studio or MSTest from the command line, which require us to sit there and do nothing while the test executes Another way: Associate Coded UI Tests and Test Cases Run the tests from Microsoft Test Manager Test Cases

39. MSTest

40. Associating Coded UI Tests and Test Cases (TFS)

41. Microsoft Test Manager

42. Next Step ( a typical way) • Set Up Team Build • With correct build definition and configuration • So that the automated test can be found in the share location for the • build definition and then it can be run from MTM • Create Test Settings and Virtual (Physical) Environment • We cannot run Coded UI Tests using MTM without an environment • Create an environment that contains the roles in the test settings and then use this environment in the test plan

43. Sometimes, things don’t work the way you want it to be.

44. If you have any comments on the coded UI test, feel free to let me know  Thank you