Kevin Harvey, on 2008-09-08: > > Well, I ran the tests again and they all ran fine. I don't have an output > anymore, and I'm totally confused. > > My last post was poorly written. The first output should have been '2 test, > 0 failures', and the second '8 tests, 6 failures', The test failures were > the anticipated result. In Aspeli's book he has us write the test first, > confirm that the tests fail, then add the functionality to satisfy the > tests. My problem is that as I added subsequent tests to my test_setup.py > file, then ran 'bin/instance test -s optilux.policy', the new test didn't > register. > > *I think* my question is: do you have to reinstall the product (or rerun > buildout, or refresh in any way) after you add new tests to test_setup.py?
No. Just double check that you have actually saved the test_setup.py file. ;-) > Here's the output of the functioning tests. > (...) > Installing PluggableAuthService ... > /home/harveyk/Plone/optilux/parts/plone/GenericSetup/registry.py:744: > DeprecationWarning: Version for profile PluggableAuthService:simple taken > from version.txt. This is deprecated behaviour and will be removed in > GenericSetup 1.5: please specify the version in metadata.xml. > DeprecationWarning) > /home/harveyk/Plone/optilux/parts/plone/GenericSetup/registry.py:744: > DeprecationWarning: Version for profile PluggableAuthService:empty taken > from version.txt. This is deprecated behaviour and will be removed in > GenericSetup 1.5: please specify the version in metadata.xml. > DeprecationWarning) This is just a warning for a different product, which you can ignore. The same is true for the other warnings. -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ "This is your day, don't let them take it away." [Barlow Girl] _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
