We have three applications (A, B, and C) under the ABC origination. Currently, all test cases for each individual rule type is created in a single ruleset version ABC_TC:01-01-01 and shared across all applications. From a best-practice perspective, should we:
Continue using a single shared test ruleset for all applications?
Create separate test rulesets for each application (e.g., A_Test, B_Test, C_Test)?
Should we also increment the test ruleset version for every release?
Also for automation test suite, should we use the same ruleset version?
Please advise on the recommended approach considering maintainability, versioning, and deployment alignment.
@Siva Sankar You can keep a common naming pattern, but it is better to have separate test rulesets per application (for example, A_TC, B_TC, C_TC) so that tests stay aligned with each app’s rules and deployments. A shared test ruleset like ABC_TC is fine only for truly common, reusable tests, and even then it should be referenced as a separate “common test” ruleset, not the only one. Yes, you should version your test rulesets along with each application release (for example, when A goes from 01-01 to 01-02, move A_TC from 01-01-01 to 01-02-01) so that test changes track code changes. This helps you rerun the exact tests used for an older release if you ever need to. For automation test suites, use the same test ruleset and version that belongs to that release, so functional tests, regression suites, and API tests all stay in sync. This structure makes deployments cleaner, avoids test conflicts between applications, and improves long-term maintainability.