Great video, I recommend that you fill the space you're talking with cushion or objects. The room around you has quite alot of reverb that affects your sound quality.
@QAUnderground
3 жыл бұрын
Thanks for the tips!
@rahulanwekar3961
2 жыл бұрын
Very informative Video, Can you please create a Video with CICD implementation like trigger the webhook whenever contract gets created or updated
@PalBose
Жыл бұрын
Very good explanation. Wish there was no background music throughout though.
@QAUnderground
Жыл бұрын
Thank you for your feedback! I'm glad you found the explanation helpful. I understand that background music can be distracting for some viewers and it's great that you let us know your preference. We'll keep your feedback in mind for future videos and strive to create content that is informative and enjoyable for everyone.
@skipodap1
3 жыл бұрын
Great video! thanks much
@QAUnderground
Жыл бұрын
Thank you for the kind words!
@flute_nayak
3 жыл бұрын
Nice explanation
@QAUnderground
3 жыл бұрын
Thank You!
@tabithawagnerphotographyan2254
2 жыл бұрын
You’re very good
@QAUnderground
2 жыл бұрын
Oh thank you
@shardqa
2 жыл бұрын
Very well explained.
@QAUnderground
Жыл бұрын
Glad it was helpful!
@bollineniharitha555
3 жыл бұрын
Which role we are playing here consumer or provider and what are the files to be added when we are doing contract testing
@QAUnderground
3 жыл бұрын
Hi @Bollineni Haritha, Thanks for your question! You are playing both roles, With contract testing you are creating both consumer tests and provider tests. The consumer tests are created using a mock'd provider and the provider tests are created using the generated contract by the consumer (the contract we uploaded to the PACT Broker). The files need for testing would be the generated contract from the PACT Broker. I hope this helps clarify things!
@ElvenSpellmaker
4 жыл бұрын
I'm really confused which environment the Provider is run in, if you're meant to run Contract tests _before_ deploying then where is the API URL pointing to? You can't point to a dev environment because that'll have the old code.
@QAUnderground
4 жыл бұрын
Hi! Thats a great question! Where the Provider verification is ran depends on how your environments are setup. For example usually, teams may have a dev, QA, stage, PreProd, and Prod, or dev, stage, and Prod. The Provider verification in those scenarios can be ran in either stage or preprod. If that scenario doesn't fit yours, you can always run the Provider against a local instance of the API that contains the changes as well.
@ElvenSpellmaker
4 жыл бұрын
@@QAUnderground Thanks for the reply! Yeah I was discussing this with my team earlier and was wondering if for the first environment you'd spin up the API with various services mocked (such as CosmosDB) locally on the Build Agent using the already built container and then use that for the base app. Taking a simple Build --> Dev --> Prod set-up, you'd: Build Docker Container and run Unit, Component tests. Pre-deploy for Dev spin up the built container for PACT tests, and then, Pre-deploy to Prod use the Dev API for PACT tests.
@carlconn3090
3 жыл бұрын
great video, next time sit closer the microphone.
@QAUnderground
Жыл бұрын
Thanks for the feedback!
@pramodmallick5746
4 жыл бұрын
can u share the code snippet in github please
@QAUnderground
4 жыл бұрын
That's great feedback! I will work to get those code snippets up into GitHub. Thanks!
@Agnostic2008
Жыл бұрын
echo echo echo :)
@QAUnderground
Жыл бұрын
Why was the echo feeling blue? Because it was repeating itself over and over! Thanks for checking out the video, hope you join the QA Underground community!!
Пікірлер: 24