1

I am working for a young startup (eLearning) and we are actually in an early stage where our (dev) performance is measured by working features at the end of a sprint.

A company with a really good VRT product wants to work with us (1 month free and after that they want money). But I do not know if it is necessary yet. Because:

  • we do not have many visitors at our site (yet)
  • we have a really good deployment performance (several times a day)
  • we've already behat running (dev- and on test system via jenkins)

I think that a really large site needs such tests. Because they lose much money, if there is a bug on their live system.

I want to know if there are other reasons for using such tests in an early startup that is already live, but has even no QA team.

What are the indicators for a need of such VRT product?

1

VRT is required for validating the User Interface of the application. It targets the overall Look and Feel of the aplication including CSS, HTML, Quality and type of images, alignment & positioning of the various fields and user controls, Style Guide etc.

In today's competitive world when there are lost of similar web applications (eLearning), one has to come up with certain features different from other applications it can be Content, Accessibility, Cost and User Interface (ofcourse). UI is the first thing which will catch an user's attraction, so this must be validated. Again, this testing becomes utmost important if your application if supporting Multiple Browsers and Mobile platforms and that too with multiple resolutions & most important different mind set of peoples (I think, there is no reason in current times of not providing support to these features). It is also required if you want your application to be responsive.

As per me, competition is more when it comes to startups as they have to grow and for growth they need to work and deliver extra set of features and improvements. But, if your application is already live and you have already received a good user response then priority of this testing can be reduced. Ofcourse, with the delivery of new features and use of new technologies you have to maintain and nurture the Quality of the product (both in functional and non-functional ways) to avoid broken CSS and Style guide with new features, as breaking CSS is easy, but testing it is hard.

I have worked in a project where competition was there between different applications of the same client for achieving highest rating for both Functional and Non-Functional features (like GUI, Performance, Security etc.). So client has 2 members of special team for validating only the UI of the application across different browsers (thank god we didn't have mobile support at that time).

There are many tools (free and licensed) available in market for VRT. But as mentioned by experts in earlier post of SQA that biggest & most efficient tool for validating the visual appearance of a web application is Human eye and brain. So, you can go for manual testing too, but your problem becomes more bigger when you added 'No QA team' is there for carry this kind of testing either manual or automated.

If I have been in your place, I will talk to the third party that after 1 month of free trial, I (including other team members) will analyze their findings & reports and if we find that they are adding some good values to my application, then we can continue with them, else terminate the contract. Another option, is to hire a QA for this activity (obviously not only for VRT but also for functional testing too, if feasible). This will be more efficient and good paying option in long run.

Courtesy to the existing post.

0

Visual regression testing with PhantomCSS or WebdriverCSS PhantomCSS and WebdriverCSS are the default image comparison modules for, respectively, PhantomJS and Webdriver.io.

Tools of this kind automatically take UI screenshots and compare them to baseline images during regression testing. They also notify you of visual regressions by failing tests in case the layout is broken. In addition, some of these tools can black out UI regions, which is useful for dealing with timestamps, ads, avatar images, and other dynamic UI areas.

But can they really make for efficient visual regression testing tools? It depends on how much time and effort you’re ready to invest into UI testing.

As far as automated image comparison goes, popular code-based image comparison solutions don’t offer much in terms of ROI. Even though they spare you from having to eyeball each page in search of layout regressions, they also tend to over-complicate things that are supposed to be simple. There’s a case illustrating what I’m talking about.

  • While this is a decent description of some visual regression testing tools, it does not answer the OP's question, which is asking when such tools should be used. – Kate Paulk Feb 19 '18 at 12:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.