Automated tests
The problem
A home equity operation goes through many hands (partner, analysis, legal, payment) and every stage requires documents and checks. Without a single place, operations stalled and nobody knew which stage they were in or what was missing to move on.
Integration tests by default: the real Spring context, real PostgreSQL and RabbitMQ in Testcontainers, requests through the filter chain. Line and branch coverage at 100%, measured by JaCoCo.
Decisions and why
- A real database instead of mocks
- A mocked repository passes the test and fails the constraint in production.
- Mocks only at the machine edge
- Mail, storage and the clock. Declared on the abstract test, never scattered.
- One test class per domain
- SessionTest, MfaTest, UserTest: the name says what is covered.
requestresponse
Pick a scenario above to watch the message travel through the architecture.
What it looks like
Replica of the pipeline board with fictional data (internal system) esteira.evilrabbit.com.br/lines/triage
Triagem
Conferência de dados2
Marina SouzaGMR$ 480 mil 1 d
Paulo HenriqueR$ 1,2 mi hoje
Combate à fraude1
Ricardo AlvesAPR$ 750 mil 4 d
Validação dos documentos2
Carla PradoGMR$ 610 mil 2 6 d
João ReisR$ 295 mil 2 d
Aguardando aprovação0
Nada aqui