Skip to content

[Backend] backend/.env.test is committed with real looking secrets format #1512

Description

@grantfox-oss

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Why this matters
backend/.env.test is checked into the repo to configure the Jest test environment. Even if the values are dummy test only values, committing an env file sets a bad precedent and risks a future edit accidentally introducing a real credential.

Acceptance criteria

  • Audit backend/.env.test values to confirm none are real secrets
  • Rename to backend/.env.test.example and load it explicitly from jest.config.ts, or clearly comment every value as a placeholder
  • Document the test env setup in backend/README.md

Files to touch

  • backend/.env.test
  • backend/jest.config.ts
  • backend/README.md

Out of scope
Rotating any credentials, none should exist here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendIssues related to backend developmentgood first issueGood for newcomerssecuritySecurity related issues

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions