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 code, the method comprising:
generating first code that corresponds to a first part of the application code;
mapping a test to the first code, wherein the test is also mapped to a second code, wherein the first code is dependent on the second code and wherein the first code is configured to invoke the second code;
identifying the second code based on the mapping of the test to the first code, wherein the second code corresponds to a different part of the application code, and is mapped to the test;
initiating the test of the first code;
identifying a problem based on the test, if any, between the first code and the second code;
resolving the problem;
performing a risk assessment to identify regression defects;
identifying code that the first code is dependent; and
identifying tests impacted by changes to the first code before releasing the first code.
2. A method for generating application code, the method comprising:
developing first code that corresponds to a first part of the application code;
mapping the first code to tests, wherein the tests are also mapped to other code including a second code, wherein the first code is dependent on the second code and wherein the first code is configured to invoke the second code;
identifying the second code from the mapping and notifying developers of the second code of the first code such that the developers are notified that the first code is dependent on the second code;
performing the tests to identify a problem with the first code and the second code;
resolving the problem prior to releasing the application code;
performing a risk assessment to identify regression defects;
identifying additional code that the first code is dependent on; and
identifying tests impacted by changes to the first code before releasing the first code.
3. The method of claim 2 , further comprising identifying a problem between the first code and the second code.
4. The method of claim 2 , further comprising adding a test to the code repository.
5. The method of claim 2 , further comprising notifying a developer of the first code of changes that may affect the first code.
6. The method of claim 5 , further comprising notifying the developers of the second code of a dependency associated with the first code.
7. The method of claim 2 , further comprising adding tests.
8. The method of claim 2 , further comprising resolving the problem during code development of the first code rather than after submitting the first code for release.
9. A non-transitory storage medium having stored therein computer-instructions which, when executed by one or more hardware processors, perform a method for generating application code, the method comprising:
developing first code that corresponds to a first part of the application code;
mapping the first code to tests, wherein the tests are mapped to other code including a second code, wherein the first code is dependent on the second code and wherein the first code is configured to invoke the second code;
identifying the second code from the mapping and notifying developers of the second code of the first code such that the developers are notified that the first code is dependent on the second code;
performing the tests to identify a problem with the first code and the second code;
resolving the problem prior to releasing the application code;
performing a risk assessment to identify regression defects;
identifying additional code that the first code is dependent on; and
identifying tests impacted by changes to the first code before releasing the first code.
10. The non-transitory storage medium of claim 9 , the method comprising identifying a problem between the first code and the second code.
11. The non-transitory storage medium of claim 9 , the method further comprising adding a test to the code repository.
12. The non-transitory storage medium of claim 9 , the method further comprising notifying a developer of the first code of changes that may impact the first code.
13. The non-transitory storage medium of claim 12 , the method further comprising notifying the developers of the second code of a code dependency associated with the first code.
14. The non-transitory storage medium of claim 9 , the method further comprising adding tests.
15. The non-transitory storage medium of claim 9 , the method further comprising resolving the problem during code development of the first code rather than after submitting the first code for release.