<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>QuantumHeat.org</title>
		<description>Discuss QuantumHeat.org</description>
		<link>http://www.quantumheat.org</link>
		<lastBuildDate>Thu, 07 May 2026 12:15:46 +0000</lastBuildDate>
		<generator>JComments</generator>
		<atom:link href="http://www.quantumheat.org/index.php/en/component/jcomments/feed/com_content/313" rel="self" type="application/rss+xml" />
		<item>
			<title>SE says:</title>
			<link>http://www.quantumheat.org#comment-8884</link>
			<description><![CDATA[As document you should create a test plan which is a project plan for testing. Maybe there a templates for test plans especially for energy devices. I do software testing personally but the main principles should be the same. * introduction with background information / define why do you want test your device * describe test object and list all documents related to the test object * what should be tested / what shouldn't been tested (what can be tested see https://en.wikipedia.org/wiki/ISO/IEC_9126) * prioritise your the features you want to test. do a risk analysis for this. test the features with a higher prio more extensive. * list requirement documents (do you want to evaluate against some standards? ) * draft your test strategy (helicopter view). for black box testing you need a good documentation basis. but decide the right test method for every feature independently. * test environment (plan test environment like you have done it already in your draft, keep the environment parameter under control is a good thing. knowing all your input data and environment parameters makes your test reproducible. keep them constant and stable.) * plan the test driver for test automation. plan what is done manually. * calculate what you need - human resources and all test ware. (make or buy decision) * describe when a test run is assumed as failed or passed * describe how to proceed when a test run is interrupted - in this case it is important to proof that the test object is still in a defined state. * plan the execution of the test run itself step by step * plan all tasks you have to do to prepare the test environment, test run, etc. * what are the deliverables out of the test activities (documents, etc.)]]></description>
			<dc:creator>SE</dc:creator>
			<pubDate>Thu, 20 Jul 2017 18:29:44 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-8884</guid>
		</item>
		<item>
			<title>Randall Reviere says:</title>
			<link>http://www.quantumheat.org#comment-4783</link>
			<description><![CDATA[Just to let you know that as of 1/8/14 your catch is not working on the new account creation page. I'd like to create an account but can't at this point.]]></description>
			<dc:creator>Randall Reviere</dc:creator>
			<pubDate>Wed, 08 Jan 2014 23:45:47 +0000</pubDate>
			<guid>http://www.quantumheat.org#comment-4783</guid>
		</item>
	</channel>
</rss>
