George E.P Box wrote : Essentially, all models are wrong, but some are useful. It is clear that design patterns are useful in Software, but a wrong implementation can easily leads to a bad practice and a wrong application of the concept.
Browser automation is a fairly new technology and In my personal case I try to be a really pragmatic person, so I ask myself if I’m doing the right thing, Am I creating a really useful framework?, how can I do to do things better?.
Sometimes the answers are out there, sometimes they aren’t.
WebDriver is a quite interesting project and a lot of contributors are really helping to improve the product. But I feel like there is a need to really guide us on how to build a framework for Browser automation. But a guide on how to use WebDriver is not enough ( for that you can use the documentation).
What it is really necessary is a set of best practices that can help to implement that framework and a key element is the usage of the coolest and latest features of C#, so you can combine usability and technology.
As an example is the lack of documentation on how to use the PageObject patter. Yeah, they have some documentation but it just give you an idea how it looks like but the original question remains : How you can know if you are doing the right thing?
Experience maybe?. Yeah experience is always welcome, but there is a need to provide more documentation and best practice on how to use design patterns in the browser automation world, so you can model that patters to your application.
I would say that the best thing to do is provide feedback to the community so they can see what could be improved, or in the other hand starting writing that book 🙂