Well, I sometimes like to have visual confirmation that something has run overnight when I get in in the morning, especially when there's insufficient logging. In this case, the test automates a process in an Access database which is set up to allow the user to prevent execution in the first 60 seconds. I think the point of having it in the foreground is primarily to make it easy to test that the parameters are correct, so we can see it run when we press the test button.
Oh, there's one other - if something fails, like a database login, and the process stops, waiting for credentials, it's nice to have the windows visible so that we can see what's going on and maybe even correct it so the job can complete. For overnight batches, I actually prefer to have these things run in the foreground just for that reason.