Your SlideShare is downloading. ×
0
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
Test Automation Techniques for Windows Applications
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

Test Automation Techniques for Windows Applications

1,759

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
1,759
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
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. Unit testingUI AutomationAPI testing
  • 2. HandlesMessages Keyboard / mouse eventsTests – simulating user behavior
  • 3. With or without handlesDefault and custom messagesSynchronous and asynchronous callsMouse, keyboard usage
  • 4. Creation order (Z), IDsCustom components – support neededComponents without handlesHelpers : IAccessible, IWebBrowser2, …
  • 5. Caption, classIndentifying windows – Winspector, Spy++Window state – visible, hidden, modalDealing with unwanted windows
  • 6.  Custom components, inaccessible components need special actions Support on application side, custom message calls (or COM components ?) on test side DEVs - messages, code examples QAs / SDETs – add calls in tests Documents, early identification, communication 
  • 7.  Build validation. Can unit tests do the job ? Reduce integration risks and build confidence in own product Deal with geographically divided teams Continuous integration. How about continuous testing ? CI tools, triggers. Continuous integration for automation tests. Why do we need it ?
  • 8.  Testing environment: virtualization technologies Automation environment: testing software products in same conditions You need a control board. Hudson can do it ! Results ? What to do with them ? E-mail ? Alerts ? Validation vs. testing. Validate each build, test important ones
  • 9.  UI changes. Biggest threat for our tests So it happened. They changed the UI. Again. How do we react ? How about a backup ? API testing, unit tests Is there anything to do in order to be prepared for these events ? The cost of UI changes should include automation updates
  • 10.  Create models for your application Mapping UI elements with own classes. Hide implementation details Avoid using “map elements” directly in tests Adding abstraction layers can help you Functionality testing Testing framework vs. tests. SDET or QA ?
  • 11.  Data driven testing Can we keep only the logic in testing scripts ? Why store data in special files ? Is it even entirely possible ? Extend test coverage Open QA framework to all QAs. Enable them to write automation tests. In theory.
  • 12.  Build entire team confidence in automation tests Test and detect problems early. Maybe before commit ? Indentify problems before they get in the build Custom testing for developers
  • 13. Before Smokecommit tests Validate Regression Integration tests Bug-fixing cost increases
  • 14.  Hybrid application ? › Example: Windows application containing web components Mobile apps automation Web applications

×