~/talk

5 Levels of Automated Testing of an E-commerce Project

Talkat code.talks commerce 2019 · 2019-04-09..04-10· [testing]
links:none on file
slides:none on file

Five concrete testing layers for an e-commerce stack: fast unit tests that run 1,000+ tests in 4s against the shops framework, functional tests that boot services and roll back DB transactions to validate persistence and integration, broad but shallow Chavez HTTP smoke testing for every registered route (checks only HTTP status), heavyweight browser acceptance tests via Selenium that cover business flows but are brittle, and Gatling load tests to catch scale problems (50 → 50,000 products). Continuous integration with Jenkins and PHPStan rounds out the pipeline.

AI-written summary · about

  1. 0:00Intro
  2. 1:00What is testing
  3. 1:48Unit testing
  4. 5:39Functional testing
  5. 10:01HTTP smoke tests
  6. 11:44Advantages of smoke tests
  7. 15:17Advantages of acceptance tests
  8. 18:52Advantages of performance tests
  9. 23:19Coding standards
  10. 24:41Static analysis
  11. 25:07Architecture sniff
  12. 25:38Continuous integration
  13. 26:06Jenkins
  14. 26:52Resources
  15. 27:34Questions
~/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.