<?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>The Blog of Travis Gneiting &#187; Testing</title>
	<atom:link href="http://www.blog.travisgneiting.com/category/testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blog.travisgneiting.com</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2012 03:45:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	
	
	<!-- google ad injected by adsense-optimizer http://www.adsenseoptimizer.de -->
	<div  style="padding:7px; float: right; padding-right: 0; margin: 3px;"><!-- Ad number: 1 --><script type="text/javascript"><!--
    	 
    	google_ad_client = "pub-3961093531196233"; google_alternate_color = "FFFFFF";
		google_ad_width = 200; google_ad_height = 200;
		google_ad_format = "200x200_as"; google_ad_type = "text_image";
		google_ad_channel ="1685894941"; google_color_border = "336699";
		google_color_link = "0000FF"; google_color_bg = "FFFFFF";
		google_color_text = "000000"; google_color_url = "008000";
		google_ui_features = "rc:0"; //--></script>
		<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script></div>	<item>
		<title>PEX and Moles &#8211; Promising White Box Unit Testing</title>
		<link>http://www.blog.travisgneiting.com/2010/07/12/pex-and-moles-promising-white-box-unit-testing/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=pex-and-moles-promising-white-box-unit-testing</link>
		<comments>http://www.blog.travisgneiting.com/2010/07/12/pex-and-moles-promising-white-box-unit-testing/#comments</comments>
		<pubDate>Mon, 12 Jul 2010 13:05:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://www.blog.travisgneiting.com/?p=108</guid>
		<description><![CDATA[Pex automatically generates test from Visual Studio code editor. It tries interesting sets of input and output of a method. This provide a high level of test coverage automatically. Currently it is a Visual Studio add in for testing .NET Framework Applications Moles supports Unit Testing by isolation with detours and stubs. http://research.microsoft.com/en-us/projects/pex/ You can [...]]]></description>
			<content:encoded><![CDATA[<!-- google_ad_section_start --><p>Pex automatically generates test from Visual Studio code editor. It tries interesting sets of input and output of a method. This provide a high level of test coverage automatically. Currently it is a Visual Studio add in for testing .NET Framework Applications</p>
<p>Moles supports Unit Testing by isolation with detours and stubs.</p>
<p><a href="http://research.microsoft.com/en-us/projects/pex/">http://research.microsoft.com/en-us/projects/pex/</a></p>
<p>You can try it out online with no install at: <a href="http://www.pexforfun.com/">http://www.pexforfun.com/</a></p>
<!-- google_ad_section_end -->]]></content:encoded>
			<wfw:commentRss>http://www.blog.travisgneiting.com/2010/07/12/pex-and-moles-promising-white-box-unit-testing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>6 Steps for Website Testing at a Glance</title>
		<link>http://www.blog.travisgneiting.com/2010/04/26/website-testing-at-a-glance/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=website-testing-at-a-glance</link>
		<comments>http://www.blog.travisgneiting.com/2010/04/26/website-testing-at-a-glance/#comments</comments>
		<pubDate>Mon, 26 Apr 2010 16:47:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Testing]]></category>
		<category><![CDATA[How to test software]]></category>
		<category><![CDATA[Software Testing]]></category>
		<category><![CDATA[Website Testing]]></category>

		<guid isPermaLink="false">http://www.blog.travisgneiting.com/?p=100</guid>
		<description><![CDATA[Website Application Testing Procedures How to test software 1) Functionality Testing      a) Identification of requirement and goals      b) Input data based on functional specification      c) Output correct based on functional specification      d) Execution of test case      e) Compare actual to expected output        2) Non-functional Testing       a) Baseline Testing             Has performance increased       [...]]]></description>
			<content:encoded><![CDATA[<!-- google_ad_section_start --><h1>Website Application Testing Procedures</h1>
<h2>How to test software</h2>
<p><strong>1)</strong> <strong>Functionality Testing<br />
</strong>     a) Identification of requirement and goals<br />
     b) Input data based on functional specification<br />
     c) Output correct based on functional specification<br />
     d) Execution of test case<br />
     e) Compare actual to expected output       </p>
<p><strong>2) Non-functional Testing<br />
      a) Baseline Testing<br />
            </strong>Has performance increased<br />
<strong>      b) Compatibility Testing<br />
</strong>            Cross Browser, Printer, Mobile, databases, servers<br />
<strong>      c) Compliance (Conformance) Testing<br />
            </strong>Sometimes 3 party testing for certification or standards to meet Quality of Service (QoS)<br />
<strong>      d</strong><strong>) Documentation Testing<br />
            </strong>Is written material readable and usable, with proper spelling and grammer?<br />
   <strong>   e) Endurance (Soak)Testing<br />
</strong>            Testing with significant load for significant amount of time<br />
<strong>      f) Interface Testing<br />
</strong>           Error Handling, Connections<br />
<strong>       g) Load Testing<br />
             </strong>Testing large demand on the software in peak load conditions<br />
      <strong>h) Localization Testing<br />
            </strong>Will the application work in required cultures and locale?<br />
<strong>      i) Performance Testing  <br />
</strong>           Load Testing, Stress Testing, Endurance Testing, Sniff Test, Smoke Test<br />
    <strong>  j) Recovery Testing<br />
           </strong>How does the softwear recover from crashes, hardware and, services, <strong> </strong>failures? Failsafe<br />
      <strong>k) Security Testing<br />
</strong>           Spam, Hacking, URLs, Scripting attacks<br />
<strong>      l) Scalability Testing  <br />
           </strong>Grow to meet needs<strong> <br />
      a)</strong> <strong>Usability testing<br />
</strong>            Navigation, Content, blackbox, steps, user accuracy, recall, response</p>
<!-- google_ad_section_end -->]]></content:encoded>
			<wfw:commentRss>http://www.blog.travisgneiting.com/2010/04/26/website-testing-at-a-glance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

