Method and system for enforcing version control

1. A system for controlling code in a code management system comprising:

an interface for receiving a command to execute code;

controlled storage for storing the code loaded from the code management system;

a processor for executing the code in the controlled storage;

a logger for logging results of the code;

a garbage collector for removing the code from the controlled storage after execution of the code; and

a recorder for recording a list of associated code components as each code component is loaded into the controlled storage, such that linked components may be pre-loaded into the controlled storage on subsequent execution of the code.

2. The system of claim 1 wherein the code comprises test code and program code.

3. The system of claim 2 wherein the test code comprises a first test component linking to at least one other test component, and wherein one of the test components comprises a command to execute the program code.

4. The system of claim 2 wherein the program code comprises a first program component linking to at least one other program component.

5. The system of claim 1 further comprising a code loader for loading code into the controlled storage.

6. The system of claim 5 wherein the code loader retrieves each component from code management storage on execution of that component.

7. The system of claim 1 wherein the garbage collector removes individual code components from the controlled storage after execution of the code and the logged results remain in the controlled storage.

8. The system of claim 1 , wherein further the code components are pre-loaded into the controlled storage in a sequence in which they are used in code execution.

9. The system of claim 8 further comprising associating the sequence with a selected one of a user and a test command.

10. A method for controlling code in a code management system comprising:

receiving from a command to execute code;

retrieving the code from code management storage and reloading at least a portion of the code into controlled storage in a sequence in which they are used in code execution;

executing the code in the controlled storage;

logging results of the executing code; and

removing the code from the controlled storage upon execution of the code.

11. The method of claim 10 wherein the code comprises test code and program code.

12. The method of claim 11 further comprising:

receiving from the test code a command to execute program code;

retrieving test code and program code from the code management storage and loading the test code and program code into the controlled storage;

executing the test code and the program code in the controlled storage; and

removing both the program code and test code from the controlled storage.

13. The method of claim 12 further comprising:

the test code comprising a first test component linking to at least one other test component, one of the test components executing the program code; and

the program code comprising a first program component linking to at least one other program component.

14. The method of claim 13 further comprising retrieving each component from code management storage on execution of that component.

15. The method of claim 13 wherein the individual components are removed after execution of the code and the logged results remain in the controlled storage.

16. The method of claim 13 further comprising:

recording a list of components associated with the code and storing the list for use in preloading the components on subsequent execution of the code.

17. The method of claim 16 further comprising retrieving the components in the sequence in which they are used.

18. The method of claim 17 further comprising associating the sequence with a user.

19. A system for controlling code in a code management system comprising:

an interface for receiving a command from a user to execute code;

controlled storage for temporarily storing the code from the code management system, wherein components of the code are pre-loaded into the controlled storage in a sequence in which they are used in code execution;

a processor for executing the code in the controlled storage;

a logger for logging results of the code in the controlled storage; and

a garbage collector for removing the code from the controlled storage after execution of the code while leaving the logged results in the controlled storage.