[TIMOB-17499] Windows: Create WP81 Unit and Performance Tests
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Closed |
| Resolution | Won't Do |
| Resolution Date | 2015-09-09T17:56:25.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Windows |
| Labels | n/a |
| Reporter | Ingo Muschenetz |
| Assignee | Christopher Williams |
| Created | 2014-08-12T21:24:11.000+0000 |
| Updated | 2015-09-09T17:56:25.000+0000 |
Description
1. Create WP81 unit and performance tests for JavaScriptCore that integrates with the CI server setup by Allen.
1.1. The unit tests should be based in test262 (this is item 7 from the Igalia SOW).
1.2. The performance tests should be based on JSBench.
A comment from Matt: "To use JSBench: It means we have to host JavaScriptCore in WebKit, which means building WebKit (which is basically Safari) for WP81. If this is easy (we haven't tried) then we should use JSBench. If not, then we'll need to create our own benchmark suite." I'm curious if we can't use SunSpider instead (see http://www.sencha.com/blog/javascript-engines-how-to-compile-them/) as that what's they suggest as a mechanism. It should has to demonstrate that the engine is much slower on Windows Phone vs OS X, and that we can make sure work we do to fix Windows brings those benchmarks closer together.