Thursday, January 19, 2012

Book Review: Exploratory Software Testing - Tips, tricks, tours and techniques to guide test design

Some of the first testing books I read were written by James Whittaker. His books are laid out in a practical manner making them easy to read and easy to apply. Perfect for someone starting to learn about testing (regardless of their job experience) or wanting to plan individual attacks. I read this book a few years ago after it came out, when I started questioning the way I was testing. The material was new to me and made me ask what is Exploratory Testing and what does touring have to do with it?

Exploratory Software Testing

According to Whittaker (pg. 16) Exploratory Testing (E.T.) is testing where scripts or rigidity have been removed (paraphrasing). Whittaker then explains his terms "E.T. in the small", decisions made where the scope of the testing is small and "E.T. in the large", decisions made when the scope of testing is large (small might be a screen in an application while large is the whole application). At the end of chapter 3 he mentions E.T. can be done in a way that allows test planning and execution to be completed simultaneously which I believe is one of E.T.s most important aspects. Touring (as in a tour guide or sight-seeing) becomes a metaphor for and a way to structure E.T.

There are 8 chapters in the book plus a number of appendices. In the first several chapters Whittaker discusses what he sees as the case for software quality (possibly redundant in a book for testers), introduces E.T. and explains how he uses it, in the small and the large. The next 4 or so chapters cover tours he and others have come up with. The last chapter is about how Whittaker sees the future of testing or at least how he did at the time of publishing.

The first appendix, A, is one of the most important parts of the book: building a successful career in software testing. Whittaker talks about how he got into testing and gives some advice on "getting over the hump" to be a better tester. Its short but worth reading. The rest of the appendices are old blog posts from his Microsoft days.

As a beginner (at the time I first read it) I found this book much more valuable than I do now several years later. I know more about E.T. and how it is an approach to testing that can but doesn't necessarily include tours or scripts. It isn't just manual testing either. For reference Michael Bolton (the testing expert) has some good posts in what E.T. is not:
Unfortunately this book does not do a proper job explaining E.T. in a way that one can use it, aside from following the tour metaphor. In fact after reading it again this book seems to say to the reader: these tours are the best, don't you agree? It’s important to understand Exploratory Testing is about the way you work, and the extent to which test design, test execution, and learning support and reinforce each other.

Years after reading Exploratory Software Testing I found out Exploratory Testing wasn't an original Whittaker concept rather it was conceived by James Bach. Bach has a different and more expansive idea of what constitutes Exploratory Testing. I could be wrong on this but I believe Bach coined the term but it was first published by Cem Kaner. Regardless I find it a little odd that Whittaker uses a limited definition without reference to either Bach or Kaner and their work. 

This book offers a very limited understanding of Exploratory Testing. It isn't as practical as Whittaker's previous because you can't apply the teachings very well without fully understanding what E.T. is and how tours fit in. However if you only want ideas on how Microsoft’s testers used the touring metaphor to “perform” exploratory testing then you’ll get four chapters of information otherwise Exploratory Software Testing is worth skipping.

Monday, January 16, 2012

How to Setup Transactional Replication on SQL Server 2008

Recently I've been testing server-side, mainly database stuff and have become familiar with replication on SQL Server 2008.

Thursday, January 5, 2012

My Tester's Commitments

Dear Development Team,

My job is to help you look good. My job is to support you as you create quality; to ease that burden instead of adding to it. In that spirit, I make the following commitments to you.

Sincerely,
Chris

  1. I provide a service. You are an important client of that service. I am not satisfied unless you are satisfied.
  2. I am not the gatekeeper of quality. I don’t “own” quality. Shipping a good product is a goal shared by all of us.
  3. I will test your code as soon as I can after you deliver it to me. I know that you need my test results quickly (especially for fixes and new features).
  4. I will strive to test in a way that allows you to be fully productive
  5. I’ll make every reasonable effort to test, even if I have only partial information about the product.
  6. I will learn the product quickly, and make use of that knowledge to test more cleverly.
  7. I will test important things first, and try to find important problems. (I will also report things you might consider unimportant, just in case they turn out to be important after all, but I will strive to spend less time on those.)
  8. I will strive to test in the interests of everyone whose opinions matter, including you, so that you can make better decisions about the product.
  9. I will write clear, concise, thoughtful, and respectful problem reports. (I may make suggestions about design, but I will never presume to be the designer.)
  10. I will let you know how I’m testing, and invite your comments. And I will confer with you about little things you can do to make the product much easier to test.
  11. I invite your special requests, such as if you need me to spot check something for you, help you document something, or run a special kind of test.
  12. I will not carelessly waste your time.

Thursday, December 29, 2011

About the Author

Hi my name is Chris Kenst; I'm a software tester, scuba diver and blogger. Cool, huh?

I started blogging for fun years ago and its since turned into a way to express myself and coalesce my thoughts. Only recently have I felt the confidence to step up and blog about testing. A majority of my blogging occurs at My Technology Fetish and at Search N Recovery. My hope is to write thoughtful enough that in the future I have the privilege to do some guest posts / blogging elsewhere. I understand that blogging <> journalism. =) Occasionally I do reviews of books including those provided to me for free by O'Reilly's Blogging Program. Of those books I review that I get for free I make note of it so readers can tell if I have reason to be biased.

I review for the O'Reilly Blogger Review Program

I'm a soon to be Scuba Instructor for PADI and have been teaching / helping teach for over 4 years. A big believer in teaching from experience, from things you know and learn, I try to dive on a weekly basis - outside of classes. I'm always looking for a good diving adventure and hope sometime soon to dive outside the U.S. and Mexico.

I'm a technophile. That means I love (new) technology, always have. I started as a Quality Assurance (QA) Analyst outside of college but only in the last few years have I begun to challenge the conventional wisdom on testing - testers don't belong doing QA. It just doesn't work. A follower of the context-driven school of software testing, I enjoy learning rapidly and applying that knowledge to investigate new systems and technologies. I'm interested in becoming an "expert" software tester and contributing what I can to the community. Someday soon I hope to start a local weekend testers / test dojo to meet other like-minded individuals.

So that's me, your author. I hope you take something of value from this blog. If you do, please share your story here in a comment.

Wednesday, December 28, 2011

Watch Videos (YouTube, Hulu, Amazon) on your Xbox 360

For years Xbox 360 users with a Gold Xbox Live membership and a subscription to Netflix could stream movies to their TV. But what about streaming from Amazon, Hulu and YouTube? If you just want Amazon they have a work around that will allow you to stream from your PC to your Xbox here.

What if you want to watch YouTube videos and free movies? How about Hulu, not Hulu Plus, which has many of your favorite shows?