Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test: src/graphql/types/Venue/creator.ts #3151

Conversation

NishantSinghhhhh
Copy link

@NishantSinghhhhh NishantSinghhhhh commented Feb 5, 2025

What kind of change does this PR introduce?
Test Implementation and Code Quality Enhancement

Issue Number:
Fixes #3076

Snapshots/Videos:
N/A - Test implementation

If relevant, did you update the documentation?
No documentation update required as this is a test implementation.

Summary
This PR implements comprehensive test coverage for the Venue Creator resolver in the GraphQL API. The changes include:

  • Implementation of unit tests for the venue creator field resolver
  • Coverage of authentication and authorization scenarios
  • Testing of edge cases and error handling
  • Proper typing of test context objects to maintain code quality
  • Implementation of mocking strategies for database interactions

Key testing areas include:

  • Authentication validation
  • Authorization checks for system and organization administrators
  • Creator resolution logic
  • Error handling for corrupted or missing data
  • Edge cases around membership roles and permissions

The test suite ensures robust functionality of the venue creator resolver while maintaining high code quality standards.

Does this PR introduce a breaking change?
No

Checklist

CodeRabbit AI Review

  • I have reviewed and addressed all critical issues flagged by CodeRabbit AI
  • I have implemented proper type definitions replacing any types
  • I have documented code structure and test cases clearly

Test Coverage

  • I have written comprehensive tests for the venue creator resolver
  • I have verified that test coverage meets or exceeds 95%
  • I have run the test suite locally and all tests pass

Other information

  • Test implementation follows Vitest testing patterns
  • Includes proper mocking of database interactions
  • Maintains type safety throughout the implementation
  • Follows project coding standards and best practices

Have you read the contributing guide?
Yes

Summary by CodeRabbit

  • Tests
    • Added a comprehensive suite of tests ensuring robust authentication and authorization when accessing venue creator details.
    • Validated various scenarios including unauthenticated access, role-based restrictions, and handling of absent or matching creator information.
    • Introduced new type definitions to enhance the structure of the testing context.

Signed-off-by: NishantSinghhhhh <[email protected]>
Signed-off-by: NishantSinghhhhh <[email protected]>
Signed-off-by: NishantSinghhhhh <[email protected]>
Signed-off-by: NishantSinghhhhh <[email protected]>
Signed-off-by: NishantSinghhhhh <[email protected]>
Signed-off-by: NishantSinghhhhh <[email protected]>
Signed-off-by: NishantSinghhhhh <[email protected]>
Copy link

coderabbitai bot commented Feb 5, 2025

Warning

Rate limit exceeded

@NishantSinghhhhh has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 39 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e8b0542 and 607d7b3.

📒 Files selected for processing (1)
  • test/graphql/types/Venue/creator.test.ts (1 hunks)

Walkthrough

The changes introduce a new test suite for the resolveCreator function within the GraphQL resolver for venues. It includes new type definitions for context and parent objects, and the tests validate the function's authentication and authorization logic. Various scenarios are covered, such as unauthenticated access, role-based access control, and different conditions for creator IDs, ensuring comprehensive error handling and data retrieval.

Changes

File Path Change Summary
test/graphql/types/Venue/creator.test.ts Added a comprehensive test suite for resolveCreator with multiple test cases; introduced new type definitions (ResolverContext, CurrentClient, TestContext, VenueParent) for context setup and resolver validation.

Sequence Diagram(s)

sequenceDiagram
    participant Test as TestSuite
    participant Resolver as resolveCreator
    participant DB as Database
    participant Logger as Logger

    Test->>Resolver: Call resolveCreator(context, parent)
    alt Unauthenticated or Missing ID
        Resolver-->>Test: Throw unauthenticated error
    else Unauthorized
        Resolver-->>Test: Throw unauthorized_action error
    else Creator ID is null
        Resolver-->>Test: Return null
    else Creator ID matches current user
        Resolver-->>Test: Return current user
    else Valid creator ID mismatch
        Resolver->>DB: Fetch creator details
        DB-->>Resolver: Return creator details
        alt Creator not found
            Resolver->>Logger: Log error
            Resolver-->>Test: Throw unexpected error
        else Creator found
            Resolver-->>Test: Return creator details
        end
    end
Loading

Assessment against linked issues

Objective Addressed Explanation
Achieve 100% test coverage for resolver in creator.ts [#3076]

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

github-actions bot commented Feb 5, 2025

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 4

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b137692 and 565e329.

📒 Files selected for processing (2)
  • test/graphql/types/Venue/creator.test.ts (1 hunks)
  • test/routes/graphql/gql.tada.d.ts (1 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
test/graphql/types/Venue/creator.test.ts

[error] 29-29: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


[error] 30-30: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


[error] 31-31: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (5)
test/graphql/types/Venue/creator.test.ts (4)

7-40: LGTM! Well-structured type definitions.

The type definitions and interfaces are well-organized and provide good type safety for the test suite.

🧰 Tools
🪛 Biome (1.9.4)

[error] 29-29: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


[error] 30-30: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


[error] 31-31: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


42-128: LGTM! Robust authentication and authorization implementation.

The resolver properly implements authentication and authorization checks, handles edge cases, and follows security best practices.


130-167: LGTM! Well-structured test setup.

The test setup provides a comprehensive mock structure with proper initialization of test context and mock data.


169-378: LGTM! Comprehensive test coverage.

The test suite provides excellent coverage of authentication, authorization, and edge cases. The tests are well-organized and use clear assertions.

test/routes/graphql/gql.tada.d.ts (1)

1-218: LGTM! Auto-generated GraphQL schema types.

This auto-generated file provides proper type definitions for the GraphQL schema.

test/graphql/types/Venue/creator.test.ts Show resolved Hide resolved
test/graphql/types/Venue/creator.test.ts Outdated Show resolved Hide resolved
test/graphql/types/Venue/creator.test.ts Show resolved Hide resolved
test/graphql/types/Venue/creator.test.ts Show resolved Hide resolved
Copy link

github-actions bot commented Feb 5, 2025

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

github-actions bot commented Feb 5, 2025

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

@Cioppolo14
Copy link
Contributor

@NishantSinghhhhh There isn’t an issue assigned to you for this PR. Please follow the guidelines in our PR_GUIDELINES.md file. We have the procedures in place so that everyone has a fair chance of contributing. I will be closing this pull request. Please follow the procedures and resubmit when ready.

@Cioppolo14 Cioppolo14 closed this Feb 6, 2025
@NishantSinghhhhh
Copy link
Author

Screenshot_20250206-084845.png

, @Cioppolo14 , I mean this is not the case I believe, because it is assigned to me

@NishantSinghhhhh
Copy link
Author

@palisadoes , can you please open this PR again, as I need to pass the tests so that I can merge it today itself

@palisadoes palisadoes reopened this Feb 6, 2025
coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 6, 2025
Signed-off-by: NishantSinghhhhh <[email protected]>
Signed-off-by: NishantSinghhhhh <[email protected]>
@NishantSinghhhhh
Copy link
Author

@coderabbitai full review

Copy link

coderabbitai bot commented Feb 6, 2025

✅ Actions performed

Full review triggered.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 38322df and 220b8b0.

📒 Files selected for processing (1)
  • test/graphql/types/Venue/creator.test.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Validate CodeRabbit Approval
🔇 Additional comments (6)
test/graphql/types/Venue/creator.test.ts (6)

8-42: LGTM! Well-structured type definitions.

The type definitions are clear, well-organized, and follow TypeScript best practices.


50-54: Add descriptive error messages for better debugging.

The error messages could be more descriptive to help with debugging.

 throw new TalawaGraphQLError({
   extensions: {
     code: "unauthenticated",
+    message: "User must be authenticated to access venue creator",
   },
 });

Also applies to: 73-77, 88-92, 104-108, 121-125


100-100: Implement type guards for safer type casting.

The double cast (as unknown as typeof User) bypasses TypeScript's type checking. Consider implementing type guards to ensure runtime type safety.

#!/bin/bash
# Search for User type definition
ast-grep --pattern 'type User = {
  $$$
}'

Also applies to: 128-128


131-182: LGTM! Well-structured test setup.

The test setup is comprehensive, with properly typed mock objects and follows testing best practices.


202-218: Remove duplicate test case.

This test case is identical to the previous test for unauthenticated users (lines 184-200).

-  it("should throw unauthenticated error if user is not logged in", async () => {
-    const testCtx = {
-      ...ctx,
-      currentClient: {
-        isAuthenticated: false,
-        user: undefined,
-      },
-    } as unknown as ResolverContext;
-
-    await expect(async () => {
-      await resolveCreator(mockVenue, {}, testCtx);
-    }).rejects.toThrow(
-      new TalawaGraphQLError({
-        extensions: { code: "unauthenticated" },
-      }),
-    );
-  });

184-394: LGTM! Comprehensive test coverage.

The test suite thoroughly covers various scenarios including:

  • Authentication checks
  • Authorization rules
  • Edge cases
  • Error handling

test/graphql/types/Venue/creator.test.ts Outdated Show resolved Hide resolved
coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 6, 2025
Signed-off-by: NishantSinghhhhh <[email protected]>
@NishantSinghhhhh
Copy link
Author

@palisadoes , I have added all the tests for this component , can you tell me what more changes do I need to make so that I can make this PR mergeable

Copy link

github-actions bot commented Feb 6, 2025

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

@PalisadoesFoundation PalisadoesFoundation deleted a comment from github-actions bot Feb 6, 2025
@PalisadoesFoundation PalisadoesFoundation deleted a comment from codecov bot Feb 6, 2025
@PalisadoesFoundation PalisadoesFoundation deleted a comment from github-actions bot Feb 6, 2025
@PalisadoesFoundation PalisadoesFoundation deleted a comment from github-actions bot Feb 6, 2025
@PalisadoesFoundation PalisadoesFoundation deleted a comment from github-actions bot Feb 6, 2025
@NishantSinghhhhh
Copy link
Author

@coderabbitai full review

Copy link

coderabbitai bot commented Feb 6, 2025

✅ Actions performed

Full review triggered.

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 6, 2025
Signed-off-by: NishantSinghhhhh <[email protected]>
Signed-off-by: NishantSinghhhhh <[email protected]>
Copy link

github-actions bot commented Feb 6, 2025

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 5

♻️ Duplicate comments (3)
test/graphql/types/Venue/creator.test.ts (3)

98-98: ⚠️ Potential issue

Add runtime type validation before type casting.

The type casting to typeof User is unsafe without runtime validation. Consider adding type guards.

Also applies to: 126-127


48-52: 🧹 Nitpick (assertive)

Add descriptive error messages for better debugging.

The error messages should be more descriptive to help with debugging.

Also applies to: 71-75, 86-90, 102-106, 119-123


200-216: ⚠️ Potential issue

Remove duplicate test case.

This test case is a duplicate of the previous test for unauthenticated users (lines 182-198).

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7be2cb5 and e8b0542.

📒 Files selected for processing (1)
  • test/graphql/types/Venue/creator.test.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Run tests for talawa api
  • GitHub Check: Analyse Code With CodeQL (typescript)

test/graphql/types/Venue/creator.test.ts Show resolved Hide resolved
test/graphql/types/Venue/creator.test.ts Show resolved Hide resolved
test/graphql/types/Venue/creator.test.ts Show resolved Hide resolved
test/graphql/types/Venue/creator.test.ts Show resolved Hide resolved
test/graphql/types/Venue/creator.test.ts Outdated Show resolved Hide resolved
Copy link

codecov bot commented Feb 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 39.71%. Comparing base (8dca2ac) to head (607d7b3).
Report is 1 commits behind head on develop-postgres.

Additional details and impacted files
@@                Coverage Diff                @@
##           develop-postgres    #3151   +/-   ##
=================================================
  Coverage             39.71%   39.71%           
=================================================
  Files                   455      455           
  Lines                 33553    33553           
  Branches                407      407           
=================================================
  Hits                  13324    13324           
  Misses                20229    20229           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 6, 2025
Signed-off-by: NishantSinghhhhh <[email protected]>
Copy link

github-actions bot commented Feb 6, 2025

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

@NishantSinghhhhh
Copy link
Author

NishantSinghhhhh commented Feb 6, 2025

@palisadoes , I am done adding tests in this PR , so do tell me the changes that are required to make it merge in the branch

@palisadoes palisadoes merged commit 20d7f4b into PalisadoesFoundation:develop-postgres Feb 6, 2025
17 of 18 checks passed
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.

3 participants