\u201cIs every automation framework as complex as what we have learned\u201d?<\/p>\n
A question from one of the automation training participants, this was my answer:<\/p>\n
\u201cCertainly not, most projects DO NOT have such a complex framework, few companies would be happy if you could just write a few lines using Selenium.\u201d<\/p>\n
\u201cHowever, the teams that make a difference and don\u2019t get fired few months after they\u2019ve started, DO have complex frameworks like this one\u201d<\/p>\n
In the training we did a simple test with all the code in one file, it seemed very simple and easy to understand.<\/p>\n
The next step was to build a framework and learn how to \u2018architect\u2019 a proper structure, which off course seemed hard and unnecessarily complex for one test.<\/p>\n
The easy way is not necessarily always the best way. Be sure you do the \u2018right thing\u2019, not just the easy one.<\/p>\n
BTW the \u2018easy\u2019 automation scripts have a flakiness percentage anywhere between 30 \u2013 80%, you\u2019re better off NOT doing automation at all there.<\/p>\n
The hard way can get you a flakiness percentage UNDER 2%, makes all the difference.<\/p>\n
#QsDaily #automation #frameworkdesign #training<\/p>\n<\/div>