RPG – that’s a toughie! However, a quick Google (google is YOUR friend, too) found a Microsoft link that should help:
The code checking tool included in Visual is dynamite – but I don’t know if it will do RPG.
As to best practices: Keep source code control within the QA department, along with the modification request software (don’t use the Microsoft one here – if you can’t afford the investment in a commercial one, try CVS or
Subversion). Set out a strict process for check-in for test, and if possible, keep an entirely different [equivalent of cvs-root] for check-in for testing and check-in for move to production. QA should have absolute control of the latter – no one else has access.
Be sure to define your controlable artifacts to include as much as possible – design drawings, requirements, test code, tools as well as source code and follow the same change management process for all artifacts.
Hope this helps. Good luck!
This is my first time using this forum, but I will try. I have found that if you go to this website, http://www.qaforums.com/. That QA Forums seems to have a variety of Quality Assurance people that will be happy to help you get this department set up properly. Just remember that all time spent on testing the quality will help the end user to be happier with your product. And in the end help your bottom line because of their satisfaction. I hope this site is able to help you. Good Luck!