On 30/09/14 14:40, Josh Matthews wrote: > ---------- Forwarded message ---------- > From: Simon Sapin <simon.sa...@exyr.org> > Date: 30 September 2014 04:56 > Subject: Re: [dev-servo] Meeting notes 9/29 (CI; DOM binding safety; > SpiderMonkey upgrade; test harness improvements; dogfooding; security; > workweek; incremental reflow) > To: Josh Matthews <j...@joshmatthews.net> > > > https://github.com/servo/servo/wiki/Meeting-2014-09-29 > >> # Test harness improvements. >> - zwarich: Every time I run tests and see hundreds of processes, I wonder >> why we can't have one testrunner process that runs them in sequence. It's >> what webkit and blink do. >> - pcwalton: Yes, too much overhead right now. >> > > I happened to be talking with James about the test harness yesterday. The > reason we start a new Servo process for every test is that it’s the only > way to get Servo to navigate to another URL remotely. Other browsers use > WebDriver for this.
And, for the record the reason that the wpt tests are driven remotely is that they, unlike tests written specifically for servo, have to deal gracefully with behaviour like crashes or hangs. > We can probably fix this by implementing a subset of WebDriver. Reusing > processes for running many tests requires some kind of wire protocol to > communicate with them remotely, we might as well use a standard one. Yeah, for running just js tests the requirements aren't too bad. Basically you have to be able to use the protocol to load pages, execute some script, and send some results from the script back to the remote end. For reftests you also need to be able to take a screenshot. I guess actually navigating browsing contexts in servo could be a problem? _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
