Abstract: A system and method for analyzing risk factors to enhance the quality of program code have been disclosed. The risks are identified and evaluated, post which test cases are defined for each of the identified risk factors. Further, the defect density, code complexity and change rate corresponding to each of the test cases is determined. Risk profiles are created for each of the test cases. The risk profiles are categorized based on defect density, complexity of the code and change rate. The test cases are evaluated depending upon the risk posed by new scripts added to the program code. The scripts need to be executed for satisfying a necessary and sufficient condition are decided based on the correlation between program code files, activities on those files, defects corresponding to those files and test cases used to test those defects.

Abstract: The various embodiments herein disclose a system and method for generating a delta code coverage information. The system for generating delta code coverage information comprises, a source control module configured for storing a plurality of software program code files to be processed and a plurality of code coverage data corresponding to the plurality of software program code files, a processor configured to generate a delta code coverage data for analysis for each of the plurality of software program code files on a line level or at a branch level by performing a time based delta code coverage process and a path based delta code coverage process.

Abstract: The various embodiments herein provide a method and system for synchronization of links and attachments during synchronization between source and target devices. The system for executing synchronization between the source and target devices comprises a connector framework, a process framework, a mapping manager, a recovery manager, a conflict manager and a failure manager. The method comprises getting the “as of state” of the attachment that is old and new attachment information list for the revisions, then the system having history for the attachment constructs “as of state” and send as part of the event and system not having history for the attachment, stores attachment information in the history state table with the source update time information in poller as well as the time of adding attachment from the adapter.

Abstract: The various embodiments herein provide a system and method for identifying, analyzing and integrating the risks associated with a source code. The system comprises a code coverage module for collecting and transforming the code coverage information by a file name, a source code analyzer module for collecting and transforming source code violations information by the file name, a software configuration management module for collecting and transforming the source code commit information by the file name, a risk analyzer processing module for receiving and relating the collected code coverage information, source code violations information and source code commit information with each other by the file name and a report generation module for publishing the processed result of the collected code coverage information, source code violations information and source code commit information in a report. The report is reviewed for identifying, analyzing and integrating risks associated with source code.

Abstract: The embodiments herein disclose a method for merging results from multiple runs based on run inputs in a source system. The method involves performing first run on a first input, to receive a first result and performing a second run on a second input to receive a second result. The first result and second result are aggregated based on a set of rules and a plurality of merge cases/conditions to obtain a final result. The first run is performed by carrying out a static analysis on the first inputs. The second run is performed by carrying out a static analysis on the second inputs. A method is also provided for merging cobertura coverage and a source code.

Abstract: Techniques are provided for tracking and analyzing defect density by source file or module. Defect density is the number of distinct defects which required changes to be made (to fix the defect) to a particular file or module in a given period of time. This metric is very useful for identifying the most critical areas of weakness of the system and hence the areas where additional investment/action may be taken. For example, this metric can be used to prioritize the area in which unit tests should be written, for which additional automated system tests should be written or which a project should be undertaken to re-write the error prone file or module to improve its quality and maintainability.

Abstract: Techniques are provided for analyzing data called “pivot points” which allows users to instantly generate a report based on all available dimensions for any cell in a tabular report or any data point in a graphical report. In one embodiment, the techniques involve placing a unique UI element or menu next to or on each data point, and clicking on this UI element brings up an automatically filtered list of the valid reports available for just this sub-set of the data. Once the user selects which view they want, a report is automatically generated based on those dimensions with just this subset of data.