If you upgrade your framework/php/React version then you need to have tests to makes sure nothing breakes after upgrade!?

Ive never seen a project with tests that completly covers everything and ive been a developer (web) for over 10 years.

Without tests you just upgrade, get down on your knees and pray?

We have a whole suite of tests, unit tests, integration tests, regression tests, etc. - but they can never cover *everything*, and it's a fallacy to think otherwise. We do run them every time we upgrade anything major though for entirely that reason. It's saved us more than a few times.

That's exactly what you do.

Unless you manually test every feature sideways to ensure it still works as expected and have historical documented manual tests to compare results with.

Keep in mind also, a lot of devs confuse code coverage with test coverage, and almost every project I've seen __with testing__ has high code coverage and very little test coverage.

@C0D4 Thats probably why the only company i worked at that had a code coverage requirement had horrible tests. (Most of the code was covered, most of the tests were worse than useless)

Just push your code and have the users test it in production. Any issues they discover, tell them it is a limitation of the product or say it is not part of requirements and you are done!

Eventually the users will stop complaining and are happy when something works part of the time.

This is what our Salesforce dev team does and they have been going strong for years. 😜