Test Strategy
For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!
Automated Acceptance Testing
CodeCount automates the collection of source code sizing information. The CodeCount toolset utilizes one of two possible source lines of code (SLOC) definitions, physical or logical. COCOMO (COnstructive COst MOdel), is a tool which allows one to estimate the cost, effort, and schedule associated with a prospective software development project.
Languages: Ada, Assembly, C, C++, COBOL, FORTRAN, Java, JOVIAL, Pascal, PL1
SLOCCount is a set of tools for counting physical Source Lines of Code (SLOC) in a large number of languages of a potentially large set of programs. SLOCCount can automatically identify and measure many programming languages.
Languages: Ada, Assembly, awk, Bourne shell and variants, C, C++, C shell, COBOL, C#, Expect, Fortran, Haskell, Java, lex/flex, LISP/Scheme, Makefile, Modula-3, Objective-C, Pascal, Perl, PHP, Python, Ruby, sed, SQL, TCL, and Yacc/Bison.
SourceMonitor lets you see inside your software source code to find out how much code you have and to identify the relative complexity of your modules. For example, you can use SourceMonitor to identify the code that is most likely to contain defects and thus warrants formal review. Collects metrics in a fast, single pass through source files. Displays and prints metrics in tables and charts.
Languages: C++, C, C#, Java, Delphi, Visual Basic (VB6) or HTML
LOCC is an extensible system for producing hierarchical, incremental measurements of work product size that are useful for estimation, planning, and other software engineering activities. LOCC supports size measurement of grammar-based languages through integrated support for JavaCC. LOCC produces size data corresponding to the number of packages, the number of classes in each package, the number of methods in each class, and the number of lines of code in each method.
Languages: C++, Java
Code Counter Pro is perfect for those reports you need to send to your boss – count up all your progamming lines (SLOC, KLOC) automatically, find out your team’s productivity, use as handy help for measuring Function Points through Backfiring, measure comment percentages and more.
Languages: ASM, COBOL, C, C++, C#, Fortran, Java, JSP, PHP, HTML, Delphi, Pascal, VB, XML
SLOC Metrics measures the size of your source code based on the Physical Source Lines of Code metric recommended by the Software Engineering Institute at Carnegie Mellon University (CMU/SEI-92-TR-019). Specifically, the source lines that are included in the count are the lines that contain executable statements, declarations, and/or compiler directives. Comments, and blank lines are excluded from the count. When a line or statement contains more than one type, it is classified as the type with the highest precedence. The order of precedence for the types is: executable, declaration, compiler directive, comment and lastly, white space.
Languages: ASP, C, C++, C#, Java, HTML, Perl, Visual Basic
Resource Standard Metrics, or RSM, is a source code metrics and quality analysis tool unlike any other on the market. The unique ability of RSM to support virtually any operating system provides your enterprise with the ability to standardize the measurement of source code quality and metrics throughout your organization. RSM provides the fastest, most flexible and easy-to-use tool to assist in the measurement of code quality and metrics.
Languages: C, C++, C#, Java
EZ-Metrix supports software development estimates, productivity measurement, schedule forecasting and quality analysis. With an easy Internet-based interface, multiple language support and flexible licensing features, you will be up and running in minutes with EZ-Metrix. Measure source code size from virtually all text-based languages and from any platform or operating system with the same utility. Size data may be stored in EZ-Metrix’s internal database or may be exported for further analysis.
Languages: Ada, ALGOL, antlr, asp, Assembly, awk, bash, BASIC, bison, C, C#, C++, ColdFusion, Delphi, Forth, FORTRAN, Haskell, HTML, Java, Javascript, JOVIAL, jsp, lex, lisp, Makefile, MUMPS, Pascal, Perl, PHP, PL/SQL, PL1, PowerBuilder, ps, Python, Ruby, sdl, sed, SGML, shell, SQL, Visual Basic, XML, Yacc
McCabe IQ enables you to deliver better, more reliable software to your end-users, and is known worldwide as the gold standard for the analysis, comprehension, testing, and reengineering of new software and legacy systems. McCabe IQ uses advanced software metrics to identify, objectively measure, and report on the complexity and quality of your code at the application and enterprise level.
Languages: Ada, ASM86, C, C#, C++.NET, C++, COBOL, FORTRAN, Java, JSP, Perl, PL1, VB, VB.NET
An important consideration for Software Project Managers is whether the requirements are being altered in a given project without their knowledge or consent. The impact of unauthorized or unscheduled departure from requirements can lead to considerable problems in maintaining and managing large source projects.
Having received requests from several major C/C++ and Java projects to measure ‘changes’ in source code projects, Power Software was commissioned to manufacture an automated tool to measure changed lines of source code.
The first question we asked was ‘are there any existing tools that can already accomplish this task?’ The obvious starting place was ‘Change Management’ tools like CMVC (Configuration Management Version Control) systems. These tools indicate which files have changed between projects but do not gather and present the information in the format our customers’ required. One problem with CMVC systems was that a file shown to be ‘changed’ might have changed only by time and date. This is misleading if we are looking for actual changes in source code.
The next place we looked was at existing Software Metrics tools. These tools measure source code parameters including SLOC (source lines of code). However it is possible that a Software Metrics tool could report that the compared files or projects have the same total number of source lines but these could have changed intrinsically. The actual lines of code could have changed but the total number of lines will be unchanged so the ‘changed line’ is not detected.
For our customers the particular information required is ‘changed source lines of code’, ‘added source lines of code’ and ‘deleted source lines of code’. This needs to be gathered across two releases of the same project to show exactly what has ‘changed’. The information needs to be presented as ‘changed lines’ at the file and project level to assist management in their job of maintaining highest quality through proper control mechanisms.
Hi,
Please find to answer follwing questions in order to find out sutable CLOC tools for your project.
CodeCount automates the collection of source code sizing information. The CodeCount toolset utilizes one of two possible source lines of code (SLOC) definitions, physical or logical. COCOMO (COnstructive COst MOdel), is a tool which allows one to estimate the cost, effort, and schedule associated with a prospective software development project.
Languages: Ada, Assembly, C, C++, COBOL, FORTRAN, Java, JOVIAL, Pascal, PL1
SLOCCount is a set of tools for counting physical Source Lines of Code (SLOC) in a large number of languages of a potentially large set of programs. SLOCCount can automatically identify and measure many programming languages.
Languages: Ada, Assembly, awk, Bourne shell and variants, C, C++, C shell, COBOL, C#, Expect, Fortran, Haskell, Java, lex/flex, LISP/Scheme, Makefile, Modula-3, Objective-C, Pascal, Perl, PHP, Python, Ruby, sed, SQL, TCL, and Yacc/Bison.
SourceMonitor lets you see inside your software source code to find out how much code you have and to identify the relative complexity of your modules. For example, you can use SourceMonitor to identify the code that is most likely to contain defects and thus warrants formal review. Collects metrics in a fast, single pass through source files. Displays and prints metrics in tables and charts.
Languages: C++, C, C#, Java, Delphi, Visual Basic (VB6) or HTML
LOCC is an extensible system for producing hierarchical, incremental measurements of work product size that are useful for estimation, planning, and other software engineering activities. LOCC supports size measurement of grammar-based languages through integrated support for JavaCC. LOCC produces size data corresponding to the number of packages, the number of classes in each package, the number of methods in each class, and the number of lines of code in each method.
Languages: C++, Java
Code Counter Pro is perfect for those reports you need to send to your boss – count up all your progamming lines (SLOC, KLOC) automatically, find out your team’s productivity, use as handy help for measuring Function Points through Backfiring, measure comment percentages and more.
Languages: ASM, COBOL, C, C++, C#, Fortran, Java, JSP, PHP, HTML, Delphi, Pascal, VB, XML
SLOC Metrics measures the size of your source code based on the Physical Source Lines of Code metric recommended by the Software Engineering Institute at Carnegie Mellon University (CMU/SEI-92-TR-019). Specifically, the source lines that are included in the count are the lines that contain executable statements, declarations, and/or compiler directives. Comments, and blank lines are excluded from the count. When a line or statement contains more than one type, it is classified as the type with the highest precedence. The order of precedence for the types is: executable, declaration, compiler directive, comment and lastly, white space.
Languages: ASP, C, C++, C#, Java, HTML, Perl, Visual Basic
Resource Standard Metrics, or RSM, is a source code metrics and quality analysis tool unlike any other on the market. The unique ability of RSM to support virtually any operating system provides your enterprise with the ability to standardize the measurement of source code quality and metrics throughout your organization. RSM provides the fastest, most flexible and easy-to-use tool to assist in the measurement of code quality and metrics.
Languages: C, C++, C#, Java
EZ-Metrix supports software development estimates, productivity measurement, schedule forecasting and quality analysis. With an easy Internet-based interface, multiple language support and flexible licensing features, you will be up and running in minutes with EZ-Metrix. Measure source code size from virtually all text-based languages and from any platform or operating system with the same utility. Size data may be stored in EZ-Metrix’s internal database or may be exported for further analysis.
Languages: Ada, ALGOL, antlr, asp, Assembly, awk, bash, BASIC, bison, C, C#, C++, ColdFusion, Delphi, Forth, FORTRAN, Haskell, HTML, Java, Javascript, JOVIAL, jsp, lex, lisp, Makefile, MUMPS, Pascal, Perl, PHP, PL/SQL, PL1, PowerBuilder, ps, Python, Ruby, sdl, sed, SGML, shell, SQL, Visual Basic, XML, Yacc
McCabe IQ enables you to deliver better, more reliable software to your end-users, and is known worldwide as the gold standard for the analysis, comprehension, testing, and reengineering of new software and legacy systems. McCabe IQ uses advanced software metrics to identify, objectively measure, and report on the complexity and quality of your code at the application and enterprise level.
Languages: Ada, ASM86, C, C#, C++.NET, C++, COBOL, FORTRAN, Java, JSP, Perl, PL1, VB, VB.NET
rajeshkumar created the topic: Checkstyle reports different issues on different r
Checkstyle reports different issues on different runs
I’m seeing something strange with the checkstyle plugin.
We are using Checkstyle plugin 2.5 and configure it using a checkstyle
file in a jar that is an extension of our pom.
Thus:
<project> <properties> <checkstyle-maven-plugin.version>2.5</checkstyle-maven-plugin.version> </properties> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-checkstyle-plugin</artifactId> <version>${checkstyle-maven-plugin.version}</version> <configuration> <includeTestSourceDirectory>true</includeTestSourceDirectory> <configLocation>iris_checks.xml</configLocation> </configuration> </plugin> </plugins> <extensions> <extension> <groupId>org.example</groupId> <artifactId>build-resources</artifactId> <version>1.0.4</version> </extension> </extensions> </build> </project>
When I run the following command line:
mvn clean checkstyle:checkstyle && cp target/checkstyle-result.xml .
&& mvn clean checkstyle:checkstyle && diff checkstyle-result.xml
target/checkstyle-result.xml
I sometimes see differences like:
> <error line="12" column="5" severity="warning" message="Missing a Javadoc > comment." > source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocVariableCheck"/> 279a281,286 > <error line="122" column="9" severity="warning" message="Missing a Javadoc > comment." > source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocVariableCheck"/> > <error line="123" column="9" severity="warning" message="Missing a Javadoc > comment." > source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocVariableCheck"/> > <error line="124" column="9" severity="warning" message="Missing a Javadoc > comment." > source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocVariableCheck"/> > <error line="125" column="9" severity="warning" message="Missing a Javadoc > comment." > source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocVariableCheck"/> > <error line="126" column="9" severity="warning" message="Missing a Javadoc > comment." > source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocVariableCheck"/> > <error line="127" column="9" severity="warning" message="Missing a Javadoc > comment." > source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocVariableCheck"/>
I don’t change code between runs, so I assume this may never happen.
What could cause this?
With regards,
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
rajeshkumar created the topic: Integration of Sonar in IDE
Integration of Sonar in IDE to enable instant feedback to developer
Proposals from both Evgeny and Andrew have been accepted for Google Summer Of Code 2010 ( code.google.com/soc/ ) :
* Integration of Sonar in IDE to enable instant feedback to developer (Evgeny) : in other words, providing Sonar plugins for IDEA and Eclipse.
* Sonar Widget Dashboard – Customizable U (Andrew) : in other words, making Sonar dashboards configurable.
And here is a post from Evgeny on this subject : godin.net.ru/2010/04/27/my-proposal-for-…summer-of-code-2010/ .
If you want to actively participate to discussions on the way to implement those two ideas, you can subscribe to the dev mailing list.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
rajeshkumar created the topic: calculate KLOC (added, deleted, updated) ?
Hi,
I am looking for a tools which help me to calculate KLOC (added, deleted, updated) ?
RSM is the one but its commercial.
Any Suggestion?
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
scmuser created the topic: KLOC tools reasearch
I was going through the www.powersoftware.com
I have requirement to KLOC process which not only gather the matrix but also, Create a delta report as such src addition, deletion and update.
Could you please tell me which tool is good for us?
I am just going through Sonar, SLOC, Squale and many more… how does Ez-Metrix is different from following tools?
CAST
Sonar
SLOC
RSM
LocMetrics
EZ-Metrics
Metrixware
Parasoft (Jtest)
Squale
KODERS
PRACTILINE
POWERSOFTWARE
CLOC
Unified CodeCount (UCC)
scmuser replied the topic: Re:KLOC tools reasearch
There is one more links given below…
community.scmgalaxy.com/pg/blog/rajeshku…3536/sonar-vs-squale
Rajesh Kumar
Good Reference can be found on
<!–[if gte mso 9]> Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 <![endif]–><!–[if gte mso 9]> <![endif]–><!–[if gte mso 10]> <! /* Style Definitions */ table.MsoNormalTable {mso-style-name:”Table Normal”; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:””; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:”Calibri”,”sans-serif”; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:”Times New Roman”; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:”Times New Roman”; mso-bidi-theme-font:minor-bidi;} –> <!–[endif]–>
<!–[if gte mso 9]> Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 <![endif]–><!–[if gte mso 9]> <![endif]–><!–[if gte mso 10]> /* Style Definitions */ table.MsoNormalTable {mso-style-name:”Table Normal”; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:””; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:”Calibri”,”sans-serif”; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:”Times New Roman”; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:”Times New Roman”; mso-bidi-theme-font:minor-bidi;} <![endif]–>
http://community.scmgalaxy.com/pg/file/read/4281/sloc-using-rsm
http://cloc.sourceforge.net/
http://www.qsm.com/?q=resources/code-counters/index.html
http://en.wikipedia.org/wiki/Source_lines_of_code