I didn't get into the test method management end of things yesterday because it's a topic on its own. Some main issues are:

1. When does a B test become an A test?
2. Who makes this decision?
3. How are the tests and results stored and administered?

I'm going to take the easy way out and not answer #3. I have some ideas on #1 and #2 though.

One thing I didn't mention yesterday is that B test methods also include methods written for new features. Once the entire feature is completed those test methods can be promoted to A and should always be green. This also follows the XP premise of completed stories -- once the story is done the customer signs off on it and it goes into the finished story pile. The A tests represent the fact that all of these completed stories still work and that makes the customer very happy.

So who makes the promotions? The customer of course. They don't have to know what each test method does but until the whole feature is signed off all of its test methods stay at B.