Ask HN: How to make sure developers do not change public API?

2 pointsjulbaxter3 comments

How do you make sure developers in your team or in the company do not change the public API of the application when it is not planned? Yes you can write unit-tests, but they can also change/fix the unit-tests to have a green build.

View on HN

In addition to normal unit tests, you can write tests whose job is a warning to a human being "you are about to do something dangerous, are you sure?" With a way to say "yes I meant to do that" when necessary.

Whereas unit tests test the product, these tests are oriented towards the development process.

https://codewithoutrules.com/2016/03/01/process-reminders/ has an example.

So basically, you don't trust your developers to do their job properly. Do I understand that correctly?

It is not a question of trust. I include myself in the "developers". I am talking about removing human errors and putting automation.

Reply on news.ycombinator.com