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:
Tools are specifically designed to target some particular test environment. Such as: Windows automation tool, web automation tool etc. It serves as driving agent for an automation process. However, automation framework is not a tool to perform some specific task, but is an infrastructure that provides the solution where different tools can plug itself and do their job in an unified manner. Hence providing a common platform to the automation engineer doing their job. There are various types of frameworks.
Recent comments