Next to no unit or local testing. It's a Java monolith multiple teams work on at once and someone several steps removed from our team decided to set maven-sure

Next to no unit or local testing. It's a Java monolith multiple teams work on at once and someone several steps removed from our team decided to set maven-surefire-plugin to fork for every test and not reuse forks in the POM all our projects inherit from in 2014. That causes a ~1s delay per test (even @Ignore'd ones) where they used to take less close to a millisecond, and I've tracked down the "business exception" commits in our projects that came in the months after that disabled the test phase entirely, in order to overcome the build time delay. The rest is history. Now we've got projects where 98% of the tests laying about in the repo are dysfunctional lies. Couple that with using Spring across multiple independently built modules multiple teams commit to and you're looking at one or more hours between committing a change and finding out whether or not the latest build deployed to an environment successfully starts so you can test your change.