History for February followup sprint setup

changed:
-
<ol>
<li>
Go ahead and make sure you've done the January [Sprint setup].
</li>

<li>
In your test Plone site, be sure to add PloneHelpCenter as a product in your plone_control_panel.
</li>

<li>
See if you understand what we think we understand about the desired [Target PHC Workflow].
</li>

<li>
Setup <a href="/Members/tbryan/unittest_talk">PloneTestCase</a> like Tom Bryan showed us at the <a href="/Members/tbryan/unittest_talk">last TriZPUG meeting</a>:
<p>
</p><ul>
<li>
Export <a href="http://cvs.sourceforge.net/viewcvs.py/collective/ZopeTestCase/">ZopeTestCase</a> from the Collective&nbsp; and place in your $ZOPE_HOME/lib/python/Testing (not Products!)
</li>

<li>
Put <a href="http://zope.org/Members/shh/Tutorial/test.py">test.py</a> in your $ZOPE_HOME/bin (overwriting the one that is there).
</li>

<li>
Linux: make test.py script executable. Make sure the first line reads: <pre>#!/usr/bin/env /path/to/zope's/python2.3/bin/python<br></pre>
</li>

<li>
Export <a href="http://cvs.sourceforge.net/viewcvs.py/collective/PloneTestCase/">PloneTestCase</a> from the Collective and place in your $INSTANCE_HOME Products directory.
</li>

<li>
<code>cd $INSTANCE_HOME</code>
</li>

<li>
Linux:
<pre>$ZOPE_HOME/bin/test.py -v \<br>--config-file etc/zope.conf \<br>--libdir Products/PloneProductToTest<br></pre>
</li>

<li>
Windows:
<pre>python $ZOPE_HOME/bin/test.py -v \<br>--config-file etc/zope.conf \<br>--libdir Products/PloneProductToTest<br></pre>
</li>
</ul>
</li>
<li>
In $INSTANCE_HOME/Products/PloneHelpCenter/Testing/__init.py__, uncomment the three lines to CreateTestData in portal_migration.
</li>
<li>
In portal_migrations/Setup, under "PloneHelpCenter Test Data," check
Create Test Data and then click "Update." All the other PHC test data
shown (Create Test Users,
Create Test PloneHelpCenter,
Create Test Tutorials,
and Create Test Howtos) will be created by simply checking Create Test
Data.
</li>
</ol>