I can't stress strongly enough how you should have separate accounts
in test and development environments. I was lazy with it and got bit once. I
was using the same AppPoolID in test and production a few years ago to test an
upgrade. I also restored my WSS v2 Config database (big no-no). When I ran the
software I was installing it asked for my SQL server, so I gave it the SQL
server in my test environment. Unfortunately it was only using that to get my
Config, where it found the name of my production SQL box and proceeded to do the
upgrade on it instead. Of course there were about four things wrong with that
situation, but had I been using an account in my test environment that had no
permissions in production it could have been prevented.