Skip to content
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

plots: smoke test for happy case #2411

Merged
merged 8 commits into from
Jun 13, 2017
Merged

Conversation

wwwillchen
Copy link
Contributor

A simple smoke test for plots. Will add more over time.

Closes part of #1980

@wwwillchen wwwillchen changed the title Plots smoke plots: smoke test for happy case May 31, 2017
get travis to retry
node $analyze_script --ci
node $clean_script

echo "Finished plots smoke test without errors"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dontcha need some set -e goodness to make this fail?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup.

plots/analyze.js Outdated
@@ -45,6 +48,9 @@ function main() {
GENERATED_RESULTS_PATH,
`var generatedResults = ${JSON.stringify(generatedResults)}`
);
if (args.ci) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can do

if (process.env.CI)

and avoid adding a custom flag

fi

node $measure_script --site https://google.com/ -n 2 --disable-network-throttling --disable-cpu-throttling
node $analyze_script --ci
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you want to assert anything about the analyze results?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll do this is in a follow-up PR - I think many of the potential issues (e.g. lighthouse changes that break plots) would be caught without assertions.

I'm thinking about processing the output and replace non-deterministic values (e.g. timing values) and then diff it with a golden file.

Copy link
Member

@paulirish paulirish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

marking this appropriately. my above comments. ;)

Copy link
Contributor Author

@wwwillchen wwwillchen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@paulirish - oy sorry for the long delay. can you take another look?

plots/analyze.js Outdated
@@ -45,6 +48,9 @@ function main() {
GENERATED_RESULTS_PATH,
`var generatedResults = ${JSON.stringify(generatedResults)}`
);
if (args.ci) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

fi

node $measure_script --site https://google.com/ -n 2 --disable-network-throttling --disable-cpu-throttling
node $analyze_script --ci
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll do this is in a follow-up PR - I think many of the potential issues (e.g. lighthouse changes that break plots) would be caught without assertions.

I'm thinking about processing the output and replace non-deterministic values (e.g. timing values) and then diff it with a golden file.

@paulirish
Copy link
Member

Only +30s to travis times. Not bad. :)

@paulirish paulirish merged commit 1c5c57f into GoogleChrome:master Jun 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants