Consider auto-generating default tests for plugin types

[ogajduse]

Summary

PR #57 introduces auto-generation of default tests for PulpPlugin:

# All Pulp plugins use ci.yml from plugin_template
if not self.tests:
    self.tests = {'github': {'Python': 'ci.yml'}}

This allows config.yaml to omit the tests field, reducing repetition and maintenance burden.

Proposal

Apply similar auto-generation to other plugin types where tests follow predictable patterns:

ForemanPlugin

• 38 of 47 plugins define tests in config.yaml
• Many follow patterns like {Ruby: ruby_tests.yml, JavaScript: js_tests.yml}
• Could auto-generate common patterns when not explicitly defined

Potential Benefits

• DRY principle: Reduces repetitive configuration
• Maintainability: Fewer lines to update when patterns change
• Consistency: Ensures new plugins get sensible defaults
• Opt-out friendly: Explicit tests: {} can override defaults

Considerations

• Need to identify stable test patterns for each type
• Must preserve ability to explicitly define no tests
• Could start conservatively (one type at a time)

Questions

1. Are there stable test patterns for ForemanPlugin worth encoding?
2. Should SmartProxyPlugin/HammerPlugin adopt tests.github defaults alongside puppet_acceptance_tests?
3. Would this change align with project maintainers' philosophy?

Related to PR #57 discussion: #57 (comment)

[ekohl]

ForemanPlugin

* 38 of 47 plugins define tests in `config.yaml`
* Many follow patterns like `{Ruby: ruby_tests.yml, JavaScript: js_tests.yml}`
* Could auto-generate common patterns when not explicitly defined

There's too much variance so IMHO it doesn't make sense to now. https://github.com/theforeman/foreman_plugin_template doesn't even have it because theforeman/foreman_plugin_template#62 is still open. Pulp is different because the template contains a single best practice.

I'd still like it, but then I think what needs to happen is:

• Align on a best practice by having it in the template
• Align all plugins on that practice
• Make the default in this repo match the best practice, allowing to opt out where it's different.

[ogajduse]

Agreed, but that's a lot of work and a lot of community coordination. :) Perhaps, I could get back to it one day.

[ekohl]

Guess why we ended up with the current implementation ;)