I'm a fan of Dave's stuff, but BT has some great counter-points here. Good vid I would think Contract Testing has a lot of merit in an ideal situation, where either automation is getting written along with the implementation of a new app or microservice, or in the more common scenario where QA is being brought on mid-development, infinite wealth and hours to parse out what belongs to whom and where to cordon off tests and expectations. So we write E2E!! Because its the path of least resistance to take stress off manual QA testing, and get results deliverable to stakeholders. 🤷♂ I'll keep Contract Testing as a wonderful, unreachable dream for now 😂 also, I've seen Try and Catch in out-in-the-wild examples here and there and no sir, I don't like it. I'll stick to if statements, ty
Thanks for the thoughtful comment. In general, I would agree and avoid using try-catch blocks in integration tests. As we explored in the video, integration tests are meant to verify the behavior of your system as a whole, including interactions between components and external dependencies. When an exception occurs in an integration test, it’s a sign of a deeper issue, for example a misconfigured dependency or a defect in the system.
BoomerTester clearly knows what he's talking about.
Thanks for the kind comment.
Very informative. BoomerTester has a very thorough knowledge and I appreciate his friendly tone even when giving a critical review of someone else.
Thanks for watching!
Great video! You make the contact funny and information all at once.
Glad you enjoyed it!
I got beard envy BoomerTester
Best advice I can give you is... don't shave? :)
Good info! Thanks for posting.
You bet!
My code has been propagating problems for year! This vid is super informative
Only thing worse than that is a ram emergency.
I'm a fan of Dave's stuff, but BT has some great counter-points here. Good vid
I would think Contract Testing has a lot of merit in an ideal situation, where either automation is getting written along with the implementation of a new app or microservice, or in the more common scenario where QA is being brought on mid-development, infinite wealth and hours to parse out what belongs to whom and where to cordon off tests and expectations. So we write E2E!! Because its the path of least resistance to take stress off manual QA testing, and get results deliverable to stakeholders. 🤷♂ I'll keep Contract Testing as a wonderful, unreachable dream for now 😂
also, I've seen Try and Catch in out-in-the-wild examples here and there and no sir, I don't like it. I'll stick to if statements, ty
Thanks for the thoughtful comment. In general, I would agree and avoid using try-catch blocks in integration tests. As we explored in the video, integration tests are meant to verify the behavior of your system as a whole, including interactions between components and external dependencies. When an exception occurs in an integration test, it’s a sign of a deeper issue, for example a misconfigured dependency or a defect in the system.
🔥🔥🔥🔥
🧑🚒🧑🚒🧑🚒🧑🚒
Lots of great information
Glad it was helpful!
Boomer is brilliant
I wish but thank you for the compliment.
First comment! I win! 🎉🥳🎉🥳
Congrats, you now have ligma.
Dangit... I missed being through first comment lol
You snooze you lose. :) Thanks for watching though.