On Tue, Apr 28, 2015 at 4:52 PM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> For a layout engine, being able to attach an actual testcase to a bug > report is _really_ useful once you get out of "just build it" mode and into > "fix all the bugs in this thing you built" mode. Github issues simply have > no way to do this that I've been able to find. You can put testcases on > jsfiddle or other such services, but it's really hard to do minimal > testcases that way because of all the things those services pull in, it's > impossible to test some things (e.g. parser issues, quirks mode) because > there's little control over the markup, and there are absolutely no > guarantees your testcase will be around in 5 years when you want to see > what that code change was trying to fix. > > This is really a problem I expect you'll want to solve at some point if > you want to be able to get useful functionality bug reports and community > QA. Developers can commit testcases to a github repo and reference them with github.io URLs, but that's no good for casual (e.g. web-developer level) bug reporters. So, yes indeed. Rob -- oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo owohooo osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o oioso oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo owohooo osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro ooofo otohoeo ofoioroeo ooofo ohoeololo. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
