Yeah, if you ever get a chance, do try Mozilla Litmus out sometime.
Its actually really easy to use for automated testing, they even include scripts so you can run an entire testing evolution in one command. Plus the more data the QA team has, the faster they can work, every little bit helps the QA team. As does participating in bug triage days and hacking on Aurora and Betas, and hell, some people like nightlies but I don't tend to test them myself. With a full time and very demanding civilian job, and my Army Reserve stuff, I dont have time for the extensive amount of work that working on nightlies entails.
I don't know about Chrome, I don't use it. I honestly use Internet Explorer much more than Chrome (And before the rain of downvotes happens, hear me out, I strongly detest IE. One of the reasons I started volunteering time to Mozilla Quality was because even the sometimes sketchy betas and RCs were better browsers than IE 6, which is what I had. Though IE 10 is pretty good as its blazing fast, at least on Windows 7. It is still definitely not my first choice, but its pretty good. The problems with IE were never really with Trident though, the Trident Engine's actually quite good, it was all the other bullshit like ActiveX and its rather dodgy idea of Microsoft cherry picked standards).
However, my distrust of Microsoft is nothing compared to my distrust of Google and Apple. If I'm going to use WebKit, I use Konqueror, since KHTML is WebKit's daddy. So, given my limited knowledge about Chrome, or WebKit for that matter, I have no idea what Apple's rules in regard to taking on bugs as well as pushing patches to WebKit are (like if anyone besides Apple themselves can do it) or even how Google tests it, since IIRC they have both the Chromium volunteer testing community as well as paid QA Oompa Loompas who work for the Chocolate Factory directly.