What is Contract Testing in API automation + Demo (EA Weekly)

preview_player
Показать описание
In this EA Weekly video of our EA Weekly series, we will be discussing Contract testing with Pact and understand how to make sure API testing we are doing is done on both the consumer and provider end while it's otherwise called as TestDouble.

When to start automation testing and what to automate ?
*************************************************************
Pact
******

Contract Testing
----------------------------

Udemy Course
---------------------------

EAWeekly series
----------------------------

Cypress Complete course
--------------------------------------------

Selenium Framework development courses
----------------------------------------------------------------------

#executeautomation #udemy #cypress #selenium
Рекомендации по теме
Комментарии
Автор

The exchange of the pact/contract files is the most trivial part of this. Changing the organization culture to produce contracts and for the dev teams to run them against their service is the harder part. The hardest part is getting the teams to communicate well. Indeed, contracts encode the understanding of each party formally and in a machine checkable way, which is always more precise than verbal or informal or formal-uncheckable communications/agreements.

paulfrischknecht
Автор

Thank you so are making a difference in other's lives....

MrUmang
Автор

I fail to understand what is the difference between end-to-end API response schema validation and using pact? It seems that end to end tests will run the same job anyway - so why do the test twice?

EYM-ONLINE
Автор

Hello, I can't find information about contract testing in DART

luisarmandobr
Автор

Thanks for this video, really good presintation, nice explanation.

sataneisen
Автор

I am not exactly able to understand how is consumer-driven contract testing different from behavior-driven testing? what is the pact server doing for consumer-driven contract testing that we have not been doing by specifying the expected behavior of the provider service in the consumer and verifying if the response from the provider matches the expectation in the consumer?

SimranKaur-ewuk
Автор

Thanks for the video, there are very few resources on this topic. There is only one thing I'm not clear on Imagine I'm the Consumer (The QA Team). I need to write ConsumerPactTest. What is my source of truth to write the tests? The documentation?

healthypessimist
Автор

This Video is really helpful to understand contract testing with PACT, but in real case if I do not want to use Pact Broken, still can we implement Contract testing(Without PACT)?.If I get a answer will be very useful.

poojashrikotan
Автор

Thank you for the video!

In a world where we have contract tests to verify the contract between the consumer/provider for a number of services endpoints with the real service being used for verification, what other tests do we need to write from an integration testing perspective?

Is there something that the contract tests are missing that we want other coverage around?
Do we reduce the number of necessary tests we need from an integration perspective by creating contract tests instead?

Cold_Shadows
Автор

So the contract is generated with real production data?

GG-uzus
Автор

Hi Karthik,

Comparing the JSON schema with API response body Structure and mandatory fields, types (json type response) is contract testing all about?

Pact seems to be useful while developing the application but in System testing or integration testing phase, is it all about validation Shema Rules vs JSON response sent by application?

Please let me know.. little confused here

BhargavMurari
Автор

Isn't this contract testing the same as testing the json schema of a response or request?...because if im expecting particular json structure to be returned then if it changes then my test will fail.

Boygadget
Автор

Hello, Thanks for this video, this example is sur Github ?

omarsaddaoui
Автор

can we use pact to test microservices that uses xml.. if yes can you please share any website links that explains this..

navaneethakrishnan
Автор

Thanks for making the video karthik, your videos are very educational. A small feedback: Maybe you should increase the font size of the code editor while recording as it is quite difficult to read the font. Thanks again!

Gaurav-S
Автор

Thanks for the video, I like the fact that both Consumer and Provider tests are mentioned and showed within a demo.

I feedback tho, I personally disagree with calling Contract tests "unit tests". Consumer tests use a mocked local API from Pact to create the contract files, while Provider tests use the actual API. Both are outside of the scope of a Unit. I'd call them integration tests rather.

worglord
Автор

Thanks for this stuff. Just wanted to know if we can do it for POST/PUT or it is only for GET HTTP requests?

afzalaiet
Автор

Thanks for such nice video. Could you please share the Employee API?

sushil
Автор

take this as a suggestion, when you explain something little complicated try using animated elements inbetween (like ted ed animation videos). that would be better for understanding more than one's body language

trypodstudios
Автор

Can you please the provide the code of Pact Testing in you github portal?

ankushmonga