Comments on: Test environment http://itknowledgeexchange.techtarget.com/itanswers/test-environment-2/ Wed, 19 Jun 2013 19:19:38 +0000 hourly 1 By: sunsetrider http://itknowledgeexchange.techtarget.com/itanswers/test-environment-2/#comment-101464 sunsetrider Tue, 10 Jan 2012 16:02:37 +0000 #comment-101464 I would recommend that you create a ‘standard’ test system for each environment (this will probably create some overlap), but you can use this test system for future changes. Also, you will not need to retain ‘experts’ for this system, since your test cases and resullts should be the same each time. You can always develop new test cases when new functionality is added.

When you are ready to test changes; load your current test system, compare the results with the previous test system (they should be the same, since no changes were introduced); implement your current set of changes; run the test system (adding additional test cases for new functionality) and compare with previous test system output. This is a relatively simple process to ensure only those functions that were modified have been changed.

I prefer this technique, rather than copying every db 10th record and turning this into our ‘test’ system. Using the above example, I have a high confidence level that the changes implement will be adequately tested, and we will not have screwed up something else.

]]>