Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write a Karate/Postman Test to verify that OSGI plugins can be installed and then reloaded #31323

Open
fabrizzio-dotCMS opened this issue Feb 7, 2025 · 0 comments

Comments

@fabrizzio-dotCMS
Copy link
Contributor

fabrizzio-dotCMS commented Feb 7, 2025

Parent Issue

#31185

Task

Issue Description:

Given the problem encountered in ticket 31185, where installing an OSGi plugin containing a REST resource caused our Jersey container to become unusable due to a recurring exception, we want to create a Karate or Postman test to ensure stability.

This will help confirm that our container remains stable even after multiple plugin lifecycle operations.

Proposed Objective

Same as Parent Issue

Proposed Priority

Priority 2 - Important

Acceptance Criteria

This test should validate that we can:
1. Install OSGi plugins,
2. Stop them,
3. Restart them, and
4. Verify that the Jersey container remains functional after a few consecutive cycles, properly serving content from other endpoints and maintaining expected behavior.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

@fabrizzio-dotCMS fabrizzio-dotCMS changed the title Write a Karate/Postman Test to verify that OSGI plugins can installed and reladed Write a Karate/Postman Test to verify that OSGI plugins can be installed and then reloaded Feb 7, 2025
@nollymar nollymar moved this from New to Next 1-3 Sprints in dotCMS - Product Planning Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Next 1-3 Sprints
Development

No branches or pull requests

1 participant