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. Manual testing of user
My website has a test suite with visual regression tests; screenshot different webpages and compare against a set of expected images: https://github.com/twolfson/twolfson.com/tree/3.40.0/test/perceptual-tests/expected_screenshots This weekend, I switched it from PhantomJS to node-webkit and am happy with the results: Benefits node_modules/ always work (e.g. no process is undefined issues) node_mod
Check out my free 6-day email course on Visual Regression testing: https://learn.visualregressiontesting.com/ This screencast covers a basic introduction to Wraith, a screenshot comparison tool created by developers at BBC News. It includes a demonstration of the default script provided at installation, plus a custom implementation for a more real-world example.
I finally had a chance to play with PhantomCSS, a CSS regression testing tool that compares screenshots to see if CSS changes have affected the design, and wanted to share my experience with you. We are using it at Ariba to validate that I do not break any designs as I migrate us from two giant, unmanageable CSS files into smaller, modularize and better written lessCSS files. PhantomCSS uses Caspe
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
