Archives
Business rules for handling overdue library books ... a century overdue!
Submitted by Erik Petersen on Wed, 12/03/2008 - 13:09. acceptance testingIn Finland, there is a religious annual that comes out (obviously) every year, collecting 12 monthly magazines into a bound volume. The 116th edition of Vartija was printed in 2004 with the theme, “Doctrines Challenged by the Faith of Common Man”. I guess most Finnish libraries stock it, and Finns are regular readers borrowing 3 books every 2 months. If we have faith in common man, we can presume that they also return them. Unless their great grandchildren return them a little overdue….
Ad-hoc vs. Exploratory Testing
Submitted by Antony Marcano on Wed, 12/03/2008 - 13:47. exploratory testingAd-hoc testing in comparison to exploratory testing is like the difference between someone who only runs when they are late for their train and a professional athlete that competes in 100 metre sprints.
The person that runs for the bus simply runs instinctively - yet the professional athlete, with the sports-science consultant, studies ways to optimise their running, trains and practices to improve both their power and technique (such as with the Pose method).
The minute you even read about exploratory testing, you are stepping away from ad-hoc (having a play) testing. The mere fact that you appreciate that it isn't only instinctive but realise that there is a method to what may at a glance seem easy to do is the day you are no longer just "having a play".
Four Ages of Testing
Submitted by Brian Marick on Wed, 12/03/2008 - 14:30.DbFit 1.0 Released: support for in/out parameters, blank-padded strings and quer
Submitted by webmaster@testdriven.com (News) on Wed, 12/03/2008 - 16:03.Performance: art and/or technique(s)?
Submitted by Ainars Galvans on Wed, 12/03/2008 - 16:32. performance testingMore From "Play As Exploratory Learning"
Submitted by noreply@blogger.com (Michael) on Wed, 12/03/2008 - 19:21.Cost-Benefit Analysis of a Test
Submitted by noreply@blogger.com (Patrick Copeland) on Thu, 13/03/2008 - 02:02.Posted by Antoine Picard
We have become test hoarders. Our focus on test-driven development, developer testing and other testing practices has allowed us to accumulate a large collection of tests of various types and sizes. Although this is valiant and beneficial, it is too easy to forget that each test, whether a unit test or a manual test has a cost as well. This cost should be balanced against the benefits of the test when deciding whether a test should be deleted or whether it should be written in the first place.
Let's start with the benefits of a test. It is all too easy to think that the benefits of a test are to increase coverage or to satisfy an artificial policy set by the Test Certified program. Not so. Although it is difficult to measure for an individual test, its benefits are the number of bugs that it kept from reaching production.
Register for CITCON Denver
Submitted by Developer Testing on Thu, 13/03/2008 - 02:34.Watching movies to find localization bugs
Submitted by noreply@blogger.com (Patrick Copeland) on Thu, 13/03/2008 - 05:50.In December, Google Pack shipped 10 new languages in 10 new countries/regions including China Pack. This was in addition to the 30 languages Pack was all ready available in. Localization testing for these 10 languages is not trivial. The testing needs to be done very quickly by experts in the language who may not have seen the application before. Localization testing (LQA) can also be costly since it requires multiple external vendors, and the LQA schedule is highly sensitive to changes in the product schedule.
