![]() ![]() So far so good, but before IDz 14.1.5, if you close the workbench and open it again you will notice that analysis results are completely gone. Having those results, you could then fix the found issues, export them in xml format or make a report. Once you have picked all rules for analysis you can click Analyze button and wait for the results to appear in Software Analyzer Results view. Typically, the precise definition of “too many” and “too little” can be adjusted by selecting appropriate thresholds in the properties pane beneath the rule selection.įigure 4. a class containing too many lines of code and too little comments is considered a violation. Metrics rules give more general picture of code quality, i.e. If you use a different convention for some variable, then the place in code where you declared it is marked as rule violation. java naming convention dictates to use camel case starting with a lower-case letter for variable names. Code Review providers contain rules with violations occurring at specific location: e.g. IDz is shipping providers of two kinds: Code Review and Metrics. globalization, security, naming conventions, etc. The next level of the hierarchy is rule category, which is just a logical grouping for sets of rules that have something in common, e.g. ![]() Rules in IDz are grouped according to following hierarchy: the top element is rule provider rules from two distinct providers are so different that they are using generally incompatible data models and require results to be displayed in separate views. Then you can choose whether you want to check the entire workspace, or some projects or working sets and switch to the Rules tab where you can select the rules you want the source code to be compliant with.įigure 2. ![]() To analyze your source code, you can right click on any project, select Software Analyzer -> Software Analyzer Configurations and double click Software Analyzer to create a new configuration. IDz is providing customers with static analysis capabilities for a long time, supporting languages like Java, COBOL and PL/I. Static Analysis is a technique for checking software for various issues, such as bad code, vulnerabilities, potential bugs, compliance to certain standards, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |