<?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>TestRoot &#187; Test plan</title>
	<atom:link href="http://www.testroot.com/tag/test-plan/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.testroot.com</link>
	<description>Yazılım Test &#38; Kalite</description>
	<lastBuildDate>Wed, 24 Aug 2011 08:05:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Test plan Outline</title>
		<link>http://www.testroot.com/2009/01/29/test-plan-outline/</link>
		<comments>http://www.testroot.com/2009/01/29/test-plan-outline/#comments</comments>
		<pubDate>Thu, 29 Jan 2009 12:13:37 +0000</pubDate>
		<dc:creator>Kenan Yaylıcıoğlu</dc:creator>
				<category><![CDATA[Yazılım Test]]></category>
		<category><![CDATA[Outline]]></category>
		<category><![CDATA[Test plan]]></category>

		<guid isPermaLink="false">http://www.testroot.com/?p=31</guid>
		<description><![CDATA[Bir kaç arkadaş sorduda bir test plan örneği varmı diye, kendi kullandığım kullanılan şirkete uyarlandığı için örnek göstermek istemedim. Bunun yeri olması gerektiği gibi bir plan outlineı vereceğim, kendi işleyişinize göre uyarlama yapılırsa oldukça kullanışlı olabilir. 1. SCOPE 1.1 Identification 1.2 System overview 1.3 Document overview 1.4 Relationship to other plans 2. REFERENCED DOCUMENTS 3. [...]]]></description>
			<content:encoded><![CDATA[<p>Bir kaç arkadaş sorduda bir test plan örneği varmı diye, kendi kullandığım kullanılan şirkete uyarlandığı için örnek göstermek istemedim. Bunun yeri olması gerektiği gibi bir plan outlineı vereceğim, kendi işleyişinize göre uyarlama yapılırsa oldukça kullanışlı olabilir.</p>
<p>1. <strong>SCOPE</strong><br />
  1.1 Identification<br />
  1.2 System overview<br />
  1.3 Document overview<br />
  1.4 Relationship to other plans<br />
2. <strong>REFERENCED DOCUMENTS	</strong><br />
3. <strong>SOFTWARE TEST ENVIRONMENT</strong><br />
  3.x [Name of test site(s)]<br />
    3.x.1 Software items<br />
    3.x.2 Hardware and firmware items<br />
    3.x.3 Other materials<br />
    3.x.4 Proprietary nature, acquirer&#8217;s rights, and licensing<br />
    3.x.5 Installation, testing, and control<br />
    3.x.6 Participating organizations<br />
    3.x.7 Personnel<br />
    3.x.8 Orientation plan<br />
    3.x.9 Tests to be performed<br />
4. <strong>TEST IDENTIFICATION</strong><br />
  4.1 General information<br />
    4.1.1 Test levels<br />
    4.1.2 Test classes<br />
    4.1.3 General test conditions<br />
    4.1.4 Test progression<br />
    4.1.5 Data recording, reduction, and analysis<br />
  4.2 Planned tests<br />
    4.2.x (Item(s) to be tested)<br />
    4.2.x.y (Project-unique identifier of a test)<br />
5. <strong>TEST SCHEDULES</strong><br />
6. <strong>REQUIREMENTS TRACEABILITY</strong>	</p>
]]></content:encoded>
			<wfw:commentRss>http://www.testroot.com/2009/01/29/test-plan-outline/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.469 seconds -->

