Skip to content

Conversation

@deepikaSingh2711
Copy link
Collaborator

@deepikaSingh2711 deepikaSingh2711 commented Dec 7, 2025

Describe your changes

Automation tests for Multitenant scenario

1)To run Integration test for single tenant use this command
TENANCY_MODEL=single npm run integration-test

2)To run Integration test for Multi tenant (tenant 1) use this command
TENANCY_MODEL=multi TENANT=SDM-DEV-CONSUMER-EU12 npm run integration-test

3)To run Integration test for Multi tenant (tenant 2) use this command
TENANCY_MODEL=multi TENANT=SDMGoogleWorkspaceConsumer npm run integration-test

Any documentation

wiki documentation - https://wiki.one.int.sap/wiki/display/sapecm/Integration+testing+for+SDM+CAP+Plugin

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist before requesting a review

  • I have tested the functionality on my cloud environment.
  • I have provided sufficient automated/ unit tests for the code.
  • I have increased or maintained the test coverage.
  • I have ran integration tests on my cloud environment.
  • I have validated blackduck portal for any vulnerability after my commit.

Upload Screenshots/lists of the scenarios tested

  • I have Uploaded Screenshots or added lists of the scenarios tested in description

single tenant
image

multi tenant 1

Screenshot 2025-12-10 at 1 42 47 PM

multi tenant 2

Screenshot 2025-12-10 at 1 44 49 PM

TENANCY_MODEL=multi TENANT=TENANT2 npm run integration-test
echo ""
echo " All integration tests completed successfully!"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a deploy+integration test job like Java?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is only Integration test job, earlier there was only for single tenant, Now It runs for both single and multitenant

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For single tenant it is a single job, so can we do the same for multitenant as well? Otherwise we will have to track an extra job after PR merge

Comment on lines 178 to 180
echo "========================================"
echo " Running Multi-Tenant Integration Tests (Tenant 1)"
echo "========================================"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please specify the name of the Tenant instead of Tenant 1, like SDM-DEV-CONSUMER-EU12

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem with adding it here is I think it won't be printed if it is being run from local system. So can we print it in the code itself?

yashmeet29
yashmeet29 previously approved these changes Dec 10, 2025
Copy link
Contributor

@rishikunnath2747 rishikunnath2747 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replied to some comments

@deepikaSingh2711 deepikaSingh2711 merged commit c6a4892 into develop Dec 10, 2025
10 checks passed
@deepikaSingh2711 deepikaSingh2711 deleted the multitenantIntegrationTestSetup branch December 10, 2025 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants