Google Views on QA and Engineering Productivity

Google, like most software companies, started small and its development staff were involved in both building and testing code. But as with any growing company, more specialised roles soon started to appear in order to eliminate bottlenecks and to ensure quality in the development process.

Google Views on QA and Engineering Productivity

Image Credit

Automated Testing

Due to its fast growth, Google at first attempted to automate its testing processes. This helped avoid the bottlenecks created by manual testing and allowed the company to release products more quickly.

This also led to the development of more distinct testing roles: test engineers concentrated on what needed testing, and software engineers focussed on building the frameworks and tools needed to automate testing.

As with a mobile software testing service, this division ultimately led to better and more efficient testing regimes. Partly this is because test engineers were able to develop a better understanding of the products they were working with.

In addition, software engineers could concentrate on building an array of testing tools that could be used across a range of different products and reduce the number of manual tasks. Many of these have since been made available to the wider software community, and mobile software testing services have made a contribution to the success of the industry as a whole.

Reduced Testing Time

By making these changes the company was able to reduce testing time. However, it found that overall development time didn’t reduce. The company found an unintended consequence in that the software engineers ended up building tools to accelerate other areas of the software development process, including measuring developer productivity.

As their role expanded beyond the mobile software testing service, Google allowed the engineers to choose a more appropriate title, and they became ‘Software Engineer, Tools and Infrastructure’ to reflect their wider role.

Software testing has become big business, so it’s easy to see why Google’s approach is an attractive one. By helping to shorten testing times and at the same time improve the overall effectiveness of development teams, it benefits the entire process.

It’s important that testing isn’t seen simply as something that happens at the end of the development process before a product is released. It should be a fully integrated part of the software life cycle and can ensure that a better product is delivered.

Both comments and pings are currently closed.

Comments are closed.