-
Notifications
You must be signed in to change notification settings - Fork 126
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
Tool for tracking history of values to monitor for regressions? #10
Comments
👍 This so much. Seeing the pagespeed score can be useful, but seeing the history and when regressions happen is much more useful. |
Is this beyond the scope of this module itself? This sounds like an awesome idea but maybe this feature can be pushed into another module responsible for running PSI multiple times and comparing the results. Guessing ultimately this goes back into a CI environment - would you want this locally? |
@jrcryer yup probably. so... somebody do it!
Yes. Might take some inspiration from https://github.com/es-analysis/plato |
I'm planning exactly to do that. ;) Putting in psi and draw the graphs e.g. is really a no brainer. Maybe someone wants to work together with me? |
@stefanjudis I can't promise masses of time but point me in the right direction and I'll see what I can help out with 😃 Plus - really like the graphs! |
@stefanjudis What @jrcryer said. If you are still in the idea/design stage, what do you think about a shared Google doc that we can collect our thoughts in? |
First of all I'd need inspiration at stefanjudis/grunt-phantomas#79. ;) But sure google docs would be nice. But once a repository is set up, maybe the github wiki is a better place? |
Any updates on this? |
We'd like to run this every time a component is updated, and track all numbers through time.
My goal is to be alerted when any numbers jump sharply.
For example: A sudden growth in Javascript Response Bytes could might mean a developer unknowingly added JS dependency significantly larger than we were expecting.
The text was updated successfully, but these errors were encountered: