Were there established standards or goals for test coverage in your project?

In most Java projects, standards for test coverage levels are indeed established, often ranging from 70% to 90%. This helps maintain code quality and reduce the number of bugs. For example, you can configure a CI/CD system that will reject the build if coverage falls below a specified threshold.

However, it is important to understand that a high coverage percentage does not always guarantee the quality of tests — it is better to focus on coverage of critical parts of the logic and write meaningful tests, rather than just increasing the numbers.