Method and apparatus for developer code risk assessment
One example method involves generating executable code, mapping a testcase to the executable code, where the testcase is associated with a test, identifying a dependent code component, notifying an owner of the dependent code component of a relation between the dependent code component and the executable code, initiating a test of the executable code, and resolving any problems that are identified during the test of the executable code. In this example, the entire method is performed during a code development phase.
1. A method for generating application executable code by multiple developer clients including a first developer client and a second developer client, the method comprising:
generating executable code by the first developer client, wherein the executable code corresponds to a first part of the application executable code;
mapping a testcase to the executable code, the testcase being associated with a test;
identifying a dependent code component based on the mapping of the testcase to the executable code, wherein the dependent code component is associated with executable code generated by a second developer client, wherein the dependent code component generated by the second developer client corresponds to a different part of the application executable code and is mapped to the testcase;
notifying the second developer client of the dependent code component of a relation between the dependent code component and the executable code generated by the first developer client;
initiating a test of the executable code generated by the first developer client; and
identifying a problem, if any, between the executable code generated by the first developer client and the dependent code component generated by the second developer client, wherein the test allows the problem to be resolved before the application executable code is released.
2. The method as recited in claim 1 , wherein the method is performed prior to submission of the executable code for release.
3. The method as recited in claim 1 , wherein the test of the executable code generated by the first developer chart also tests the dependent code component.
4. The method as recited in claim 1 , wherein a map of the test to the executable code generated by the first developer client is part of a path: usecase→component>testcases→code line executed.
5. The method as recited in claim 1 , wherein the executable code generated by the first developer client is a line of executable code.
6. The method as recited in claim 1 , wherein the test is verified as not being a duplicate of an existing test.
7. The method as recited in claim 1 , wherein the dependent code component generated by the second client developer is dependent upon the executable code generated by the first developer client.
8. The method as recited in claim 1 , further comprising resolving the problem in the executable code generated by the first developer client that was identified during the test or in the dependent code component.
9. The method as recited in claim 8 , further comprising submitting the application executable code for release after the problem has been resolved.
10. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, perform a method for generating application executable code by the multiple developer client including a first developer client and a second developer client, the method comprising:
generated executable code by the first developer client, wherein the executable code corresponds to a first part of the application executable code;
mapping a testcase to the executable code generated by the first developer client, the testcase being associated with a test;
identifying a dependent code component based on the mapping of the testcase to the executable code, wherein the dependent code component is associated with executable code generated by a second developer client, wherein the dependent code component generated by the second developer client corresponds to a different part of the application executable code and is mapped to the testcase;
notifying the second developer client of the dependent code component of a relation between the dependent code component and the executable code generated by the first developer client;
initiating a test of the executable code generated by the first developer client; and
identifying a problem, if any, between the executable code generated by the first developer client and the dependent code component generated by the second developer client, wherein the test allows the problem to be resolved before the application executable code is released.
11. The non-transitory storage medium as recited in claim 10 , wherein the operations are performed prior to submission of the executable code for release.
12. The non-transitory storage medium as recited in claim 10 , wherein the test of the executable code generated by the first developer client also tests the dependent code component.
13. The non-transitory storage medium as recited in claim 10 , wherein a map of the test to the executable code generated by the first developer client is part of a path: usecase→component>testcases→code line executed.
14. The non-transitory storage medium as recited in claim 10 , wherein the executable code generated by the first developer client is a line of executable code.
15. The non-transitory storage medium as recited in claim 10 , wherein the test is verified as not being a duplicate of an existing test.
16. The non-transitory storage medium as recited in claim 10 , wherein the dependent code component generated by the second client developer is dependent upon the executable code generated by the first developer client.
17. The non-transitory storage medium as recited in claim 10 , wherein the operations further comprise resolving the problem in the executable code generated by the first developer client or in the dependent code component that was identified during the test.
18. The non-transitory storage medium as recited in claim 17 , wherein the operations further comprise submitting the application executable code for release after the problem has been resolved.
19. A server comprising:
one or more hardware processors; and
the non-transitory storage medium as recited in claim 10 .