31:34 I dont see relation here. CDD (Contract driven development) relies on the contract (API spec) created/edited before you even start to develop/change the service. In perfect implementation you create a an API spec or change in it and tests (both "happy paths" and "bad paths") should be generated from this spec. And now developer should adapt his code to the spec . If he does not do that - for example he pushes the branch just with an updated spec, nothing else, to repository - then CI pipeline wich will run those newly generated tests against service built from "old"/not-adapted code will fail. So importing spec (OpenAPI preferably), building a mocks from it and generating tests from it are key features here. Recreating the API by recording (along with exporting spec in OpenAPI format) would be usefull only once - when you want to build your spec from scratch for already existing system.
Oleg is making me a better java developer everyday, thanks Devoxx.
Introductory talk for junior-level developers
31:34 I dont see relation here. CDD (Contract driven development) relies on the contract (API spec) created/edited before you even start to develop/change the service. In perfect implementation you create a an API spec or change in it and tests (both "happy paths" and "bad paths") should be generated from this spec. And now developer should adapt his code to the spec . If he does not do that - for example he pushes the branch just with an updated spec, nothing else, to repository - then CI pipeline wich will run those newly generated tests against service built from "old"/not-adapted code will fail. So importing spec (OpenAPI preferably), building a mocks from it and generating tests from it are key features here. Recreating the API by recording (along with exporting spec in OpenAPI format) would be usefull only once - when you want to build your spec from scratch for already existing system.