[Bug 62511] Mass rendering tests / visual diff

2014-08-07 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=62511

ssas...@wikimedia.org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from ssas...@wikimedia.org ---
Now deployed and mostly working ... still has some issues, but it is more in
the realm of tweaking and bug fixing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 62511] Mass rendering tests / visual diff

2014-07-22 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=62511

ssas...@wikimedia.org changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|marc...@wikimedia.org   |ssas...@wikimedia.org

--- Comment #3 from ssas...@wikimedia.org ---
The repo @ https://github.com/subbuss/parsoid_visual_diffs is now ready for
deploy.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 62511] Mass rendering tests / visual diff

2014-06-24 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=62511

--- Comment #2 from ssas...@wikimedia.org ---
(In reply to ssastry from comment #1)
 (In reply to Gabriel Wicke from comment #0)
  Once we have proper CSS hooked up as discussed in bug 51245 we should start
  automated visual comparisons between PHP parser HTML + CSS and Parsoid HTML
  + CSS. The easiest way to scale  surface this is likely testreduce.
  
  Some promising tools mentioned in a recent wikitech thread titled 'CSS
  regressions':
  
  * https://github.com/Huddle/PhantomCSS
 
 JS code driven by PhantomCSS (JS) and Resemble.js

Downloaded phantomcss and started looking at the code. PhantomCSS seems like a
wrapper to work with casper to acquire screenshots, etc. capserjs can be run in
nodejs using spookyjs. I'll try experimenting with this tomorrow. 

But, I'm now wondering whether the generated images might be too big and/or if
we'll get too many trivial rendering diffs, and whether running a normalizing
html diff on PHP and Parsoid HTML should be considered as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 62511] Mass rendering tests / visual diff

2014-06-23 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=62511

Gabriel Wicke gwi...@wikimedia.org changed:

   What|Removed |Added

Summary|Mass rendering tests|Mass rendering tests /
   ||visual diff

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 62511] Mass rendering tests / visual diff

2014-06-23 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=62511

--- Comment #1 from ssas...@wikimedia.org ---
(In reply to Gabriel Wicke from comment #0)
 Once we have proper CSS hooked up as discussed in bug 51245 we should start
 automated visual comparisons between PHP parser HTML + CSS and Parsoid HTML
 + CSS. The easiest way to scale  surface this is likely testreduce.
 
 Some promising tools mentioned in a recent wikitech thread titled 'CSS
 regressions':
 
 * https://github.com/Huddle/PhantomCSS

JS code driven by PhantomCSS (JS) and Resemble.js

 * http://pdiff.sourceforge.net/
C++ code .. probably standalone.

 * https://github.com/BBC-News/wraith
Ruby code driven by phantomjs + ImageMagick

 * https://github.com/igorescobar/automated-screenshot-diff

nodejs library and has a dependency on a C library (cairo). Not sure if it will
work with https://www.npmjs.org/package/image-diff which is ImageMagick
binding.

It looks like huddle's solution will fit neatly within our nodejs setup. But,
worth experimenting with a couple solns to see what works best in terms of:
performance, quality, ease of use.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 62511] Mass rendering tests

2014-03-14 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=62511

Gabriel Wicke gwi...@wikimedia.org changed:

   What|Removed |Added

   See Also||https://bugzilla.wikimedia.
   ||org/show_bug.cgi?id=62633

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 62511] Mass rendering tests

2014-03-10 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=62511

Gabriel Wicke gwi...@wikimedia.org changed:

   What|Removed |Added

 Depends on||51245

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 62511] Mass rendering tests

2014-03-10 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=62511

Gabriel Wicke gwi...@wikimedia.org changed:

   What|Removed |Added

   Priority|Unprioritized   |Normal

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l