I've got a few ideas for things I'd like to work on and submit to core, but getting my head wrapped around the testing process for rails itself (as opposed to an rails app) is proving slower than I had wanted. Specifically, I've noticed a) that testing works inconsistently if I'm working on JUST RAILS in it's own directory vs. working on rails in vendor/rails/ from within an established application, and b) I'm unsure of how to turn on logging while running unit tests on rails itself - I'd like to see the sql flying by to make sure my tests and changes are doing what I think they're doing.
I've read through various blog and email posts, and have made some progress, but I have yet to find anything really comprehensive. Josh Susser's "Laying Tracks" pdf was a simple-but-great intro to the *process* of contributing, but now I need to get down into the details of discovering the tools at my disposal during that process.
Any pointers to things that might assist me here (or answers to my above questions)?