Task #4003
closed
Uncouple pulpcore tests from plugins by creating a test plugin
0%
Description
Some of pulpcore tests rely on the pulp_file[0] and pulp_rpm[1] plugins. The problem is that this won't scale. As we add more features to pulpcore that are only used by a subset of plugins, this design will require us to install more plugins into pulpcore's CI.
We should decouple pulpcore tests from requiring plugins by introducing a test plugin that tests can use. This test plugin would contain a superset of all features that pulpcore provides.
Alternatively we could maybe leverage the plugin template to be this test plugin.
[0] https://github.com/pulp/pulpcore/tree/master/pulpcore/tests/functional/api/using_plugin
[1] https://github.com/pulp/pulpcore/blob/master/pulpcore/tests/functional/api/using_plugin/test_sync_multiple_plugins.py
Updated by amacdona@redhat.com almost 6 years ago
Since the plugin_template includes tests, it would be really convenient if we use that.
Updated by bmbouter almost 6 years ago
How do you imagine the TestPlugin working? Would it actually sync and publish content?
Updated by daviddavis over 5 years ago
- Subject changed from Uncouple the pulpcore tests from pulp_file by creating a TestPlugin to Uncouple pulpcore tests from plugins by creating a test plugin
- Description updated (diff)
Updated by daviddavis about 4 years ago
- Status changed from NEW to CLOSED - WONTFIX
.