Move application management integration test cases for corresponding test classes

[sadilchamishka]

$subject

Summary by CodeRabbit

• Tests
  • Reorganized test configuration to reallocate test cases across different test suites, optimizing test execution management.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 198f9ec4-e76a-414f-b097-9f5551b858b1

📥 Commits

Reviewing files that changed from the base of the PR and between 77c0da8 and 40aac63.

📒 Files selected for processing (1)

• modules/integration/tests-integration/tests-backend/src/test/resources/testng.xml

---

Walkthrough

TestNG configuration reorganization: two test cases (ApplicationTemplateMgtTestCase and ApplicationPatchTest) were relocated between test suites, moving from is-tests-saas-app-creation to is-tests-default-configuration and is-test-rest-api respectively.

Changes

Cohort / File(s)	Summary
TestNG Configuration modules/integration/tests-integration/tests-backend/src/test/resources/testng.xml	Reorganized test case suite assignments: migrated ApplicationTemplateMgtTestCase to is-tests-default-configuration and ApplicationPatchTest to is-test-rest-api, removing both from is-tests-saas-app-creation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Tests hop to new homes so fine,
From SaaS to REST, default lines align,
Configuration dances, suite by suite,
Templates and patches find retreat! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly describes the main change: moving application management integration test cases to their corresponding test classes, which aligns with the file changes in testng.xml.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch refactor-integration-test-of-application-mgt

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/23939691514

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

This PR reorganizes TestNG suite composition for application management-related integration tests, relocating specific test classes to more appropriate <test> blocks in the main integration TestNG suite.

Changes:

• Moved ApplicationTemplateMgtTestCase into the is-tests-default-configuration block.
• Moved ApplicationPatchTest into the main server application management REST API test block.
• Removed both classes from is-tests-saas-app-creation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

is-tests-saas-app-creation now contains only SaasAppCreationInitializerTestCase. Since that class enables a config, restarts the server, and restores the config in @AfterTest, this block becomes an expensive no-op (extra restart + potential flakiness) with no tests benefiting from the enabled setting. Consider removing this <test> block entirely, or keep at least one test class in this block that actually requires enable_app_creation=true.

[Copilot]

The PR description is currently the placeholder $subject, which doesn’t explain the motivation/impact of moving these test classes between TestNG blocks (e.g., ordering/config assumptions, CI runtime impact). Please update the PR description to briefly state why the move is needed and what suite(s) these tests should belong to.

[sadilchamishka]

https://github.com/sadilchamishka/product-is/actions/runs/23939702462

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/23939691514
Status: failure