On 12/28/12, Steffen Hoffmann <hoff...@web.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, >
:) > here are some recent findings, that other plugin authors/maintainers may > find helpful as well: > > I noticed that component names in the 'enable' attribute to > trac.test.EnvironmentStub are required with correct casing for 0.11.x, > while they're accepted regardless of character casing from Trac 0.12 > onwards. > yes. is_component_enabled changed from one version to the other . Needless to say that I prefer current approach since it's exactly like Trac's. Besides , there are some other hacks needed for enabling / disabling components at run time . That's why I extended EnvironmentStub class https://bitbucket.org/olemis/trac-gviz/src/58ba7fb58a7347d05a41eb7840ae3ac13678a598/trac-dev/gviz/tracgviz/testing/__init__.py?at=default ;) > I've found that the line > packages = find_packages(exclude=['*.tests']) > in Trac's setup.py prevents all the functional test methods from > becoming packaged and installed. So no wonder, that any import from > trac.tests or below must fail. > > Question: Does the above mean, that we have to include the functional > tester stuff in each Trac plugin separately? At least I can't see > another straight way. > No . My interpretation is that if you want to run tests for your plugins then you should download an sdist package (or check out source using svn ;) rather than bdist and then install it via setup.py develop ... be it inside a virtualenv or not ;) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
