Rbsdms 114 feature#536
Open
akgarg06 wants to merge 16 commits into
Open
Conversation
…into RBSDMS-114-feature
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your changes
Any documentation
Adds integration tests for creating attachments directly on active (published) entities, without going through the draft flow. Tests cover single-tenant and multi-tenant scenarios across named user and technical user token flows.
New test files:
IntegrationTest_ActiveEntity — core active-entity tests (16 test cases)
IntegrationTest_ActiveEntity_MultipleFacet — same tests across all 3 facets (attachments, references, footnotes)
IntegrationTest_ActiveEntity_Chapters_MultipleFacet — same tests on nested Chapters entities across all 3 facets
Workflow updates (6 files):
Added active-entity-test as a dedicated job in all integration test workflows (single-tenant and multi-tenant)
The job runs after the main integration-test slot to avoid fixture conflicts, and before the versioned/virus-scan slots
Tests run in parallel across namedUser / technicalUser token flows and TENANT1 / TENANT2 (multi-tenant)
Type of change
Checklist before requesting a review
Upload Screenshots/lists of the scenarios tested
Individual test cases run
Single Tenant : https://github.com/cap-java/sdm/actions/runs/29014326579
Multi Tenant : https://github.com/cap-java/sdm/actions/runs/29013763522