The Australian Government coat of Arms

Communities of practice

Communities of practice

Consumer-Driven Contract tests** (CDC tests)

Hi all,

In an article I posted in the learning section on the Testing Pyramid (, I ran across the below concept that may be worth exploring further. What do people think? I think it is an excellent idea, if you have an organisation structure that supports sharing of the literal technical contracts at the required level and social or organisational contracts in place with producing teams to support your CDC test…

Consumer-Driven Contract tests (CDC tests) let the consumers drive the implementation of a contract. Using CDC, consumers of an interface write tests that check the interface for all data they need from that interface. The consuming team then publishes these tests so that the publishing team can fetch and execute these tests easily.

1 Like

I think DesignOps and DevOps (although probably not new concepts to be honest) is helping to bridge the understanding between designers and developers much better, as we all know how tricky the handover process can be sometimes.

I have also read articles about how designers can benefit from the API design thinking in how we approach some of the interface design, so that it is more optimized for large and complex testing.

We do need better ways of formalizing the user requirements as part of the development teams writing user stories for their development process and how that is then tested. I think these are very interesting concepts and hopefully something for the GovCMS team to consider incorporating into their design system?