CODE ROUTINE PERFORMANCE PREDICTION USING TEST RESULTS FROM CODE INTEGRATION TOOL

1 . A system for code routine performance prediction, the system comprising:

a code integrator to merge multiple developer committed copies of code for an application and automatically run tests on the merged code, and to gather performance information of a pre-written code routine included in the merged code, wherein the performance information is generated in response to the tests;

a code routine performance manager to receive and store the performance information of the pre-written code routine; and

a code development environment to allow a developer of the application to create and modify a working copy of code for the application, and to receive the performance information of the pre-written code routine when the pre-written code routine is included in the working copy of the code.

2 . The system of claim 1 , wherein the code integrator is further receive, from the code routine performance manager, an indication that the code integrator is to gather performance information of the pre-written code routine.

3 . The system of claim 2 , wherein the code routine performance manager includes an administrator user interface that allows an administrator to determine that the code integrator is to gather performance information of the pre-written code routine, causing the indication.

4 . The system of claim 1 , wherein the code development environment is further to display alerts or warnings to the developer on the fly when the pre-written code routine is included in the working copy of the code or shortly after, wherein the alerts or warning are based on the performance information.

5 . The system of claim 4 , wherein the code development environment is to display the alerts or warnings to the developer as code analysis rule violations.

6 . The system of claim 1 , wherein the code integrator detects at least one use case of how the pre-written code routine is used during the tests, and categorizes the performance information according to the at least one use case.

7 . The system of claim 1 , wherein the code development environment allows the developer to commit the working copy of the code to be merged with the merged code by the code integrator, which causes the code integrator to automatically gather updated performance information of the pre-written code routine based on the updated merged code.

8 . A method for code routine performance prediction, the method comprising:

determining, at a code routine performance manager, that a pre-written code routine should be monitored;

receiving, at a code integrator, an indication that the pre-written code routine should be monitored, wherein the code integrator is to merge multiple developer committed copies of code for an application and automatically run tests on the merged code, and wherein the merged code includes the pre-written code routine;

gathering, at the code integrator, performance information of the pre-written code routine, wherein the performance information is generated in response to the tests;

receiving and storing, at the code routine performance manager, the performance information of the pre-written code routine; and

receiving, at a code development environment, the performance information of the pre-written code routine when the pre-written code routine is included in a working copy of the code.

9 . The method of claim 8 , wherein the code development environment is to allow a developer of the application to create and modify the working copy of code for the application, and wherein the code development environment is further to display alerts or warnings to the developer on the fly when the pre-written code routine is included in the working copy of the code or shortly after, wherein the alerts or warning are based on the performance information.

10 . The method of claim 8 , wherein the determining that the pre-written code routine should be monitored is based on input from an administrator via a user interface of the a code routine performance manager.

11 . The method of claim 8 , wherein the gathering of the performance information of the pre-written code routine includes detecting a test use case of how the pre-written code routine is used during the tests, and categorizing the performance information according to the test use case.

12 . The method of claim 11 , wherein the code development environment is to detect an actual use case of how a developer of the application uses the pre-written code routine in a working copy of the code, and wherein the code development environment is further to display alerts or warnings to the developer on the fly when the actual use case matches the test use case.

13 . A machine-readable storage medium encoded with instructions for code routine performance prediction, the instructions executable by a processor of a system, the instructions comprising:

code routine indicating instructions to indicate to a code integrator that a pre-written code routine should be monitored, wherein the code integrator is to merge multiple developer committed copies of code for an application and automatically run tests on the merged code, and wherein the merged code includes the pre-written code routine;

performance information receiving instructions to receive, from the code integrator, performance information of the pre-written code routine, wherein the performance information is generated in response to the tests; and

performance information providing instructions to provide the performance information to a code development environment to display alerts or warnings to the developer when the pre-written code routine is used.

14 . The machine-readable storage medium of claim 13 , the instructions further comprising administration user interface instructions to allow an administrator to determine that the the pre-written code routine is to be monitored.

15 . The machine-readable storage medium of claim 13 , wherein the performance information includes at least one of the following:

a number of times the pre-written code routine was called during the tests;

an execution time related to at least one of the times the pre-written code routine was called during the tests; and

a use case related to at least one of the times the pre-written code routine was called during the tests.