-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion: what does a typical performance run look like? #343
Comments
Also, I don't see why it's necessary to start beforeLaunch: function () {
httpServer.createServer({
showDir: false
}).listen('8080', 'localhost');
}, I guess README.md is simply outdated? |
@staltz There was a change in Chrome that broke Benchpress. |
@jeffbcross did give me a .zip of a newer version that should fix it, I just have been too busy to add it in. |
... and yes, the README might be a little outdated. |
Ok, I'll send a small PR to update the README, and wait for a Chrome fix. |
Closing for #348 |
I ran the performance scripts, and I'm not sure if they ran correctly, because I get a lot of zeroes on this table (while Chrome opened and tests seemed to be running):
I have not setup my development environment like you have. For instance, I didn't have
protractor
installed globally (it's a devDependency, so it's already installed locally). Instead I ran./node_modules/.bin/webdriver-manager update
and./node_modules/.bin/webdriver-manager start
prior to runningnpm run perf
. I also didn't have ahttp-server
installed globally since it's also a devDependency. If the output of that table above looks correct, then I can update the instructions in README.md to be less susceptible on "works-on-my-computer" issues. Relying on locally installed binaries is safer (also against version mismatch problems).The text was updated successfully, but these errors were encountered: