switching from jstestdriver
6 views
Skip to first unread message
craft...@gmail.com
Sep 2, 2014, 3:04:18 PM9/2/14
to buster...@googlegroups.com
Anyone switched from jstestdriver that can share their experiences?
We've had a number of issues with jstestdriver, including
1) had to write an AMD loader, and keeping dependencies updated takes some care
2) mishandling of unicode in js source (like d3.js)
3) inability to serve other file types such as images
4) poor latency
The latency is a combination of start-up time of the java command line tool, and the poll interval of the client stub. I suspect it would be much better if the client were long-polling, or using SSE, or something. How does busterjs do this?
We've had a number of issues with jstestdriver, including
1) had to write an AMD loader, and keeping dependencies updated takes some care
2) mishandling of unicode in js source (like d3.js)
3) inability to serve other file types such as images
4) poor latency
The latency is a combination of start-up time of the java command line tool, and the poll interval of the client stub. I suspect it would be much better if the client were long-polling, or using SSE, or something. How does busterjs do this?
Reply all
Reply to author
Forward
0 new messages