Refactoring - a key ingredient of evolution of your automation framework

Ever happened to you that your UI gets migrated to the angular stack while you have all the automated tests and infra in place in selenium Webdriver and Java framework. When you run your tests they are mostly flaky and and drain your efforts in fixing/false negatives?

Is the solution to this problem finding a new tool that fits well for angular UI such as protractor? Or to spend some time refactoring your existing framework to support angular UI and leverage the existing tests and infra in place?

In this talk we shall discuss the later solution and the implementation.

 
 

Outline/Structure of the Case Study

Refactoring your existing framework to support angular UI and leverage the existing tests and infra in place

Learning Outcome

refactoring your existing framework to support angular UI and leverage the existing tests and infra in place

Target Audience

Anyone who is into tetsing and dev

schedule Submitted 10 months ago

Public Feedback