Automated-UI-Presentation

What I learned about Automated UI Testing

My 2 Week Dive Into Automated UI Testing

by Zachary McKinnon

Introduction

• Where I Started
• My Journey
  • Test Lab Configuration
  • Microsoft Build Video
  • Selenium Deep Dive (Blog Posts, YouTube, Pluralsight)

Conclusion

• Microsoft is moving away from Coded UI. (Not Official, My Interpretation ONLY)
• Why?
  • It's Losing
  • New Technology (Appium)
  • Mobile Apps
• What does all this mean?

Technology Comparison (Coded UI)

Pros

• Existing Tests
• Works with Microsoft Tools (MTM, Load Testing)
• Microsoft Support
• Comfortable with Framework (Sorta)
• Pluralsight Courses

Cons

• Difficult environment configuration
• Not a lot of resources (My Experience)
• Microsoft is presenting alternatives

Technology Comparison (Protractor)

Pros

• Works Well with Angular

Cons

• New Language
• NPM + Microsoft = No Fun (for now)

Technology Comparison (Selenium)

Pros

• Most Popular Technology
• Easy Setup
• Good Resources (Pluralsight)
• Works with Microsoft Tools (MTM and Load Testing, surprisingly)

Cons

• All New Tests
• New Framework to Learn

My Suggestions

• Re-evaluate Automated UI Test Framework
• Make Automated UI Tests Run After EVERY Deploy
• Teach All QAs AND Developers How to Write These Tests
• Collaboration Between QAs and Developers Across the Board (Entire Pyramid)