Speaker: Josh Long / starbuxman Hi Spring fans! In this tip, we'll look at how to get fast-feedback and do integration testing with Spring Cloud Contract. In this video, we'll focus on HTTP-based services.
The tests are written using JUnit 4 (?), but I am using JUnit 5 now and I just can't mock the JPA Repository and the RestTemplate properly ... 😥 Errors keep showing up indicating that they actually trying to do real connections (and failed) ...
nice presentation . what is the recommended way for work with clients - put all of them into 1 git repository or create a new repository for every service? example: repository: service A repository: service B repository: service C repository: clients: module: service A client module: service B client module: service C client or repository: service A repository: service A client repository: service B repository: service B client repository: service C repository: service C client ?
I highly recommend to use one repo per service. This will be much easier to handle when you combine a build pipeline and build triggers. In addition it underlines the principle of encapsulation of microservices.
Hi I am using -spring-cloud-contract ver 3.0.0 I have contracts written in groovy and specify in gradle.build file BaseCallForTest ,unfortunately my ContractVerifierTest classes generated without extending class specified in BaseCallForTest in contracts. I am printing out value for BaseCallForTest and it is what i expect Any ideas/recomendations will be helpful
Best rapid coverage of CDC
awesome one , keep it up 👌
The tests are written using JUnit 4 (?), but I am using JUnit 5 now and I just can't mock the JPA Repository and the RestTemplate properly ... 😥
Errors keep showing up indicating that they actually trying to do real connections (and failed) ...
thanks nice explanations with example
Thanks, Josh!
excelanto 🤩
excellent video. Example with spring webflux???
nice presentation .
what is the recommended way for work with clients - put all of them into 1 git repository or create a new repository for every service?
example:
repository: service A
repository: service B
repository: service C
repository: clients:
module: service A client
module: service B client
module: service C client
or
repository: service A
repository: service A client
repository: service B
repository: service B client
repository: service C
repository: service C client
?
I highly recommend to use one repo per service. This will be much easier to handle when you combine a build pipeline and build triggers. In addition it underlines the principle of encapsulation of microservices.
Why it's unlisted?
I need to use 0.75x haha ...
Hi I am using -spring-cloud-contract ver 3.0.0
I have contracts written in groovy and specify in gradle.build file BaseCallForTest ,unfortunately my ContractVerifierTest classes generated without extending class specified in BaseCallForTest in contracts.
I am printing out value for BaseCallForTest and it is what i expect
Any ideas/recomendations will be helpful