Hello servo developers,
tl;dr version: I am considering a dissertation topic somewhere in the vicinity of: "QuickCheck-ing HTML/CSS rendering in modern browsers". This might have some relevance for Servo. Interested? Any feedback? Longer version: My name is Joel Martin (github.com/kanaka) and I am a PhD student at UT Arlington. Past projects of mine include noVNC, websockify (used in emscripten for TCP), make-a-lisp (including a Rust implementation), and Raft.js. I haven't quite settled on my dissertation topic, but my top contender at the moment involves property-based (i.e. QuickCheck style) generation of random web pages/stylesheets. The oracle would be a cluster of browsers (multiple vendors/variants) driven by WebDriver/Selenium that would render the test cases and screenshot them. Significant discrepancies between renderings would be considered a failing test case and then standard QuickCheck-style shrinking would be used to reduce the test case HTML/CSS to a minimal-ish reproducer. Besides the obvious case of finding rendering differences (and bugs) in browser rendering engines, this sort of testing seems especially relevant for brand new rendering engines such as Servo. Is this idea of interest to the Servo team? Would it be useful for Servo development/testing? Or perhaps redundant with existing testing I'm not aware of? If this idea is of interesting, is this the right forum for discussing it, or is there a person or subset of the team that would be interested in discussing it more with me (to keep the noise down here)? I value any feedback you might have. Joel Martin (kanaka) _______________________________________________ dev-servo mailing list [email protected] https://lists.mozilla.org/listinfo/dev-servo
