Migrate, Modernize and Build Java Web Apps on Azure: This live workshop will cover methods to enhance Java application development workflow.
Modern Digital Website Security: Prepare to face any form of malicious web activity and enable your sites to optimally serve your customers.
Software developer at Playtika
About
Software developer with over 6 years of experience. Passionate to JVM languages: Java, Kotlin, Groovy. In love with micro-services world, believe in Scrum. Open source contributor: Camel, Spring Boot, Spring Cloud Config, Spring Cloud Netflix, Netflix Eureka, Test Containers for Spring Boot. Github: https://github.com/tdanylchuk Twitter: https://twitter.com/tdanylchuk
Stats
| Reputation: | 176 |
| Pageviews: | 63.7K |
| Articles: | 1 |
| Comments: | 2 |
Articles
Comments
May 25, 2019 · Taras Danylchuk
Well it depends on the system, and if you have simple logic of 2-3 cases of cource you may write single functional test instead of 2 integration tests (controller and repo).
But in most cases your code will evolve fast by adding new functionality and all of this functionality you will need to maintain, means each new addition should be covered by tests, so instead of adding new integrations tests (which are relatevely faster) you will add 1-2 functional tests, which can't cover all corner cases and time execution are far bigger than few integration tests.
To know more about difference and need of these two types of testing visit my second article about functional tests - https://dzone.com/articles/advanced-functional-testing-in-spring-boot-by-usin .
Oct 25, 2018 · Taras Danylchuk
You are welcome, I'm glad that it was helpful for you.