New Question on Plone Community - Bin/test with no parameters

1 view
Skip to first unread message

Plone Community

unread,
Oct 24, 2016, 4:48:13 PM10/24/16
to eea-facete...@googlegroups.com
Plese reply at: http://community.plone.org/t/bin-test-with-no-parameters/2927 @alberto wrote: I just installed Plone 5.0.6 using the Vagrant installer. After the installation, the first thing I do is to ssh the box, go to the Plone buildout dir and run bin/test The output shows 2 failures and 2 errors from plone.reload.tests.test_code.TestTimes and plone.reload.tests.test_code.TestSearch. Is it expected? The goal here is to be able to test the whole Plone install if we want to upgrade any third-party add-on. For example, we might use eea.facetednavigation as a requirement for our add-on. Our add-on was developed using eea.facetednavigation 9.2. Now that 10.0 was released, we would like to pin it to 10.0 (in setup.py or buildout.cfg), but we thought about running the tests for all add-ons to see if the upgrade in that specific one would break anything. Does that make sense? If so, what is the recommended way to do it? Posts: 1 Participants: 1 Read full topic Plese reply at: http://community.plone.org/t/bin-test-with-no-parameters/2927
Reply all
Reply to author
Forward
0 new messages