Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Front-end automated testing

Front-end automated testing

Slides of a presentation that I made for my job colleagues about front-end tests.

8ffce1486e39ee3f43f52be5580b9966?s=128

luiznasciment0

April 28, 2021
Tweet

Transcript

  1. Front-end automated testing Why? When? How? Luiz Nascimento

  2. Why?

  3. Confidence • No developer should fear the code • Constantly

    refactoring and improving • Catch bugs locally • Take every opportunity to guarantee that it works
  4. Scalability • Techinical scalability • People scalability • Maintainable projects

    • Assure that new features don’t break old ones • Documentation
  5. Time • First barrier is NOT small • It IS

    faster. • Less bugs, less problems, less rollbacks • Thins won’t break out of nothing • There is no superhero
  6. People • Good tech companies do it • Higher level

    • Attractive for awesome developers
  7. When?

  8. None
  9. • Use cases coverage > Code coverage • What is

    an integration test? • What about unit tests? • And what about E2E? • User behavior • Learning from other companies
  10. How?

  11. Tools • Jest • React testing library • MSW –

    Mock Service Worker • Cypress
  12. /sibelius

  13. None