March 6th, 2007 | by Allen Hutchison | published in Google Testing
Posted by Allen Hutchison, Engineering Manager and Jay Han, Software Engineer in TestThe testing world has a lot of terms for the activity that we undertake every day. You’ll often hear the words QA, QC, and Test Engineering used interchangeably. While…
February 28th, 2007 | by Allen Hutchison | published in Google Testing
Posted by Mark Striebeck, Engineering Project ManagerYesterday we held a global internal test conference that we called “Testapalooza”.The idea for Testapalooza came out of discussions about how to build a vibrant testing community here at Google. Many…
February 13th, 2007 | by Allen Hutchison | published in Google Testing
Posted by Allen Hutchison, Engineering ManagerGooglers in our Test Engineering group often speak at, and write for, forums on testing all over the world. This week our own Julian Harty has published an interesting article titled “Improving the Accuracy…
February 6th, 2007 | by Allen Hutchison | published in Google Testing
Posted by Harry Robinson, Software Engineer in Test Several readers have commented that our current blog slogan, “Life is too short for manual testing,” implies that we don’t value manual and exploratory testing. In fact, we are big fans of explo…
February 2nd, 2007 | by Michelle Levesque | published in Google Testing
For a class, try having a corresponding set of test methods, where each one describes a responsibility of the object, with the first word implicitly the name of the class under test. For example, in Java: class HtmlLinkRewriterTest … { void testA…
January 31st, 2007 | by Allen Hutchison | published in Google Testing
Posted by Harry Robinson, Software Engineer in Test On Saturday, February 24, the Mountain View Googleplex will offer hospitality, support and free munchies for the first-ever “Developer-Tester/Tester-Developer Summit” — a peer-driven gathering…
January 24th, 2007 | by Michelle Levesque | published in Google Testing
So you’ve learned all about method stubs, mock objects, and fakes. You might be tempted to stub out slow or I/O-dependent built-ins. For example: def Foo(path): if os.path.exists(path): return DoSomething() else: return DoSomethingElse() d…
January 23rd, 2007 | by Allen Hutchison | published in Google Testing
Posted by Allen Hutchison, Engineering ManagerI work in the Test Engineering team, and have always been passionate about sharing my test experiences with others. Last year we organized the first Google Test Automation Conference, where about 150 people…
January 21st, 2007 | by Michelle Levesque | published in Google Testing
We want you to write more tests. Yes, you. You’ve already been told that tests are the safety net that protects you when you need to refactor your code, or when another developer adds features. You even know that tests can help with the design of your …