<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Software Testing Tools Blog - Testertools &#187; VB</title>
	<atom:link href="http://www.testertools.com/blog/tag/vb/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.testertools.com/blog</link>
	<description>The latest news and blog information from testertools.com</description>
	<lastBuildDate>Fri, 03 Feb 2012 11:24:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New TesterTools &#8211; CodeCount</title>
		<link>http://www.testertools.com/blog/new-testertools-codecount/</link>
		<comments>http://www.testertools.com/blog/new-testertools-codecount/#comments</comments>
		<pubDate>Tue, 23 Feb 2010 07:38:09 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[Ada]]></category>
		<category><![CDATA[and VbScript]]></category>
		<category><![CDATA[ASP]]></category>
		<category><![CDATA[ASP.NET]]></category>
		<category><![CDATA[C#]]></category>
		<category><![CDATA[C/C++]]></category>
		<category><![CDATA[COCOMO]]></category>
		<category><![CDATA[CodeCount]]></category>
		<category><![CDATA[cost estimation models]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[JSP]]></category>
		<category><![CDATA[Perl]]></category>
		<category><![CDATA[Price-S]]></category>
		<category><![CDATA[SEER-SEM]]></category>
		<category><![CDATA[Size metric]]></category>
		<category><![CDATA[SLIM]]></category>
		<category><![CDATA[SLOC]]></category>
		<category><![CDATA[Software Engineering Institute]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[UCC]]></category>
		<category><![CDATA[USC Center for Systems and Software Engineering]]></category>
		<category><![CDATA[VB]]></category>

		<guid isPermaLink="false">http://www.testertools.com/blog/?p=539</guid>
		<description><![CDATA[<br/>
Size is one of the most important attributes of a software product. It is not only the key indicator of software cost and time but also a base unit to derive other metrics for project status and software quality measurement. Size metric is used as an essential input for most of cost estimation models such ]]></description>
			<content:encoded><![CDATA[<br/><p><a href="http://www.testertools.com/blog/wp-content/uploads/2010/02/Understand_31.jpg"><img class="alignleft size-full wp-image-1044" title="Understand_3" src="http://www.testertools.com/blog/wp-content/uploads/2010/02/Understand_31.jpg" alt="" width="285" height="191" /></a></p>
<p>Size is one of the most important attributes of a software product. It is not only the key indicator of software cost and time but also a base unit to derive other metrics for project status and software quality measurement. <strong>Size metric</strong> is used as an essential input for most of <strong>cost estimation models</strong> such as <strong>COCOMO, SLIM, SEER-SEM</strong> and <strong>Price-S.</strong></p>
<p>Although source lines of code or <strong>SLOC</strong> is a widely accepted <strong>sizing metric</strong>, there is a lack of standard that enforces a consistency of what and how to count SLOC. Ensuring consistency across independent organizations in the rules used to count software cost code is often difficult to achieve. To that end, the <strong>USC Center for Systems and Software Engineering (CSSE)</strong> has developed and released a code counting toolset called <strong>CodeCount</strong> to support sizing software code for historical data collection and reporting purposes. This toolset is a collection of tools designed to automate the collection of source code sizing information. It implements the popular code counting standards published by the <strong>Software Engineering Institute (SEI)</strong> and adapted by <strong>COCOMO</strong>. <strong>Logical</strong> and <strong>physical</strong> <strong>SLOC</strong> are among the metrics generated by the toolset.</p>
<p>Direct download link click <a href="http://sunset.usc.edu/research/CODECOUNT/UserInfoFrmUCC_200910.html" target="_blank">here </a></p>
<p>For more info on this product  click<a href="http://csse.usc.edu/research/CODECOUNT/" target="_blank"> here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.testertools.com/blog/new-testertools-codecount/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New TesterTools &#8211; Project Analyzer</title>
		<link>http://www.testertools.com/blog/new-testertools-project-analyzer/</link>
		<comments>http://www.testertools.com/blog/new-testertools-project-analyzer/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 06:01:11 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[Automated Testing]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[dead code]]></category>
		<category><![CDATA[Project Analyzer]]></category>
		<category><![CDATA[standardize naming]]></category>
		<category><![CDATA[VB]]></category>
		<category><![CDATA[VB.NET]]></category>
		<category><![CDATA[VB6 code]]></category>
		<category><![CDATA[Visual Basic]]></category>

		<guid isPermaLink="false">http://www.testertools.com/blog/?p=446</guid>
		<description><![CDATA[<br/>Project Analyzer is a Visual Basic code review and quality control  tool. In other words, static code analysis for VB.  Detect logic  flaws by automated code review.  Perform impact analysis before writing  changes.   Understand poorly documented legacy code.  Reverse engineer  existing VB projects into diagrams and documentation.  Save costs and ]]></description>
			<content:encoded><![CDATA[<br/><p><a href="http://www.aivosto.com/project/project.html"><strong>Project Analyzer</strong> </a>is a <strong>Visual Basic</strong> code review and quality control  tool. In other words, <em>static code analysis</em> for <strong>VB</strong>.  Detect logic  flaws by automated code review.  Perform impact analysis before writing  changes.   Understand poorly documented legacy code.  Reverse engineer  existing VB projects into diagrams and documentation.  Save costs and  keep end-users happy by delivering high-quality VB applications with few  errors.</p>
<p><strong>Key features</strong></p>
<p><strong>Detect dead code</strong>.  Remove unused modules, procedures, variables, constants and controls.  Decrease your .exe by up to 100s of kB.  Dead code info.<br />
<strong></strong></p>
<p><strong>Optimize</strong>.  Find inefficient code. Use faster syntax and optimal declarations.<br />
<strong></strong></p>
<p><strong>Enforce coding style</strong>.  Apply design standards<strong> </strong>and make that spaghetti code readable again.<br />
<strong></strong></p>
<p><strong>Standardize naming</strong>.  Enforce naming conventions<strong> </strong>on variables, procedures and other objects. Pro, Ent<br />
<strong></strong></p>
<p><strong>Detect errors</strong>.  Find functionality problems, such as unimplemented events, questionable tab orders and missing error handling.<br />
<strong></strong></p>
<p><strong>Avoid resource leaks</strong>.  Ensure proper disposing of objects and API handles.<br />
<strong></strong></p>
<p><strong>Find duplicate blocks</strong>.  Spot and join duplicate code blocks that frequently result from copy &amp; paste coding. Ent<br />
<strong></strong></p>
<p><strong>Ensure .NET compatibility</strong>.  Review VB6 code for known VB.NET compatibility issues.</p>
<ul></ul>
<p><img class="aligncenter size-full wp-image-450" title="Project Analyzer" src="http://www.testertools.com/blog/wp-content/uploads/2010/01/Project-Analyzer.gif" alt="Project Analyzer" width="540" height="448" /></p>
<p>View <a href="http://www.testertools.com/11133/Project_Analyzer_-_Automated_Code_Review.html" target="_blank">TesterTools</a> dedicated page for this tool.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.testertools.com/blog/new-testertools-project-analyzer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New TesterTools &#8211; WebCorder</title>
		<link>http://www.testertools.com/blog/new-testertools-webcorder/</link>
		<comments>http://www.testertools.com/blog/new-testertools-webcorder/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 08:26:43 +0000</pubDate>
		<dc:creator>Andrew</dc:creator>
				<category><![CDATA[GUI Testing]]></category>
		<category><![CDATA[action record]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[Crimson Solutions]]></category>
		<category><![CDATA[GUI]]></category>
		<category><![CDATA[text]]></category>
		<category><![CDATA[text check]]></category>
		<category><![CDATA[VB]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[web test]]></category>

		<guid isPermaLink="false">http://www.testertools.com/blog/?p=374</guid>
		<description><![CDATA[<br/>WebCorder is a free GUI software testing tool I developed in VB to allow for simple end user web testing.  Essentially the user presses record and navigates their way through a scenario, telling the program to check for text/images along the way and optionally taking screenshots.  At the end of the process you stop recording ]]></description>
			<content:encoded><![CDATA[<br/><p><strong><a href="http://www.crimsonsolutions.co.uk/testing/testing-downloads.php" target="_blank">WebCorder</a></strong> is a free <strong>GUI</strong> software testing tool I developed in <strong>VB</strong> to allow for simple end user web testing.  Essentially the user presses record and navigates their way through a scenario, telling the program to check for text/images along the way and optionally taking screenshots.  At the end of the process you stop recording and save the script.  You can then play back the script either interactively or in batch mode, and the program will generate log files etc.</p>
<p>View <a href="http://www.testertools.com/11079/WebCorder.html" target="_blank">TesterTools</a> dedicated page for this tool.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.testertools.com/blog/new-testertools-webcorder/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

