
<?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>QA Evangelist &#187; SQA &#8211; Terms</title>
	<atom:link href="http://blog.qaevangelist.com/?feed=rss2&#038;cat=10" rel="self" type="application/rss+xml" />
	<link>http://blog.qaevangelist.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 29 Jul 2010 14:55:06 +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>Data-Driven Testing</title>
		<link>http://blog.qaevangelist.com/?p=196</link>
		<comments>http://blog.qaevangelist.com/?p=196#comments</comments>
		<pubDate>Mon, 17 May 2010 14:20:18 +0000</pubDate>
		<dc:creator>George Nunez</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=196</guid>
		<description><![CDATA[Data-driven testing is a term used to define software testing where one test script is used against several iterations of variable data; thereby, testing many possible conditions with one test case.   This re-use reduces maintenance and improves test coverage.  The data values are typically stored in one or more central repository: data sources (i.e. csv [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=196</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Integration Testing</title>
		<link>http://blog.qaevangelist.com/?p=71</link>
		<comments>http://blog.qaevangelist.com/?p=71#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:30:37 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=71</guid>
		<description><![CDATA[Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to components integration for applications and client/server functions in distributed systems.
]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=71</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unit Testing</title>
		<link>http://blog.qaevangelist.com/?p=69</link>
		<comments>http://blog.qaevangelist.com/?p=69#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:30:14 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=69</guid>
		<description><![CDATA[Unit testing is a strategy used to verify that a particular module of source code is working properly. It is a subset of White-box testing. The idea about unit tests is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed. [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=69</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stress Testing</title>
		<link>http://blog.qaevangelist.com/?p=67</link>
		<comments>http://blog.qaevangelist.com/?p=67#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:29:54 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=67</guid>
		<description><![CDATA[A form of testing that is used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. For example, a web server may be stress tested using scripts, bots, and various denials of service tools to observe [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=67</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Load Testing</title>
		<link>http://blog.qaevangelist.com/?p=65</link>
		<comments>http://blog.qaevangelist.com/?p=65#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:29:27 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=65</guid>
		<description><![CDATA[Load testing is generally used by simulating multiple users accessing the program&#8217;s services concurrently. As such, this testing is most relevant for multi-user systems, often one built using a client/server model, such as web servers. However, other types of software systems can be load-tested also.
]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=65</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Performance testing</title>
		<link>http://blog.qaevangelist.com/?p=63</link>
		<comments>http://blog.qaevangelist.com/?p=63#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:29:04 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=63</guid>
		<description><![CDATA[Performance testing is performed to determine how fast certain aspects of a system perform under a particular workload. Performance testing can serve different purposes:
1)	It can demonstrate that the system meets performance criteria.
2)	It can compare two systems to find which performs better.
3)	It can measure what parts of the system or workload cause the system to perform [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=63</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exploratory testing</title>
		<link>http://blog.qaevangelist.com/?p=61</link>
		<comments>http://blog.qaevangelist.com/?p=61#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:28:43 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=61</guid>
		<description><![CDATA[also called Ad Hoc testing, is simultaneous with learning, test design and test execution. Since it has a highly situational structure it can seem, to the casual observer, that it has no structure at all. In James Bach’s article: Where Does Exploratory Testing Fit? He quoted: “… … exploratory testing, where you explore the product [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=61</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Smoke testing</title>
		<link>http://blog.qaevangelist.com/?p=59</link>
		<comments>http://blog.qaevangelist.com/?p=59#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:28:13 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=59</guid>
		<description><![CDATA[Smoke Testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work without worrying about the details. It is done in order to check if the application is ready for further major testing, and to make sure it is working properly without failing up to the least expected level .
]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=59</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User Acceptance Testing</title>
		<link>http://blog.qaevangelist.com/?p=57</link>
		<comments>http://blog.qaevangelist.com/?p=57#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:27:55 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=57</guid>
		<description><![CDATA[lso called beta testing, application testing, and end user testing &#8211; is a phase of software development in which the software is tested in the &#8220;real world&#8221; by the intended audience. UAT can be done by
a.	in-house in which tester subjects use the software
b. more typically for widely-distributed software, by making the test version available for [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=57</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Build Acceptance Testing</title>
		<link>http://blog.qaevangelist.com/?p=55</link>
		<comments>http://blog.qaevangelist.com/?p=55#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:27:29 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Terms]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=55</guid>
		<description><![CDATA[A set of abbreviated test scenarios are used to evaluate the functional integrity of product components in the build process and the feasibility for the Quality Assurance team to complete the testing tasks on an existing build.
]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=55</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
