published by Anonymous on December 27, 2016 - 15:16
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:
Repeated verification of the same areas, looking for tiniest inconsistencies is a pain, as everyone knows. Here are most common challenges UI regression testing brings:
advantages ? Domain-specific languages allow solutions to be expressed in the idiom and at the level of abstraction of the problem domain. Consequently, domain experts themselves can understand, validate, modify, and often even develop domain-specific language programs. ? Self-documenting code.
Recent comments