Systems and methods for detection of untested code execution
Systems and methods for improving the quality of a first software product. The methods comprise performing operations by a computing device to run the first software product having source code modified based on code coverage data gathered during testing of the first software product. The code coverage data identifies at least one first portion of the source code which was executed at least once during the testing and identifies at least one second portion of the source code which was not executed during the testing. The methods also comprise: automatically detecting when an execution of the second portion is triggered while the first software product is being used by an end user; and automatically performing a notification action in response to said detecting.
1. A method for improving the quality of a first software product, comprising:
performing operations by a computing device to run the first software product generated by compiling source code modified based on code coverage data gathered during testing of the first software product prior to release on a market, the code coverage data identifying at least one first portion of the source code which was executed at least once during the testing and identifying at least one second portion of the source code which was not executed during the testing;
automatically detecting when an execution of the second portion is triggered while the first software product is being used by an end user subsequent to being released on the market;
automatically performing a notification action in response to said detecting; and
mitigating a risk of defect in the first software product based on the notification action through an end user data-driven triggering of additional testing for untested portions of the source code subsequent to when the first software product has been released.
2. The method according to claim 1 , wherein the first portion and second portion each comprise a code path through a given part of the source code.
3. The method according to claim 1 , wherein the notification action comprises logging a warning message for said detecting.
4. The method according to claim 1 , wherein the notification action comprises sending an electronic communication from the computing device to a remote device of the software product's vendor.
5. The method according to claim 1 , wherein the notification action comprises alerting the end user of the detecting.
6. The method according to claim 1 , wherein the detecting is made at run time of the second portion.
7. The method according to claim 1 , further comprising using the code coverage data to identify which code paths of the source code were tested at least once during the testing and which code paths of the source code were not tested during the testing.
8. The method according to claim 7 , further comprising modifying the source code by inserting a command for taking the notification action at the beginning of each code path found to have been untested.
9. The method according to claim 1 , further comprising:
tracking a number of times the second portion is used by at least the end user;
determining if the number exceeds a threshold value; and
improving the quality of the first software product if a determination is made that the number exceeds the threshold value by
adding a test for the second portion to an additional testing process, and
performing the additional testing process to test the second portion.
10. The method according to claim 9 , further comprising creating a software patch or new version of the software product if the second portion's testing indicates that there is a defect.
11. A system, comprising:
at least one processing element; and
a non-transitory computer-readable storage medium comprising programming instructions that are configured to cause the at least one processing element to implement a method for improving the quality of a first software product, wherein the programming instructions comprise instructions to:
run the first software product generated by compiling source code modified based on code coverage data gathered during testing of the first software product prior to release on a market, the code coverage data identifying at least one first portion of the source code which was executed at least once during the testing and identifying at least one second portion of the source code which was not executed during the testing;
detect when an execution of the second portion is triggered while the first software product is being used by an end user;
perform a notification action in response to said detecting; and
mitigate a risk of defect in the first software product based on the notification action through an end user data-driven triggering of additional testing for untested portions of the source code subsequent to when the first software product has been released.
12. The system according to claim 11 , wherein the first portion and second portion each comprise a code path through a given part of the source code.
13. The system according to claim 11 , wherein the notification action comprises logging a warning message for said detecting.
14. The system according to claim 11 , wherein the notification action comprises sending an electronic communication from the computing device to a remote device of the software product's vendor.
15. The system according to claim 11 , wherein the notification action comprises alerting the end user of the detecting.
16. The system according to claim 11 , wherein the triggering of the second portion's execution is detected at run time of the second portion.
17. The system according to claim 11 , wherein the programming instructions comprise instructions to use the code coverage data to identify which code paths of the source code were tested at least once during the testing and which code paths of the source code were not tested during the testing.
18. The system according to claim 17 , wherein the programming instructions comprise instructions to modify the source code by inserting a command for taking the notification action at the beginning of each code path found to have been untested.
19. The system according to claim 11 , wherein the programming instructions comprise instructions to:
track a number of times the second portion is used by at least the end user; and
determine if the number exceeds a threshold value.
20. The system according to claim 19 , wherein
the second portion is tested if a determination is made that the number exceeds the threshold value, and
a software patch or new version of the software product is created if the second portion's testing indicates that there is a defect.