preTask was renamed preScript

This commit is contained in:
soulgalore 2016-06-19 21:36:24 +02:00
parent b914a45f13
commit 5537f64f7e
1 changed files with 2 additions and 2 deletions

View File

@ -16,7 +16,7 @@ The current production version is developed in the [3.x](https://github.com/site
Version 4.0 is a ground up rewrite for node.js 4.3 and newer. It builds on all our experience since shipping 3.0 in December 2014,
the first version to use node.js. It's currently under active development, you can check the release schedule [here](https://github.com/sitespeedio/sitespeed.io/milestones). We're determined to make it the best version of sitespeed.io to date.
IMPORTANT: Firefox 47.0 broke the compatibility with Firefoxdriver, so until Firefox 47.0.1 is released, you need to use Chrome for sitespeed.io (or Firefox 46). You can read more [here](https://github.com/sitespeedio/sitespeed.io/issues/993).
IMPORTANT: Firefox 47.0 broke the compatibility with Firefoxdriver, so until Firefox 47.0.1 is released, you need to use Chrome for sitespeed.io (or Firefox 46). You can read more [here](https://github.com/sitespeedio/sitespeed.io/issues/993).
Documentation and tests for the upcoming version aren't in place yet. Rest assured, it will be before 4.0 is released.
If you would like to give the new version a spin, try the following (you'll need node.js and Firefox/Chrome installed):
@ -34,7 +34,7 @@ There's a lot of things that we want to improve since 3.0. Here's some of the mo
* We support HTTP/2! In 3.X we used PhantomJS and a modified version of YSlow to analyze best practice rules. We also had BrowserMobProxy in front of our browsers that made it impossible to collect metrics using H2. We now use [the coach](https://github.com/sitespeedio/coach) and Firefox/Chrome without a proxy. That makes it easier for us to adapt to browser changes and changes in best practices.
* We now support the feature that people asked about the most: Measure a page as a logged in user. Use --browsertime.preTask to run a selenium task to before the page is analyzed. Documentation is coming soon.
* We now support the feature that people asked about the most: Measure a page as a logged in user. Use --browsertime.preScript to run a selenium task to before the page is analyzed. Documentation is coming soon.
* New HAR files rock! In the old version we use BrowserMobProxy as a proxy in front of the browser to collect the HAR. In the new version we collect the HAR directly from the browser. For Firefox we use the [HAR export trigger](https://github.com/firebug/har-export-trigger) and in Chrome we generates it from the performance log.