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:
published by Anonymous on January 27, 2016 - 09:32
Summary
The goal of this post is to show a possible way of organizing automation based on the development plan in order to automate tests as soon as possible, without losing sight of manual testing. The functionalities to be automated will have to be already tested manually prior to beginning.
Recent comments