A key area to consider while working on automation frameworks:<\/p>\n
Complexity vs configurability.. and their inverse relation<\/p>\n
To support more and more features, and make a solution scalable you’d want it to be more configurable<\/p>\n
However as you make it configurable, it is bound to become more complex.<\/p>\n
Sure using design patterns will ‘reduce’ the complexity, but inevitably will become complex as you make it configurable<\/p>\n
There’s a balance you want to maintain between the two.<\/p>\n
E.g. using libraries like cypress & robot you’d be able to create tests very quickly, but you loose control on certain configurability aspects, if you can live with them these are great<\/p>\n
So it’s going to depend on your situation, But the principle remains..<\/p>\n
#RedefiningSoftwareQuality<\/a>\u00a0#TestAutomation<\/a>\u00a0#AutomationArchitecture<\/a><\/p>\n<\/div><\/span>