[Introduction to contract testing - Part 1] The problem with end-to-end integrated tests

Welcome to part one of our four-part introduction to contract testing series.

WHAT YOU WILL LEARN:
1. The state of the industry's release process
2. The challenges teams face maintaining end-to-end integrated tests
3. Why integrated tests scale poorly with team and system size

JUMP TO
0:00 - What is integration testing and end-to-end integrated tests?
01:06 - Problems with end-to-end integrated tests
03:57 - State of the industry CI/CD pipeline
04:51 - Integration tests scaling properties

GIVE PACTFLOW A TRY

ABOUT

[Bercilakdehautdesert-ytgd]

Regarding Postman, I've had success in the past drawing fresh data into variables, for example exchange rates and product prices, using a pre-execution script. This leads the tests to be less brittle. I'm just starting to look at Pact.

[gxferreira]

The chart at the end of the video is amazing, however, the youtube suggestions (next video and channel) really hinder it. Especially when you have all the curves on it.

[bmotwqg]

one thing I am not able to figure out
I understand that one usage of pact is to support the consumer development even if the backend is not ready .. and this will be through the mock service.
however, i can see from the tutorial is the that the mock service is only run in order to execute the consumer test against it.
and once the test is finished it is brought down again (stopped)
hence how can the mock server be up with this mock service running during the consumer development??
kindly let me know if I anything is wrong from the above.

[alexanderpodkopaev]

I was always thinking that the wrong test data issue has nothing to do with particularly end-to-end testing.
'Garbage in - garbage out' principle works disregarding test type, be it unit, load or integration.
So, listing data issues as a CON for end-to-end testing looks like confusing cause and effect.