You write too many tests and open too many bugs

In my experience, many testers tend to identify with certain types of measurements and metrics which on the surface may seem to be desirable to maximize.  These statistics can provide feedback to the tester to indicate that they are making progress and getting something done through the course of their work.  However, when one looks…


Just because you can test it doesn’t mean you should

A wise test lead once said to me, “do as little as possible while still ensuring quality”.  He wasn’t giving me tips on how to be a slacker =)  I think what he wanted to say was there always seems to be more work than there are people so it pays to be as efficient as…


Creativity in Testing

One of the wonderful parts of testing software is that beyond the pure technical aspects of the discipline lie many opportunities for the tester to exercise their creativity in potentially game-changing ways.  Although we work in a field where some of the quality assurance tasks are handed down to us from previous owners (legacy test suites, existing…


Testing In Production

One of the most useful resources for a test engineer dealing with web services is the production environment. This is the live environment that exposes the product to end users. Some of the challenges that the production environment provides us are the following: How do we know that software that works in a developer box…


Object Model Design

Recently I was asked my opinion on creating object models for automated UI software testing – do I prefer LFM or POM? There is no right or wrong answer here – because I own a framework for automating Web UI, I’ll speak to this topic from that perspective. POM (Physical Object Model) style models expose…


Playback Testing Using Log files

Author Vijay Upadya,   Abstract Most testers are familiar with record/playback testing. A variation of this approach is log playback testing. Instead of explicitly recording the user actions using a recorder, this technique simply relies on the information in the log file produced by the system under test to play back the scenario. This…


Old World vs. New World

As software has become increasingly more complex and the demands placed on the test discipline have escalated, it is clear that the legacy approaches for testing software are not always adequate.  Sometimes test teams get caught up in performing the same types of tests and/or taking the same types of approaches not because those things…


Code Inspection for SDETs, Part II

In part I of this series, we looked at some of the benefits of the SDET discipline being fully plugged into the code inspection pipeline.  These benefits include such outcomes as pushing quality upstream and raising SDET awareness of the code that is being tested.  Plus, it’s fun!  J   Now we will share the…


Code Inspection for SDETs, part I

(Note for those unfamiliar with the acronym, SDET stands for Software Design Engineer in Test.  In simple terms an SDET is an engineer who develops code to test software) Code inspection has historically been a “high-yield for low cost” bug-prevention or bug-detection approach.  This is especially true when used as part of formal code review…


Hello world!

We are the senior SDETs (Software Engineer in Test) at Windows Live in Microsoft.  We plan to use this blog to make our voices heard regarding anything and everything test related.  So stay tuned for some interesting articles coming your way.