<?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></title>
	<atom:link href="http://sqtlab.com/home/feed/" rel="self" type="application/rss+xml" />
	<link>http://sqtlab.com/home</link>
	<description></description>
	<lastBuildDate>Mon, 05 Nov 2012 10:15:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
		<item>
		<title>Bug Log</title>
		<link>http://sqtlab.com/home/2012/11/bug-log/</link>
		<comments>http://sqtlab.com/home/2012/11/bug-log/#comments</comments>
		<pubDate>Mon, 05 Nov 2012 10:15:15 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=900</guid>
		<description><![CDATA[Bug Log is a document that showing the number of defect such as open, closed,postpone,reopen or deferred of a particular module.]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/11/bug-log/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dynamic testing</title>
		<link>http://sqtlab.com/home/2012/11/dynamic-testing/</link>
		<comments>http://sqtlab.com/home/2012/11/dynamic-testing/#comments</comments>
		<pubDate>Mon, 05 Nov 2012 10:09:06 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=896</guid>
		<description><![CDATA[check the expected output with the execution of different test cases is called dynamic testing.It comes under the validation process. Some Dynamic Testing methodologies are: 1.Unit testing 2.Integration testing 3.system testing]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/11/dynamic-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Load testing</title>
		<link>http://sqtlab.com/home/2012/11/load-testing/</link>
		<comments>http://sqtlab.com/home/2012/11/load-testing/#comments</comments>
		<pubDate>Fri, 02 Nov 2012 11:13:37 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=880</guid>
		<description><![CDATA[It is a process to measure the system response time under the normal and peak load conditions.Simply we can say-load test judge the capacity of an system and to ensure that at what point the system response time will degrade. Load testing tool:- 1.Apache JMeter 2.LoadRunner 3.NeoLoad 4.Silk Performer 5.Telerik Test Studio]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/11/load-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Difference between High level and Low level test case</title>
		<link>http://sqtlab.com/home/2012/10/difference-between-high-level-and-low-level-test-case/</link>
		<comments>http://sqtlab.com/home/2012/10/difference-between-high-level-and-low-level-test-case/#comments</comments>
		<pubDate>Thu, 04 Oct 2012 10:41:05 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=876</guid>
		<description><![CDATA[High level test cases covers the major functionality like flow of the application and data base test cases. Low level test cases covers the User Interface of the application. How a user can easy interact with the application.]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/10/difference-between-high-level-and-low-level-test-case/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What are the Entry and Exit criteria in software testing?</title>
		<link>http://sqtlab.com/home/2012/09/what-are-the-entry-and-exit-criteria-in-software-testing/</link>
		<comments>http://sqtlab.com/home/2012/09/what-are-the-entry-and-exit-criteria-in-software-testing/#comments</comments>
		<pubDate>Sat, 15 Sep 2012 08:26:27 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=868</guid>
		<description><![CDATA[Entry criteria start when testing process comes in system. Steps involved in this phase 1. BRS (Business Requirement Specification) 2. SRS (System Requirement Specification) 3. FRS (Functional Requirement Specification) 4. Use case 5. Test Case 6. Test Procedure Exit criteria refer when the whole testing process is completed and application is ready to release.Steps involved [...]]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/09/what-are-the-entry-and-exit-criteria-in-software-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test Design</title>
		<link>http://sqtlab.com/home/2012/05/test-design/</link>
		<comments>http://sqtlab.com/home/2012/05/test-design/#comments</comments>
		<pubDate>Wed, 16 May 2012 05:14:01 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=861</guid>
		<description><![CDATA[A well software test design consists of number of steps that describe the whole test design structure in detailed. 1. Test strategy 2. Test planning 3. Test case design 4. Test procedure 5. Test result document 1. Test strategy The first stage is Preparation of a test strategy. A test strategy is a statement of [...]]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/05/test-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Software Testing</title>
		<link>http://sqtlab.com/home/2012/03/software-testing/</link>
		<comments>http://sqtlab.com/home/2012/03/software-testing/#comments</comments>
		<pubDate>Fri, 23 Mar 2012 07:04:18 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[software testing]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=713</guid>
		<description><![CDATA[Software testing is a process of executing a program with the intention of finding error in the code.In which evaluating the system of system component by manually or with the help of automation tools. Like: qtp, selenium, test director and others.  There are mainly two types of software testing Execution-based testing: the module is run against test [...]]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/03/software-testing/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Bug Tracking Format</title>
		<link>http://sqtlab.com/home/2012/03/bug-tracking-format-2/</link>
		<comments>http://sqtlab.com/home/2012/03/bug-tracking-format-2/#comments</comments>
		<pubDate>Fri, 23 Mar 2012 06:46:22 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[Bug Tracking Format]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=707</guid>
		<description><![CDATA[Bug Tracking Format contains the following steps: Defect Id: Unique recognition of the Defect. Test Case Id: Test case recognition for that defect. Description: Complete description of the bug. Defect Submitted By: Name of the tester who detected and reported the bug. Assigned To: Name of the concern developer who would solve or fix the bug. [...]]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/03/bug-tracking-format-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bug Life Cycle</title>
		<link>http://sqtlab.com/home/2012/03/bug-life-cycle-2/</link>
		<comments>http://sqtlab.com/home/2012/03/bug-life-cycle-2/#comments</comments>
		<pubDate>Fri, 23 Mar 2012 06:28:41 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[Bug Life Cycle]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=700</guid>
		<description><![CDATA[Bug can be defined as the abnormal behavior of the software. Bug detecting and elimination depends upon the proficiency of testing done on the software. In software development process, the bug has a life cycle. This is the standardized process . The bug attains different states in the life cycle. &#160; Steps of bug life cycle: 1. New: [...]]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/03/bug-life-cycle-2/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Test Case</title>
		<link>http://sqtlab.com/home/2012/03/test-case-2/</link>
		<comments>http://sqtlab.com/home/2012/03/test-case-2/#comments</comments>
		<pubDate>Fri, 23 Mar 2012 06:23:37 +0000</pubDate>
		<dc:creator>Vikas</dc:creator>
				<category><![CDATA[Test Case]]></category>

		<guid isPermaLink="false">http://sqtlab.com/home/?p=695</guid>
		<description><![CDATA[Test case document designed by the tester it is based on the SRS document. Test case is the way of how to describe a particular task. And this is the responsibility of a tester to generate the test cases which describe the overall flow of the application. It is the sequence of the step to [...]]]></description>
		<wfw:commentRss>http://sqtlab.com/home/2012/03/test-case-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
