refactor(schema): add describe blocks in tests for each kind of schema

[muntaxir4]

User description

Description

@keyshade/schema:

• Create describe blocks to contain tests for each kind of schema. Removed old test comments.
• Change count type from string to number in secret and variable RollbackResponses.

Developer's checklist

• My PR follows the style guidelines of this project
• I have performed a self-check on my work

If changes are made in the code:

• I have followed the coding guidelines
• My changes in code generate no new warnings
• My changes are breaking another fix/feature of the project
• I have added test cases to show that my feature works
• I have added relevant screenshots in my PR
• There are no UI/UX issues

Documentation Update

• This PR requires an update to the documentation at docs.keyshade.xyz
• I have made the necessary updates to the documentation, or no documentation changes are required.

---

PR Type

Tests

---

Description

• Refactored all schema tests by introducing describe blocks for better organization and readability.
• Grouped existing test cases under appropriate describe blocks to enhance test structure.
• Added missing assertions and validation checks in some test files.
• Removed old test comments to clean up the test files.

---

Changes walkthrough 📝

Relevant files

Tests

13 files secret.spec.ts Refactor tests with `describe` blocks for schema organization. packages/schema/tests/secret.spec.ts Added describe blocks to organize tests by schema type. Grouped existing tests under new describe blocks for better structure. Ensured all test cases are wrapped within appropriate describe blocks. +428/-413 workspace.spec.ts Organize workspace tests using `describe` blocks.                packages/schema/tests/workspace.spec.ts Introduced describe blocks for each schema test group. Organized tests into logical sections using describe. Enhanced test readability and structure with describe blocks. +410/-378 workspace-role.spec.ts Categorize workspace role tests with `describe` blocks.    packages/schema/tests/workspace-role.spec.ts Added describe blocks to categorize tests by schema. Improved test organization with describe blocks. Structured tests for better clarity and maintenance. +341/-330 integration.spec.ts Structure integration tests using `describe` blocks.          packages/schema/tests/integration.spec.ts Implemented describe blocks for integration schema tests. Structured tests into sections using describe. Enhanced test clarity and organization with describe blocks. +326/-315 auth.spec.ts Organize auth tests with `describe` blocks.                            packages/schema/tests/auth.spec.ts Introduced describe blocks for auth schema tests. Organized tests into sections using describe. Improved test readability and structure with describe blocks. +35/-33  workspace-membership.spec.ts Refactor tests with `describe` blocks for schema organization packages/schema/tests/workspace-membership.spec.ts Introduced describe blocks to organize tests by schema type. Enhanced test readability by grouping related tests. Added missing assertions for test validations. +334/-313 variable.spec.ts Organize variable schema tests with `describe` blocks        packages/schema/tests/variable.spec.ts Added describe blocks to group tests by schema type. Improved test structure and readability. Included additional assertions for validation checks. +363/-352 api-key.spec.ts Refactor API key tests using `describe` blocks                      packages/schema/tests/api-key.spec.ts Grouped tests with describe blocks for better organization. Enhanced test clarity and structure. Added assertions for validation results. +280/-266 environment.spec.ts Organize environment schema tests with `describe` blocks  packages/schema/tests/environment.spec.ts Utilized describe blocks to categorize tests by schema. Improved test organization and readability. Added assertions for validation outcomes. +265/-254 user.spec.ts Refactor user schema tests with `describe` blocks                packages/schema/tests/user.spec.ts Implemented describe blocks to organize user schema tests. Enhanced test readability and structure. Added assertions for validation checks. +207/-197 pagination.spec.ts Refactor pagination schema tests with describe blocks        packages/schema/tests/pagination.spec.ts Added describe blocks to group tests for PageRequestSchema, PageResponseSchema, ResponseErrorSchema, and ClientResponseSchema. Organized existing test cases under their respective describe blocks. Removed old test comments and improved test structure. +150/-146 event.spec.ts Refactor event schema tests with describe blocks                  packages/schema/tests/event.spec.ts Introduced describe blocks for GetEventsRequestSchema and GetEventsResponseSchema tests. Structured existing test cases within the new describe blocks. Enhanced test organization and readability. +110/-108 enums.test.ts Refactor enum tests with describe blocks                                  packages/schema/tests/enums.test.ts Added describe blocks for each enum type test. Organized tests for integrationTypeEnum, expiresAfterEnum, rotateAfterEnum, eventSourceEnum, eventTriggererEnum, eventSeverityEnum, eventTypeEnum, authorityEnum, and projectAccessLevelEnum. Improved test clarity and structure. +136/-118

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Code Organization The test file contains a large number of test cases that could benefit from further grouping and organization. Consider splitting some of the larger test groups into smaller, more focused test suites.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	✅ Fix incorrect type validation in schema test where a numeric value is validated as string Suggestion Impact: The suggestion impacted the commit by changing the type of 'count' from a string to a number in the test case for RollBackSecretResponseSchema. code diff: - count: '1' + count: 1 The test case for RollBackSecretResponseSchema validates that count is a string, but this seems incorrect as count should typically be a number. Consider updating the schema and test to use a numeric type instead. packages/schema/tests/secret.spec.ts [294-297] const result = RollBackSecretResponseSchema.safeParse({ - count: '1' + count: 1 }) expect(result.success).toBe(true) Apply this suggestion Suggestion importance[1-10]: 8 Why: The suggestion identifies a potential data type inconsistency where count is validated as a string ('1') when it should logically be a number (1). This could prevent proper type safety and lead to runtime issues.	8

💡 Need additional feedback ? start a PR chat

[rajdip-b]

🎉 This PR is included in version 2.9.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀