This is where continuous integration comes in very handy. Generally the simplest form of continuous integration is automatically building and executing unit tests every time code is checked in. This is to reduce the amount of time it takes to discover possible build breaks or code level defects.
Similarly, many people extend continuous integration to include deployment and execution of all automated tests. This again, gives you early warning of any potential deployment bugs and functional issues.
Setting up an automated continuous integration environment with automated deployment and functional test cases is a lot of work, so in the case where that is not an option, or too much of an investment and you are relying on a fully manual validation then you probably want to include deployment testing as part of your normal test pass.
I'm confused by your comment about doubling up testing. Do you normally deploy for testing purposes using some other method than this RIP? If so, why? As far as I understand based on your question the order of events would be as follows:
- Team creates RIP
- RIP Deployed to test PCs
- Deployment validation (which most likely has a lot of overlap with functional tests anyways)
- Functional testing
If that doesn't sound right, please clarify your question.