After we finsih develop the JIT feature, how can we assure no crash will happen?
Do it follow below method.
Regression Test
Performance Test
Smoke Test
1. regression test[M]:
To run mozilla regression test use the following command: WebKit/WebKitTools/Scripts/run-javascriptcore-tests
2.we cann't avoid all the crash issue, but we try to avoid it[O].
i. run the performance test suit.(it will indeed catch the "obvious" crashes)
performance benchmark:
SunSpider:WebKit/WebKitTools/Scripts/run-sunspider Google v8:WebKit/WebKitTools/Scripts/run-sunspider --v8
Sputnik:http://test262.ecmascript.org/default.html
ii. run the layout test(the Layout tests also can catch crash )
iii. run the top 100 websites.(insure your browser call access most the popular web site without crash)
This good guide for proting the webkit:http://trac.webkit.org/wiki/SuccessfulPortHowTo
this code is for test the web page loader time:http://gitorious.org/methanol?page=1
EWS:is a designed to help catch build failures/test failures before patches are committed into WebKit.
web-page-replay:Record and play back web pages with simulated network conditions.
Adding archive.org-based page loading time performance tests: archive.org
In Chromium, we have --record-mode and --playback-mode flags for this
use case. They put the cache, cookie jar, and some other components
into a special mode where everything is aggressively captured and
replayed without going to the net. In the case of Firefox, I believe
someone at one time implemented a Firefox extension that rewrote pages
to capture resources and use local references.