<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.sugarlabs.org/index.php?action=history&amp;feed=atom&amp;title=Automated_Activity_Testing</id>
	<title>Automated Activity Testing - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.sugarlabs.org/index.php?action=history&amp;feed=atom&amp;title=Automated_Activity_Testing"/>
	<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Automated_Activity_Testing&amp;action=history"/>
	<updated>2026-05-29T21:32:43Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Automated_Activity_Testing&amp;diff=91117&amp;oldid=prev</id>
		<title>Svineet: Created page with &quot;Sugar toolkit now has support for Automated Activity Testing. This page lists the various aspects of Activity Testing.  The tests are supposed to be organized into the &lt;tt&gt;tes...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Automated_Activity_Testing&amp;diff=91117&amp;oldid=prev"/>
		<updated>2014-01-07T15:52:56Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Sugar toolkit now has support for Automated Activity Testing. This page lists the various aspects of Activity Testing.  The tests are supposed to be organized into the &amp;lt;tt&amp;gt;tes...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Sugar toolkit now has support for Automated Activity Testing. This page lists the various aspects of Activity Testing.&lt;br /&gt;
&lt;br /&gt;
The tests are supposed to be organized into the &amp;lt;tt&amp;gt;tests&amp;lt;/tt&amp;gt; directory inside the bundle path. Inside this there are two subdirectories - &amp;lt;tt&amp;gt;integration&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;unit&amp;lt;/tt&amp;gt; which contain UI and unit tests respectively. Both of them contain test files starting with &amp;lt;tt&amp;gt;test_&amp;lt;/tt&amp;gt;. So the directory structure can be summarized as follows - &lt;br /&gt;
&lt;br /&gt;
 tests/&lt;br /&gt;
  |-integration/&lt;br /&gt;
   |test_operations.py&lt;br /&gt;
  |-unit/&lt;br /&gt;
   |test_functions.py&lt;br /&gt;
&lt;br /&gt;
Only files beginning with test_ will be executed.&lt;br /&gt;
&lt;br /&gt;
These tests can be executed using &amp;lt;code&amp;gt;./setup.py check&amp;lt;/code&amp;gt;&lt;br /&gt;
setup.py also takes a optional argument of which set of tests to run - &lt;br /&gt;
 &lt;br /&gt;
 ./setup.py check integration&lt;br /&gt;
 ./setup.py check unit&lt;br /&gt;
&lt;br /&gt;
See the example [https://git.sugarlabs.org/~svineet33/calculate/svineet33s-calculate/commit/8cdf4f6d556b58379081a1f339513e0636506e5e tests] inside Calculate.&lt;/div&gt;</summary>
		<author><name>Svineet</name></author>
	</entry>
</feed>