Google Testers Think on Code Quality

Google’s official test blog often overlooked in the software development world, but brings a critical topic to the agenda: the quality of code remains low. Under this open and ambitious header, Google’s engineers analyze common problems and their origin in software projects.

The decline in code quality according to the discussion on the blog is associated with several basic factors:

-Time edition: The production targets are forced to bypass the quality control steps of the software

• Test deficiency: The insufficient application of automatic and manual testing processes leads to the production environment of errors -Technical debt: Fast solutions create a heavy load on the system over time
• Exip communication: The developer deepens the problems of coordination between test and product teams

Google’s experiences show that the code quality is determined not only with the skills of individual programmers, but also with corporate culture and processes. In particular, the teams who invest in automatic test infrastructure** and adopt test-driven development (TDD) methodology produce codes that are more healthy and easy to maintain.

Such instinctive and experience-specific criticisms represent an important source that promotes continuous improvement of the software industry. Google does such open conversations, helping better software applications be widespread.