That said, I much prefer hex-editing with Emacs to using a combination of xxd and vim.
I've tinkered around with hacks that put shells in Vim windows but it wasn't really satisfactory.
Screen is basically a terminal multiplexer. This would work a little differently if you were using gVim instead of Vim (from within the same screen session that you're sending the test suite command to). If you were using gVim you'd need to use a named screen session (the -S option) and send the screen command to the named session (and possible have logic in the Vim/gVim function to start a named session if one doesn't already exist). Then you'd need a separate terminal window attached to that screen session to view the test suite output.
Do a search for vim and REPL or SLIME for articles like this: http://technotales.wordpress.com/2007/10/03/like-slime-for-v...
These articles use the vim+screen combo to send commands to an interpreter, but you can use the same concepts to send your test suite to a screen session.
I try to keep my vim pretty vanilla outside of font and color preferences because I spent most of college jumping from one computer to the next and I didn't want to get used to relying on anything that wouldn't be there next week.
That said vim + screen kinda translates to vim + 'my entire computer' which doesn't prove my point really but also doesn't say much about the completeness of vim as an environment.