How to Overcome Change Blindness in Testing

- Poornima Sarangapani QA, Thoughtworks

How to overcome Change Blindness in Testing

ThoughtWorks, http://twchennai.github.io/VODQA-Chennai/

http://www.google.com/url?q=http%3A%2F%2Ftwchennai.github.io%2FVODQA-Chennai%2F&sa=D&sntz=1&usg=AFQjCNHdfPcLzXPURN1xQebS_jwFwaPgYg

• Unable to notice visual changes• Brain cannot possibly process every element of an

experience• Fail to notice a major change - focused on another

task• Selects certain things to focus - filters out anything

that is unrelated

What



• We concentrate on how does the feature work more compared to how does the feature looks.

• One pixel difference can make a vast difference• Other elements will get affected

Why is it important



Test Your Awareness : Whodunnit?


https://www.youtube.com/watch?v=ubNF9QNEQLA


Figure the differenceFigure the difference



HereHere



How



• Pretty terrible at spotting changes in visual stimuli

• Very difficult to do for a bigger application

• Focus shifts on non testable stuffs

• Repetitive

• Different responsive layout

Manual Cons



• Wraith

• Lineup

• Applitool eyes

• BackstopJS

• BackTrac

• csscritic

• Diff.io

• Dpxdt

• Galen Framework

• Gemini

• Ghost Inspector

• Hardy

• haunterjs

• PhantomCSS

• Rockcss

• SiteEffect

• Screenster

• Huxley

• Kobold

• Argus Eyes

• mirror-mirror

• Ocularjs

• Percy.io

• reg-cli

• Spectre

• VisualReview

Tools available



Demo



• Visual regression tests are not a replacement for good development practices and a good CSS architecture.

• capture screenshots for small modules or components - image comparison is faster

• Integrate your visual tests with some continuous integration platform

Good Practices



Thank You



How to Overcome Change Blindness in Testing

Technology

Transcript of How to Overcome Change Blindness in Testing