Continuous integration approach is very helpful for Agile projects. Nearly everyone has been using or at least considering to use it for Unit testing, isn't it right? But automated visual/CSS testing on Jenkins or other CI tool seems to be much less popular. Why it is so? First of all, you need to have a visual testing solution which is well-compatible with your CI tool of choice. Unfortunately, integrating them is typically not a simple task.
Our team has successfully implemented automated CSS testing on our Jenkins server with the help of Screenster, our QA automation tool which does not require coding and is free to try - on premise and in the cloud. It allows QA automation engineers to:
- create a visual baseline, with a screenshot for every test step and use it afterwards to detect UI changes
- launch automated visual tests via a Jenkins job right after the latest build was finished
- easily maintain the tests with the help of rich editing options: add or delete steps, approve steps, ignore selected CSS elements etc
And what is your experience with automated UI testing? Have you tried to implement CSS tests in CI environment? Are there any specific pitfalls you have encountered?
