UI Automation without Selenium
I have been experiencing satisfaction over UI automation efforts after a half-decade of my work in automation. The reason is new age tools like Jest and Enzyme.
No more relying on selenium for checking UI
No more relying on long execution times to verify screens
No more worrying about different drivers and browser versions
No more inspection and formation of dynamic xpaths
My emphatic outburst is based on real client experience. I have been able to execute 100s of tests under a minute. Thats something not imagined in selenium world. Typical Test Automation Pyramid has unit tests at bottom, services tests in middle and most of UI testing in terms of acceptance tests at top.
This pyramid works well in most of cases and is good compromise to hedge risk against functional issues. UI is presumed to be relatively stable once functionality is designed and we live optimism that this is taken care of.
But since advent of Node and thereby isomorphic apps, UI has become intelligent enough to render on client based on different states/workflows and conditions. On same lines, there is rise in tools that mimic JQuery within virtual DOM and get rendered HTML. THis can then be easily verified. There is also limited UI interaction available within rendered HTML which allows you to test client side validations to a good extent.
This really takes off a major load of verifying UI pages and texts thereon. Thats the good and straight part.
Challenging part is that such apps depend on lot of server responses which are mocked in such tests. There lies real craft on organization of such mock responses as well as ingesting any real world change in those mock responses.
Once this challenges are taken care of, I am sure you(and Product team) will enjoy the fruits of Test Automation!!!
No more relying on selenium for checking UI
No more relying on long execution times to verify screens
No more worrying about different drivers and browser versions
No more inspection and formation of dynamic xpaths
My emphatic outburst is based on real client experience. I have been able to execute 100s of tests under a minute. Thats something not imagined in selenium world. Typical Test Automation Pyramid has unit tests at bottom, services tests in middle and most of UI testing in terms of acceptance tests at top.
This pyramid works well in most of cases and is good compromise to hedge risk against functional issues. UI is presumed to be relatively stable once functionality is designed and we live optimism that this is taken care of.
But since advent of Node and thereby isomorphic apps, UI has become intelligent enough to render on client based on different states/workflows and conditions. On same lines, there is rise in tools that mimic JQuery within virtual DOM and get rendered HTML. THis can then be easily verified. There is also limited UI interaction available within rendered HTML which allows you to test client side validations to a good extent.
This really takes off a major load of verifying UI pages and texts thereon. Thats the good and straight part.
Challenging part is that such apps depend on lot of server responses which are mocked in such tests. There lies real craft on organization of such mock responses as well as ingesting any real world change in those mock responses.
Once this challenges are taken care of, I am sure you(and Product team) will enjoy the fruits of Test Automation!!!
Comments
Post a Comment