The document discusses the "test pyramid" concept for balancing test suites from unit to end-to-end tests. It provides examples of different types of tests including unit tests, integration tests, UI/end-to-end tests. It also discusses challenges with different types of tests and strategies for addressing those challenges including dependency injection, mocks, and tools like Cucumber, Robolectric, and Pacto. The document seeks feedback on testing approaches and provides additional resources on testing best practices.
58. Test automation
closer to
the user
Testing on the
level of the users incl. browser,
network,
databases,
external systems,
âŠ
User
Journey
UI
Connection of UI
tests to a
persona like flow
through the
system
$$$
slower
fewer
Integration
Tests of multiple integrated method
Unit
Tests of single methods without dependencies
$
faster
more
closer to the
developer
https://my.thoughtworks.com/docs/DOC-21002
- Quemfaz TDD?Quemfaz Testes Automatizados?Quem tem um servidor de CI rodando com um sequencia de builds a cada commit?Quem tem mais de 80% de cobertura? (Google notes: Code coverage goal: 80% and no less!)Quemfazmais de um release porsemana?Quemconsegueirparaprodução de maneira 100% automatizada?