Have you ever spent hours poring over a web application when making changes to the theme, looking for the consequences of CSS style rules that are too broad? Ever made changes to a client's website, only to find out the theming for the newly designed front page totally screwed up the formatting on the product pricing page -- after you deployed the changes?
You are not alone.
Enter PhantomCSS -- a framework for conducting automated visual regression testing for websites. In this session we'll cover:
- What is PhantomCSS?
- System Requirements for PhantomCSS
- Skillset Requirements to write test suites for PhantomCSS
- How can I use PhantomCSS to improve my QA process?
- Live demonstration of a PhantomCSS test suite, including a review of the output of test results
FOLLOWUP: For those of you interested, here is a link to the test suite example I used in the demonstration: https://gist.github.com/lhridley/b8dd4e5605b0e559b4dd
And since our sessions were running behind and we got cut off early, here is a link to the recording from Drupal MidCamp 2015, where the same presentation was made a few weeks earlier: https://www.youtube.com/watch?t=2963&v=WtJwqqLdSkY