Wonderfully session. I was confused with pact broker verification against actual provider as mocking consumer side calls. Now clear. It is just verifying the contract that is produced with the help of mock provider against the actual provider.
Liked the presentation. Could you please share a video describing step-by-step creating the contract test project, that is going to be very helpful for beginners?
You can find the code used in the talk in this link : github.com/akhil-ghatiki/thoughtworks-vodqa-contract-testing Thanks for the input. We have not done any such video which describes step-by-step creation. Will consider this.
On the slide at 6:00 looks like integration testing happens within the same team. I though contract testing was providing an alternative to integration testing so I was expecting it to see it where end to end testing is in that slides, i.e. between the two teams
Contract testing helps integration testing to be quick and without any last minute surprise. Integration testing mainly focus on the functionality with the hope that basic contract testing was taken care by pact testing.
No, you can't do the contract testing for Kafka producer. A producer service will produce the payloads to the kafka broker. Here, we don't have control over the contract which Kafka uses. More over, we use client SDKs which own the APIs we use to either produce or consume the payloads. The contract will be intact between these APIs and the kafka broker. So, you as a developer need not worry about the contract between your producer and the kafka broker. To be more specific, the contract tests if any between the client SDks and the broker will be taken care by the team who actually developed Kafka. And, you can have integration tests between your producer and the kafka broker. Take a look at embedded kafka for it. Its library that provides an in memory kafka instance to testing.
Hi, Thanks for a great video to understand contract testing. I tried to follow the steps after cloning the git repo but endup with an error at the last step while running ./gradlew contractTest java.lang.IllegalAccessError: class lombok.javac.apt.LombokProcessor (in unnamed module @0x6f64fb74) cannot access class com.sun.tools.javac.processing.JavacProc essingEnvironment (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module @0x6f64fb74 Could you please help me ?
Wonderfully session. I was confused with pact broker verification against actual provider as mocking consumer side calls. Now clear. It is just verifying the contract that is produced with the help of mock provider against the actual provider.
useful presentation....especially for someone new to contract testing
do you have any course that would be very helpful
Wonderful Presentation. Thank you.
Great presentation..!! Thanks :)
Liked the presentation. Could you please share a video describing step-by-step creating the contract test project, that is going to be very helpful for beginners?
You can find the code used in the talk in this link : github.com/akhil-ghatiki/thoughtworks-vodqa-contract-testing
Thanks for the input. We have not done any such video which describes step-by-step creation. Will consider this.
On the slide at 6:00 looks like integration testing happens within the same team. I though contract testing was providing an alternative to integration testing so I was expecting it to see it where end to end testing is in that slides, i.e. between the two teams
Contract testing helps integration testing to be quick and without any last minute surprise. Integration testing mainly focus on the functionality with the hope that basic contract testing was taken care by pact testing.
Great work
Could you share github repository?
Good Work guys.. Can you advise how to contract test Kafaka producer? Thanks
No, you can't do the contract testing for Kafka producer. A producer service will produce the payloads to the kafka broker. Here, we don't have control over the contract which Kafka uses. More over, we use client SDKs which own the APIs we use to either produce or consume the payloads. The contract will be intact between these APIs and the kafka broker. So, you as a developer need not worry about the contract between your producer and the kafka broker. To be more specific, the contract tests if any between the client SDks and the broker will be taken care by the team who actually developed Kafka. And, you can have integration tests between your producer and the kafka broker. Take a look at embedded kafka for it. Its library that provides an in memory kafka instance to testing.
@@akhilghatiki6553 Do we have a github link for above demo project? Thanks
can you please share git repo for this?
Possible can you share the presentation please
Can give us GitHub link so we can walk through entire code
Hi, Thanks for a great video to understand contract testing. I tried to follow the steps after cloning the git repo but endup with an error at the last step while running ./gradlew contractTest
java.lang.IllegalAccessError: class lombok.javac.apt.LombokProcessor (in unnamed module @0x6f64fb74) cannot access class com.sun.tools.javac.processing.JavacProc
essingEnvironment (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module @0x6f64fb74
Could you please help me ?
Never mind i have solved it by upgrading lombok to 1.18.20, thanks