You want to do performance testing in a reproducible test environment on React components but don't want to set up everything needed to get a test app set up as well as the tooling needed to collect performance metrics.
Using create-react-app + puppeteer + this custom script, you can get a reproducible test environment to collect performance timing metrics, page metrics from puppeteer, as well as metrics from puppeteer trace file via tracealyzer.
- Fork the repo
- Add your code to the create-react-app
- Run
npm build:local.- This runs
react-scripts buildwith thePUCLIC_URLenv var set tohttp://localhost:5000
- This runs
- Run
npm run serve.- This runs the
builddirectory at http://localhost:5000
- This runs the
- In a seperate terminal tab, run
npm run perf-test.- This runs puppeteer on the app being served on http://localhost:5000 and logs performance timing metrics, page metrics from puppeteer, as well as metrics from puppeter trace file via tracealyzer.
- Total time from start to load:
loadEventEnd - fetchStart - Time spent constructing the DOM tree:
domComplete - domInteractive - Time spent during the request:
responseEnd - requestStart - Request to completion of the DOM loading:
domInteractive - responseEnd - Render Time:
domComplete - domLoading
Source: https://gist.github.com/daliborgogic/5951a7380ff8b57464fcd24f6f42eb36#gistcomment-2237115
I referenced @markerikson's benchmark-react-redux-perf repo a lot.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify