Some people might wonder what all goes into beta testing, or testing a software product in general. I used to test software (both my own code and other developers') and it's a mix of different things. Sometimes you go down a known path, such as setting a preference with a radio button or checkbox, and clicking Save - then seeing if that preference was really saved in the database or not, and if the preference actually takes effect. Then, you un-set that preference and see if that takes effect.

Going down the not-so-known path involves maybe getting to that preference in a roundabout way, or setting conflicting preferences to see what the behavior is. The thing about testing is that as a developer, you can say that preference is to be accessed by taking Path A, but the end user is always going to find a way to reach it via Path B or even C. The fun part comes in when Path B or C breaks everything :D I do love a good crash.

I haven't broken anything yet. I'm pretty sure that is a testament to the developers who have coded the Keep, but it could be that I just haven't found my Path B yet. I'm going to keep trying.