You might be wondering why you don't find any new content on my site on the topic of test automation.
Well, I have not stopped writing about it. In fact, I have decided to create a new home for it.
My writings on test automation will continue on my new dedicated site Go Green Test Automation which you can find on https://www.testautomation.dev.
Hope to see you there, and don't forget to sign up for my newsletter once you are there.
I love writing Seleniums test scripts, but I have been getting frustrated with the messy structure of my tests. It seems that over time the test scripts get longer and all the WebDriver calls obscure the intent of the test and make it less and less readable. So, I was relieved to find that I was not alone in this frustration, and in fact, all my concerns where addressed in a test design pattern: Page Object Pattern.
The premise of a JSF Validator (javax.faces.validator.Validator) is that by default it will only be invoked whenever a value is entered in an associated input field. This makes sense, since validating an empty or unchanged value is mostly just a waste of CPU cycles.
Running a website is an increasingly complex matter. The evolution in web standards and rendering engines along with the massive adoption of capable mobile devices, can quickly take your website into the unknown. How fast and stable are your visitors network connection? How well does your site render on mobile devices?
Now, Responsive Web Design holds a lot of answers as to how to give your users a great experience on your website. But once you make that leap, you need to pay extra special attention to performance.