How to push a ReactJS application in production...
summary
Argues monitoring is nonnegotiable and names sentry New Relic truck Jas as one‑liner integrations for real‑time errors, recommends unit testing reducers and components with Karma + Jasmine + PhantomJS, uses a shallow renderer to isolate presentation tests, and uses redux mock store to assert thunk action sequences. Advises every thunk to return a promise so tests can await resolve/reject, warns end‑to‑end tests are slow and require backend fixtures, and suggests sketched test definitions (skipped tests) when time is short.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:56Let's start by defining some testing concepts...
- 6:29Useful tools to do unit testing in Reacts
- 8:16Unit testing a reducer function is a piece of cake... really!
- 10:40Unit testing components rendering
- 15:57Unit testing components behaviour
- 18:22Unit testing middlewares and rich actions (thunk)
- 21:30Midway testing
- 23:08End 2 End testing with protractor
- 25:50Manual testing on multiple devices
- 27:22KEEP
related talks
25mReact developer? How are your production skills?
52mTesting Reactive Apps
32mCrafting a Bulletproof testing pipeline for React Apps
39mMaking Your React Apps Perform At Scale
45mReactive Testing Strategies with NgRx
53mTesting React Applications
32mPushing Bugs to Prod Responsibly with React and Redux
30mTesting Front-End Applications