by Matt Lowrie, Manjusha Parvathaneni, Benjamin Pick, and Jochen Wuttke
Testing
on the Toilet , the Test Certified
Program , and the Google
Test Automation Conference (GTAC) . These efforts resulted in every project
taking ownership of all aspects of testing, such as code
coverage and performance
testing . Testing practices quickly became commonplace throughout the company
and engineers writing tests for their own code became the standard. Today, TEs
carry on this tradition of setting the standard of quality which all products
should achieve.
previous
blog post . What this means for test engineers at Google, is an enhanced
responsibility of being the authority on product excellence. We are expected to
uphold testing standards company-wide, both programmatically and persuasively.
Automate a manual verification process for product release candidates so
developers have more time to respond to potential release-blocking issues.
Design and implement an automated way to track and surface Android battery
usage to developers, so that they know immediately when a new feature will cause
users drained batteries.
Quantify if a regenerated data set used by a product, which contains a
billion entities, is better quality than the data set currently live in
production.
Write an automated test suite that validates if content presented to a user
is of an acceptable quality level based on their interests.
Read an engineering design proposal for a new feature and provide
suggestions about how and where to build in testability.
Investigate correlated stack traces submitted by users through our feedback
tracking system, and search the code base to find the correct owner for
escalation.
Collaborate on determining the root cause of a production outage, then
pinpoint tests that need to be added to prevent similar outages in the future.
Organize a task force to advise teams across the company about best
practices when testing for accessibility.
Over the next few weeks leading up to GTAC ,
we will also post vignettes of actual TEs working on different projects at
Google, to showcase the diversity of the Google Test Engineer role. Stay tuned!
Is there still manual testing tasks which TE's do? Is there still a proportion of manual testing which takes place?
ВідповістиВидалитиHi Steve,
ВидалитиTEs do not perform manual testing. However, manual testing is used by some teams at Google. In this situation, another responsibility of TEs is to formulate and execute a plan for automating as many manual tests as possible.
_Matt
Hi Matt,
ВидалитиWho does perform manual testing if not a TE?
Text also mentions automating a manual verification process, so who is doing the manual verification in that case?
Is this similar to roles like SDET at Microsoft?
ВідповістиВидалитиHow you execute Exploratory testing? Obviously, it is not automate activity.
ВідповістиВидалитиHow do you Quantify the ROI of this group work? Does Google have a PMO where these initiatives needs to be funded?
ВідповістиВидалитиWhich team does the performance test belong to?
ВідповістиВидалити