Feature Request: End-to-End Testing with Real Pepr Modules

[cmwylie19]

Is your feature request related to a problem? Please describe.

To enhance our testing suite and ensure backward compatibility with each new feature and release, we propose the creation of end-to-end tests that utilize actual Pepr modules. This approach aims to move beyond relying solely on basic or placeholder modules (such as hello-pepr) for testing.

Background

Currently, our end-to-end testing primarily leverages simplistic modules, which might not cover the full spectrum of use cases and functionalities that real-world Pepr modules encapsulate. This scenario can potentially lead to gaps in our testing, risking the introduction of changes that break backward compatibility without detection. Secondly, it relies on hello-pepr constantly growing which is not ideal.

Benefits

• Increased Confidence: Developers and users alike can have increased confidence in new releases, knowing they have been thoroughly tested against real-world scenarios.
• Early Detection: Potential issues and backward compatibility breaks can be detected early in the development process, well before reaching production.
• Streamlined Development: The development process can be streamlined as potential issues are caught early, reducing the need for hotfixes and patches post-release.

Describe the solution you'd like

• Given we have enhanced our testing suite with a diverse set of Pepr modules that and tests that guarantee backwards compatibility
• When a PR is create with a new feature
• Then all existing functionality is tested and passing before the pipeline goes green.

Describe alternatives you've considered

(optional) A clear and concise description of any alternative solutions or features you've considered.

Additional context

We welcome feedback and suggestions from the community on this proposal, including additional considerations for module selection, test scenarios, and integration into our CI pipeline.

Related to #301