Setting Up Test and Production Environments
Posted on 2000-05-10
How would you separate code that is not yet fully tested from production code given the following parameters?
- Our company has developed a program using Visual C++ 6.0 called PROJECT
- We use Visual SourceSafe 6.0
- Our team consists of 8 programmers
- Each programmer could be working on maintenance or enhancements to the PROJECT
I was thinking that we could have a test environment and a production environment. When code submitted by a programmer had passed QA, it could be migrated into the production environment. The problem with this is that the resource files (resource.h) aren't very multi-user friendly. Maybe multiple resource files could help this (see TN035). Also, the migration of code from the test to the production environments involves human intervention and that means that errors will occur. For instance, a programmer forgets to put a file back or maybe unknowingly puts back a file that shouldn't be put back (i.e. hasn't been tested).
I'm putting up 500 points for a solution based on real life experience that best meets our needs given the parameters describes above.