This post is one of multiple FUDCon Tempe hackfest liveblogs. (Not sure what FUDCon is? Read this post first.)

My last hackfest liveblog for the evening was with Adam Williamson, who's following up on some drat ideas from the test mailing list and making them into reality this weekend.

Adam: I'm running a hackfest on package-specific test cases, which is a test case that tests your package.

Why should I do this? Why would I care?

So that when you push an update and people test your update, they will be testing the right things. They won't just be saying "oh, I installed it and nothing broke, so I guess it's good." Instead, they'll be able to say "I installed it, I ran your test case, so I know the package does what it's supposed to do, and it's good."

All right. What do I do?

We have an SOP on how to [write package-specific test cases] on the wiki.

Whoa, long page. It looks like it would take a long time to work through.

10 minutes of your time. Please come do it.

I will be floating around [during FUDCon]. If you maintain a package, or if you just know how to test a package, come to me and spend 10 minutes, and we'll make a test case for the package, and that will live on forever and be useful for years to come.

Why did you start doing package-specific test cases? Was this in response to something that happened?

I believe it was the... packagekit update... we pushed out the update and people said "well, you know, I installed it and it worked okay." And then we found out that update notification was broken.

Right, that was a big deal - it meant a lot of users were stuck in limbo-land with no updates and didn't know it, and we had to run around and say to everyone "updates are broken! updates are broken!" which wasn't fun for anyone.

And we didn't have a test case that said "you have to test update notification," so we never knew it was broken. But if we had a test case that said "you have to test update notification," that will never happen again.

Okay, so if I'm at FUDCon, I can come find you and do this with you in person in 10 minutes. What if I'm not in Tempe, or I'm too busy here and can't find you until afterwards?

You can email me, you can contact the test mailing list. Come on IRC, I'm always on IRC, I'm adamw and I'm always happy to help people write test cases. This is a baby little project and we need to grow it!