software testing

The article has a good discussion of why we need the whole team, developers and all testers, to be engaged in making automation work. We need to make sure it doesn't become the domain of "that person" because then our entire testing effort doesn't benefit as much.

As someone fairly new (at least from an employment standpoint) to the world of testing, it is clear that there is healthy debate in the profession about scripted versus unscripted testing. In Elizabeth's article, she uses checking (scripted) versus "testing" (largely unscripted) and describes some experiences she has had with both testing philosophies. It's also fairly clear, and Elizabeth points this out, that the polarization of both camps does a disservice to both groups. I've become increasingly leery these days when I hear "Either/Or" arguments that allow for little to no compromise.

A great article by Scott Barber defining some elements of testing that should be changed. I still feel like I'm getting my feet wet, but I can already see some of these elements (including in myself) in the profession. Not that they have been recognized, it's time to move past them. In summary here are the 10 elements, but I encourage you to check the article out in its entirety.

Subscribe to RSS - software testing
© 2011 Brett Hinton. Drupal theme by Kiwi Themes.