chore: Fix test

[Dschoordsch]

The test would close the database connection which made later calls fail. Moved it to afterAll.

Description

Fixes/Partially Fixes #[issue number]
[Please include a summary of the changes and the related issue]

Demo

[If possible, please include a screenshot or gif/video, it'll make it easier for reviewers to understand the scope of the changes and how the change is supposed to work. If you're introducing something new or changing the existing patterns, please share a Loom and explain what decisions you've made and under what circumstances]

Testing scenarios

[Please list all the testing scenarios a reviewer has to check before approving the PR]

• Scenario A

  • Step 1
  • Step 2...

• Scenario B

  • Step 1
  • Step 2....

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label Skip Maintainer Review Indicating the PR only requires reviewer review and can be merged right after it's approved if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog

Summary by CodeRabbit

• Tests
  • Improved resource management in the test suite by centralising database connection cleanup after all tests, enhancing reliability and maintainability.

[coderabbitai]

Walkthrough

The recent changes improve resource management in the disableAnonymity.test.ts file by introducing an afterAll hook to ensure that the closePg() function is called once all tests have completed. This adjustment centralises the cleanup process, mitigating potential memory leaks or connection issues, and enhances the overall reliability of the test suite.

Changes

Files	Change Summary
packages/server/__tests__/disableAnonymity.test.ts	Added an afterAll hook to call closePg() after all tests for improved resource management. Removed individual calls to closePg() from specific test cases.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e6a3c7d and f46defa.

Files selected for processing (1)

• packages/server/tests/disableAnonymity.test.ts (2 hunks)

Additional comments not posted (1)

packages/server/__tests__/disableAnonymity.test.ts (1)

133-135: LGTM! Centralized cleanup process.

The afterAll hook ensures that the closePg() function is called after all tests have completed, preventing potential memory leaks or connection issues.

However, verify if there are any other instances of closePg() being called within individual test cases to ensure no redundant calls exist.

Verification successful

---

No redundant calls to closePg() within the test file.

The afterAll hook ensures that the closePg() function is called after all tests have completed, preventing potential memory leaks or connection issues. There are no redundant calls to closePg() within the test file.

• packages/server/__tests__/disableAnonymity.test.ts: The afterAll hook is appropriately used to centralize the cleanup process.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify if there are any other instances of `closePg()` being called within individual test cases.

# Test: Search for the function usage. Expect: No other instances of `closePg()` being called within individual test cases.
rg --type python -A 5 $'closePg'

Length of output: 62

---

Script:

#!/bin/bash
# Description: Verify if there are any other instances of `closePg()` being called within individual test cases.

# Test: Search for the function usage. Expect: No other instances of `closePg()` being called within individual test cases.
rg --type typescript -A 5 $'closePg'

Length of output: 70

---

Script:

#!/bin/bash
# Description: Verify if there are any other instances of `closePg()` being called within individual test cases.

# Test: Search for the function usage. Expect: No other instances of `closePg()` being called within individual test cases.
rg --type ts -A 5 $'closePg'

Length of output: 3797

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.