~/talk

Testing in Frontend World

Talkat Frontend fwdays'17 · on Sunday, 2017-11-26· [testing, frontend-architecture]
links:none on file
slides:none on file

Argues for a concrete frontend testing pyramid and shows what to run where: start with linting (ESLint auto-fix), then fast unit tests (Mocha/Jest), then component testing with Storybook plus snapshot tests and Enzyme for interaction, visual checks with Gemini/WebdriverIO and full E2E via Protractor or webdriver-based suites. Gives concrete numbers (three tests run in ~150ms, thousands slow CI), demonstrates Storybook stories and snapshot failures, and stresses CI integration (Travis/GitLab/Jenkins) for repeatable runs.

AI-written summary · about

  1. 0:00Introduction
  2. 1:47Why frontend testing
  3. 4:53Frontend testing types
  4. 6:20New testing pyramid
  5. 8:29Testing structure and principles
  6. 9:54FIRST principles for unit tests
  7. 13:48Test writing theory
  8. 14:11Linting as first step
  9. 17:07Unit testing specifics
  10. 18:51Component testing with React
  11. 21:20Storybook for visual tests
  12. 23:06Component interaction testing
  13. 25:14Visual testing with screenshots
  14. 26:59Integration testing in frontend
  15. 28:47Final testing pyramid
  16. 31:20Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.