Archives
Chapter 5. An Introduction to the Tools
Submitted by noreply@blogger.com (Nat Pryce) on Thu, 21/08/2008 - 13:59.We have put a new chapter of the book online: Chapter 5. An Introduction to the Tools.
What happened to chapter 4? We've moved some chapters around after reading people's comments in the discussion group and will publish chapter 4 as soon as we've finished it and polished it up. We'll put the new table of contents up ASAP.
The trace matrix
Submitted by Karen N. Johnson on Thu, 21/08/2008 - 14:49.I’ve tried blogging about the trace matrix before but the topic irritates me to the point where I have I haven’t been able to write on the topic. That’s a pretty strong reaction to a simple “tool” and my skepticism and concern about the use of this tool remains to this day. My intent in writing about the matrix now is to share my opinion, give exposure to a testing topic, and hopefully hear about other people’s experiences and thoughts about the matrix.
Using WebInject With GroundWork Monitor
Submitted by noreply@blogger.com (Corey Goldberg) on Thu, 21/08/2008 - 16:53.I am the author of WebInject, which is a popular web application/service test tool that also works as a Nagios plugin. GroundWork has an Open Source monitoring system based on Nagios.
I just stumbled across an awesome screencast tutorial from GroundWork called "Using WebInject To Monitor Web Applications And Services". It shows how to install and setup WebInject as a monitoring agent.
Corey Ladas explains Scrum-ban
Submitted by Wayne Allen on Thu, 21/08/2008 - 17:28.Cory has a great post titled: Scrum-ban | Lean Software Engineering. In it he describes how a team can take advantage of kanban within a Scrum environment.
While I am sure that there will be those who insist that Scrum doesn't need to be improved, there are those of us who learned Scrum, practiced Scrum and are aware of it's limitations and want our teams to get even better.
Where Have All the Singletons Gone?
Submitted by noreply@blogger.com (Misko) on Thu, 21/08/2008 - 19:55.In Singletons are Pathological Liars we discussed the problems of having singletons in your code. Let's build on that and answer the question "If I don't have singletons how do I ensure there is only one instance of X and how do I get X to all of the places it is needed?"
TotT: Sleeping != Synchronization
Submitted by noreply@blogger.com (dastels) on Thu, 21/08/2008 - 21:05.Often, threaded tests start out using sleeps to wait for something to happen. This test is trying to verify that DelegateToIntern spawns its work argument into a parallel thread and invokes a callback when it's done.
def testInternMakesCoffee(self):
self.caffeinated = False
def DrinkCoffee(): self.caffeinated = True
DelegateToIntern(work=Intern().MakeCoffee, callback=DrinkCoffee)
self.assertFalse(self.caffeinated, "I watch YouTubework; intern brews")
time.sleep(60) # 1min should be long enough to make coffee, right?
self.assertTrue(self.caffeinated, "Where's mah coffee?!?")
