Some third party / open source libraries have a cavalier attitude to breaking changes, and upgrading those dependencies can break my code.
Could Diffblue Cover be used to generate tests to cover my “contract” with these third parties so that a breaking change in the dependency leads to a test failure in my project?
I guess this is partly achievable if I encapsulate my dependency in my own adapter layer but it would be reassuring for Cover to have a deeper understanding of the dependency itself and identify any edge case behaviour that I happen to be depending on.