Make formatter.suite available to plugins

[Ryan J Ollos]

formatter.suite​ is useful for writing macro test cases, as seen in macros.py​. However, from trac.wiki.tests import formatter fails in a plugin when the Trac is not installed in develop (editable) mode.

[Ryan J Ollos]

Edit: Created #12487 for proposed changes.

[Ryan J Ollos]

The only way I see to solve this is to either add trac.wiki.tests.formatter directly to the distributed package, or move the code in that file. I considered moving to trac.test, but maybe it would make sense to move to trac.wiki.test: log:rjollos.git:t12233_formatter_test_suite.

[Jun Omae]

Why HelloWorldMacro is moved to trac.wiki.test package? I think WikiTestCase, subclasses of the WikiTestCase and wikisyntax_test_suite() only should be moved.

[Ryan J Ollos]

WikiTestCase uses HelloWorldMacro to create an environment: trunk/trac/wiki/tests/formatter.py@14791:161-164#L143​.

[Jun Omae]

I think we should allow to specify components to enable for WikiTestCase and wikisyntax_test_suite. Otherwise, it wouldn't be useful to test for plugins.

[Ryan J Ollos]

I found we can use Environment.enable_component to enable components in the setup function that is passed to trac.wiki.test.wikisyntax_test_suite. This hadn't worked for me in the past, but the problem was that I specified a component rule rather than a module name (e.g. tractags.* rather than tractags).

Proposed changes in log:rjollos.git:t12233_formatter_test_suite.2. See ​th:#12788 for a patch that uses trac.wiki.test.wikisyntax_test_suite in the ​TagsPlugin codebase.