<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://en.accunit.access-codelib.net/skins/common/feed.css?207"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>AccUnit - User contributions [en]</title>
		<link>http://en.accunit.access-codelib.net/Special:Contributions/Sten+Schmidt</link>
		<description>From AccUnit</description>
		<language>en</language>
		<generator>MediaWiki 1.15.1</generator>
		<lastBuildDate>Sun, 31 May 2026 05:43:09 GMT</lastBuildDate>
		<item>
			<title>Getting started</title>
			<link>http://en.accunit.access-codelib.net/Getting_started</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Erste_Schritte]]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Software_testing Software testing] is a important part of software development.&lt;br /&gt;
&lt;br /&gt;
During earlier tests at the end of the software development cycle as an acceptance condition,&lt;br /&gt;
today's approach is to write the test before programming the logic of the application ([http://en.wikipedia.org/wiki/Test-driven_development TDD]).&lt;br /&gt;
&lt;br /&gt;
Many actual programming languages ​​provide appropriate tools for automated test execution. The [http://en.wikipedia.org/wiki/Visual_Basic_for_Applications VBA]  programming language&lt;br /&gt;
unfortunately only contains rudimentary functionality to test the code (Debug.Print, Debug.Assert).&lt;br /&gt;
&lt;br /&gt;
AccUnit now offers the possibility to run automated tests on MS Access. It uses the SimplyVBUnit, an Unit Testing Framework written in VB6.&lt;br /&gt;
&lt;br /&gt;
The following pages will help you to write the first tests for your application.&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 19:15:48 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Getting_started</comments>		</item>
		<item>
			<title>Getting started</title>
			<link>http://en.accunit.access-codelib.net/Getting_started</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Erste_Schritte]]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Software_testing Software testing] is a important part of software development.&lt;br /&gt;
&lt;br /&gt;
During earlier tests at the end of the software development cycle as an acceptance condition,&lt;br /&gt;
today's approach is to write the test before programming the logic of the application ([http://en.wikipedia.org/wiki/Test-driven_development TDD]).&lt;br /&gt;
&lt;br /&gt;
Many actual programming languages ​​provide appropriate tools for automated test execution. The [http://en.wikipedia.org/wiki/Visual_Basic_for_Applications VBA]  programming language&lt;br /&gt;
unfortunately only contains rudimentary functionality to test the code (Debug.Print, Debug.Assert).&lt;br /&gt;
&lt;br /&gt;
AccUnit now offers the possibility to run automated tests on MS Access. It uses the SimplyVBUnit, an Unit Testing Framework written in VB6.&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 19:14:06 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Getting_started</comments>		</item>
		<item>
			<title>Getting started</title>
			<link>http://en.accunit.access-codelib.net/Getting_started</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Erste_Schritte]]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Software_testing Software testing] is a important part of software development.&lt;br /&gt;
&lt;br /&gt;
During earlier tests at the end of the software development cycle as an acceptance condition,&lt;br /&gt;
today's approach is to write the test before programming the logic of the application ([http://en.wikipedia.org/wiki/Test-driven_development TDD]).&lt;br /&gt;
&lt;br /&gt;
Many actual programming languages ​​provide appropriate tools for automated test execution. The [http://en.wikipedia.org/wiki/Visual_Basic_for_Applications VBA]  programming language&lt;br /&gt;
unfortunately only contains rudimentary functionality to test the code (Debug.Print, Debug.Assert).&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 19:07:24 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Getting_started</comments>		</item>
		<item>
			<title>Getting started</title>
			<link>http://en.accunit.access-codelib.net/Getting_started</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Erste_Schritte]]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Software_testing Software testing] is a important part of software development.&lt;br /&gt;
&lt;br /&gt;
During earlier tests at the end of the software development cycle as an acceptance condition,&lt;br /&gt;
today's approach is to write the test before programming the logic of the application ([http://en.wikipedia.org/wiki/Test-driven_development TDD]).&lt;br /&gt;
&lt;br /&gt;
Many actual programming languages ​​provide appropriate tools for automated test execution.&lt;br /&gt;
&lt;br /&gt;
The [http://en.wikipedia.org/wiki/Visual_Basic_for_Applications VBA]  programming language&lt;br /&gt;
unfortunately only contains rudimentary functionality to test the code (Debug.Print, Debug.Assert).&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 19:07:04 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Getting_started</comments>		</item>
		<item>
			<title>Getting started</title>
			<link>http://en.accunit.access-codelib.net/Getting_started</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Erste_Schritte]]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Software_testing Software testing] is a important part of software development.&lt;br /&gt;
&lt;br /&gt;
During earlier tests at the end of the software development cycle as an acceptance condition,&lt;br /&gt;
today's approach is to write the test before programming the logic of the application ([http://en.wikipedia.org/wiki/Test-driven_development TDD]).&lt;br /&gt;
&lt;br /&gt;
Many actual programming languages ​​provide appropriate tools for automated test execution.&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 19:03:41 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Getting_started</comments>		</item>
		<item>
			<title>Getting started</title>
			<link>http://en.accunit.access-codelib.net/Getting_started</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Erste_Schritte]]&lt;br /&gt;
&lt;br /&gt;
[http://en.wikipedia.org/wiki/Software_testing Software testing] is a important part of software development.&lt;br /&gt;
&lt;br /&gt;
During earlier tests at the end of the software development cycle as an acceptance condition,&lt;br /&gt;
today's approach is to write the test before programming the logic of the application ([http://en.wikipedia.org/wiki/Test-driven_development TDD]).&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 19:00:46 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Getting_started</comments>		</item>
		<item>
			<title>UsageWithoutAddIn</title>
			<link>http://en.accunit.access-codelib.net/UsageWithoutAddIn</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;/* remove */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Nutzung ohne Add-In]]&lt;br /&gt;
&lt;br /&gt;
=== Using AccUnit without Add-In ===&lt;br /&gt;
(is not recommended)&lt;br /&gt;
&lt;br /&gt;
The following comments are not required for use with the Add-In.&lt;br /&gt;
==== AccUnit support for the Debug-Window====&lt;br /&gt;
===== Configure the access application =====&lt;br /&gt;
====== activate ======&lt;br /&gt;
Input values to the Debug-Window: &amp;lt;code&amp;gt;CreateObject(&amp;quot;AccUnit.Configurator&amp;quot;).Init VBE.ActiveVBProject&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Result:&lt;br /&gt;
* references to AccUnit and SimplyVBUnit will be activated&lt;br /&gt;
* the HelperClass ''TestSuiteStarter'' and the Module ''_AccUnitObjects'' will be created&lt;br /&gt;
&lt;br /&gt;
====== remove ======&lt;br /&gt;
Input values to the Debug-Window: &amp;lt;code&amp;gt;CreateObject(&amp;quot;AccUnit.Configurator&amp;quot;).Remove VBE.ActiveVBProject&amp;lt;/code&amp;gt;&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 18:24:19 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:UsageWithoutAddIn</comments>		</item>
		<item>
			<title>UsageWithoutAddIn</title>
			<link>http://en.accunit.access-codelib.net/UsageWithoutAddIn</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;/* activate */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Nutzung ohne Add-In]]&lt;br /&gt;
&lt;br /&gt;
=== Using AccUnit without Add-In ===&lt;br /&gt;
(is not recommended)&lt;br /&gt;
&lt;br /&gt;
The following comments are not required for use with the Add-In.&lt;br /&gt;
==== AccUnit support for the Debug-Window====&lt;br /&gt;
===== Configure the access application =====&lt;br /&gt;
====== activate ======&lt;br /&gt;
Input values to the Debug-Window: &amp;lt;code&amp;gt;CreateObject(&amp;quot;AccUnit.Configurator&amp;quot;).Init VBE.ActiveVBProject&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Result:&lt;br /&gt;
* references to AccUnit and SimplyVBUnit will be activated&lt;br /&gt;
* the HelperClass ''TestSuiteStarter'' and the Module ''_AccUnitObjects'' will be created&lt;br /&gt;
&lt;br /&gt;
====== remove ======&lt;br /&gt;
nput values to the Debug-Window: &amp;lt;code&amp;gt;CreateObject(&amp;quot;AccUnit.Configurator&amp;quot;).Remove VBE.ActiveVBProject&amp;lt;/code&amp;gt;&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 18:23:35 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:UsageWithoutAddIn</comments>		</item>
		<item>
			<title>UsageWithoutAddIn</title>
			<link>http://en.accunit.access-codelib.net/UsageWithoutAddIn</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Nutzung ohne Add-In]]&lt;br /&gt;
&lt;br /&gt;
=== Using AccUnit without Add-In ===&lt;br /&gt;
(is not recommended)&lt;br /&gt;
&lt;br /&gt;
The following comments are not required for use with the Add-In.&lt;br /&gt;
==== AccUnit support for the Debug-Window====&lt;br /&gt;
===== Configure the access application =====&lt;br /&gt;
====== activate ======&lt;br /&gt;
Input values to the Debug-Window: &amp;lt;code&amp;gt;CreateObject(&amp;quot;AccUnit.Configurator&amp;quot;).Init VBE.ActiveVBProject&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Result:&lt;br /&gt;
* references to AccUnit and SimplyVBUnit will be aktivated&lt;br /&gt;
* the HelperClass ''TestSuiteStarter'' and the Module ''_AccUnitObjects'' will be created&lt;br /&gt;
&lt;br /&gt;
====== remove ======&lt;br /&gt;
nput values to the Debug-Window: &amp;lt;code&amp;gt;CreateObject(&amp;quot;AccUnit.Configurator&amp;quot;).Remove VBE.ActiveVBProject&amp;lt;/code&amp;gt;&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 18:23:12 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:UsageWithoutAddIn</comments>		</item>
		<item>
			<title>UsageWithoutAddIn</title>
			<link>http://en.accunit.access-codelib.net/UsageWithoutAddIn</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Nutzung ohne Add-In]]&lt;br /&gt;
&lt;br /&gt;
=== Using AccUnit without Add-In ===&lt;br /&gt;
(is not recommended)&lt;br /&gt;
&lt;br /&gt;
The following comments are not required for use with the Add-In.&lt;br /&gt;
==== AccUnit support for the Debug-Window====&lt;br /&gt;
===== Configure the access application =====&lt;br /&gt;
====== activate ======&lt;br /&gt;
Input values ​​in the Debug-Window: &amp;lt;code&amp;gt;CreateObject(&amp;quot;AccUnit.Configurator&amp;quot;).Init VBE.ActiveVBProject&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Result:&lt;br /&gt;
* references to AccUnit and SimplyVBUnit will be aktivated&lt;br /&gt;
* the HelperClass ''TestSuiteStarter'' and the Module ''_AccUnitObjects'' will be created&lt;br /&gt;
&lt;br /&gt;
====== remove ======&lt;br /&gt;
nput values ​​in the Debug-Window: &amp;lt;code&amp;gt;CreateObject(&amp;quot;AccUnit.Configurator&amp;quot;).Remove VBE.ActiveVBProject&amp;lt;/code&amp;gt;&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 18:22:41 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:UsageWithoutAddIn</comments>		</item>
		<item>
			<title>UsageWithoutAddIn</title>
			<link>http://en.accunit.access-codelib.net/UsageWithoutAddIn</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;Created page with 'de:Nutzung ohne Add-In  === Using AccUnit without Add-In ==='&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Nutzung ohne Add-In]]&lt;br /&gt;
&lt;br /&gt;
=== Using AccUnit without Add-In ===&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 18:14:03 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:UsageWithoutAddIn</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, a particular result must be calculated&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Moreover, it is not possible to precisely describe complex applications.&lt;br /&gt;
&lt;br /&gt;
To test software, it is important to split the large complexity of an application into small testable fragments (= functions / procedures). These fragments should then perform exactly ONE task. You then describe:&lt;br /&gt;
&lt;br /&gt;
  - which fragment ( Module, Class, Function, Sub ) do I test&lt;br /&gt;
  - which input value( preconditions ) do I need&lt;br /&gt;
  - which output value ( postconditions ) do I expect&lt;br /&gt;
&lt;br /&gt;
It may be necessary to revise existing sourcecode and split it into smaller testable parts.&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 18:06:53 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, a particular result must be calculated&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Moreover, it is not possible to precisely describe complex applications.&lt;br /&gt;
&lt;br /&gt;
To test software, it is important to split the large complexity of an application into small testable fragments (= functions / procedures). These fragments should then perform exactly ONE task. You then describe:&lt;br /&gt;
&lt;br /&gt;
  - which fragment ( Module, Class, Function, Sub ) do I test&lt;br /&gt;
  - which input value( preconditions ) do I need&lt;br /&gt;
  - which output value ( postconditions ) do I expect&lt;br /&gt;
&lt;br /&gt;
It may be necessary to revise existing sourcecode and to split it into smaller testable parts.&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 18:06:35 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, a particular result must be calculated&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Moreover, it is not possible to precisely describe complex applications.&lt;br /&gt;
&lt;br /&gt;
To test software, it is important to split the large complexity of an application into small testable fragments (= functions / procedures). These fragments should then perform exactly ONE task. You then describe:&lt;br /&gt;
&lt;br /&gt;
  - which fragment ( Module, Class, Function, Sub ) do I test&lt;br /&gt;
  - which input value( preconditions ) do I need&lt;br /&gt;
  - which output value ( postconditions ) do I expect&lt;/div&gt;</description>
			<pubDate>Wed, 23 May 2012 18:02:59 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, a particular result must be calculated&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Moreover, it is not possible to precisely describe complex applications.&lt;br /&gt;
&lt;br /&gt;
To test software, it is important to split the large complexity of an application into small testable fragments (= functions / procedures). These fragments should then perform exactly ONE task. You then describe:&lt;/div&gt;</description>
			<pubDate>Tue, 22 May 2012 22:09:00 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, then a particular result must be calculated&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Moreover, it is not possible to precisely describe complex applications.&lt;br /&gt;
&lt;br /&gt;
To test software, it is important to split the large complexity of an application into small testable fragments (= functions / procedures). These fragments should then perform exactly ONE task. You then describe:&lt;/div&gt;</description>
			<pubDate>Tue, 22 May 2012 22:08:22 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, then a particular result must be calculated&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Moreover, it is not possible to precisely describe complex applications.&lt;br /&gt;
&lt;br /&gt;
To test software, it is important to split the large complexity of an application into small testable fragments (= functions / procedures).&lt;/div&gt;</description>
			<pubDate>Tue, 22 May 2012 22:04:42 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, then a particular result must be calculated&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Moreover, it is not possible to precisely describe complex applications.&lt;/div&gt;</description>
			<pubDate>Tue, 22 May 2012 22:00:53 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, then a particular result must be calculated&amp;quot;).&lt;/div&gt;</description>
			<pubDate>Tue, 22 May 2012 21:49:13 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;br /&gt;
&lt;br /&gt;
Requirements in natural language, however, are not suitable as the basis of a test. (&amp;quot;Well, the thing must not crash&amp;quot; or &amp;quot;If I enter 100, then a particular result to be calculated&amp;quot;).&lt;/div&gt;</description>
			<pubDate>Tue, 22 May 2012 21:48:38 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>Basics</title>
			<link>http://en.accunit.access-codelib.net/Basics</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Grundlagen]]&lt;br /&gt;
Software testing means to determine whether the software meets the requirements.&lt;/div&gt;</description>
			<pubDate>Tue, 22 May 2012 21:43:53 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:Basics</comments>		</item>
		<item>
			<title>User Interface</title>
			<link>http://en.accunit.access-codelib.net/User_Interface</link>
			<description>&lt;p&gt;Sten Schmidt:&amp;#32;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[de:Benutzeroberfläche]] __NOTOC__&lt;br /&gt;
[[Image:AccUnit_VBE.png]]&lt;br /&gt;
&lt;br /&gt;
==== Toolbar ====&lt;br /&gt;
&lt;br /&gt;
[[Image:AccUnit_AddIn_Commandbar_Beschreibung.png]]&lt;br /&gt;
&lt;br /&gt;
==== Menu items ====&lt;br /&gt;
&lt;br /&gt;
[[Image:AccUnit_AddIn_Menu_Tools.png]]&lt;br /&gt;
[[Image:AccUnit_AddIn_Menu_View.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== VBE-Windows ====&lt;br /&gt;
[[Image:AccUnit_AddIn_Testauswahl.png]]&lt;br /&gt;
&lt;br /&gt;
[[Image:AccUnit_AddIn_Testergebnis.png]]&lt;br /&gt;
&lt;br /&gt;
==== Dialogs ====&lt;br /&gt;
[[Image:AccUnit_AddIn_TestImport.png]]&lt;br /&gt;
[[Image:AccUnit_AddIn_TestExport.png]]&lt;br /&gt;
&lt;br /&gt;
[[Image:AccUnit_AddIn_UserSettings.png]]&lt;br /&gt;
&lt;br /&gt;
[[Shortcuts]]&lt;/div&gt;</description>
			<pubDate>Tue, 22 May 2012 18:29:25 GMT</pubDate>			<dc:creator>Sten Schmidt</dc:creator>			<comments>http://en.accunit.access-codelib.net/Talk:User_Interface</comments>		</item>
	</channel>
</rss>