• Product
    • Key Features
    • Visual AI
    • Automatic Test Management
    • Dashboard & Analytics
    • Ecosystem Integrations
    • Solutions For
    • Test Engineers
    • Developers
    • DevOps
    • Product & Marketing
  • Pricing
  • Customers
  • Resources
    • Get Started!
    • Documentation
    • Resource library
    • Blog
  • About
  • Careers
  • Sign In
  • Free Trial
  • Product
    • Key Features
    • Visual AI
    • Automatic Test Management
    • Dashboard & Analytics
    • Ecosystem Integrations
    • Solutions For
    • Test Engineers
    • Developers
    • DevOps
    • Product & Marketing
  • Pricing
  • Customers
  • Resources
    • Get Started!
    • Documentation
    • Resource library
    • Blog
  • About
  • Careers
  • Sign In
  • Free Trial
  • Home
  • >
  • 2015 Archives
  • >
  • November Archives
  • >
  • 23rd November Archives

Automated Form Validation Checking

How To
November 23, 2015By Richard BradshawNo Comments

It’s commonplace to see a form on a website; some are truly awful, some, believe it or not, can actually be a pleasant experience. But most have some method of validation on them and in my experience, checking this validation is something teams look to automate. It makes sense: populate a few fields, or leave them empty, click submit, and ensure the correct validation is delivered by the site. These are positive and negative scenarios.

Recently though, I was thinking about the form validation automation I have done in the past, and questioning its effectiveness. In my opinion, validation errors and message are there to talk to the user, to help and guide them into being able to complete your form. This is most commonly done using the colour red. Field, labels, error text, popups and messages tend to be all subject to being coloured red. It was this use of red that had me question my normal approach to creating automated checks for form validation.

Now, I’m no UX (User Experience) expert, but happen to know some very good designers. I asked them, why do we use red? It fairly obvious really, it’s a colour we all associate with stopping and damage. This is backed up in the Microsoft design guidelines: Read more…

Search

Protractor vs. Selenium: Which is Easier?

Protractor vs. Selenium: Which is Easier?

August 17, 2014
Applitools Named to CB Insights’ AI 100 List for the Second Year in a Row

Applitools Named to CB Insights’ AI 100 List for the Second Year in a Row

February 7, 2019
Record Playback and Visual Testing – Part 1

Record Playback and Visual Testing – Part 1

October 16, 2013

Applitools at Google’s GDG DevFest 2013

November 4, 2013
Applitools Eyes is Live!

Applitools Eyes is Live!

November 6, 2013

Popular Posts

  • Protractor vs Selenium Protractor vs. Selenium: Which is Easier? posted on August 17, 2014
  • 41 Awesome Quotes about Software Testing posted on September 30, 2014
  • Manoj Kumar Automating Accessibility Tests: Web is for Everyone posted on November 9, 2017
  • So many choices Comparing JavaScript Browser Automation Frameworks: Selenium Versus Webdriver.io Versus Puppeteer posted on June 25, 2018
  • How to Do Visual Testing with Selenium posted on December 17, 2014

Terms & Conditions | Privacy Policy | © 2019 Applitools. All rights reserved.
  • Key Features
  • Solutions For
    • Test Engineers
    • Developers
    • DevOps
    • Product & Marketing
  • Pricing
  • Customers
  • Resources
    • Get Started!
    • Documentation
    • Resource Library
    • Blog
  • About
  • Careers
  • Contact
  • Free Trial