Skip to content

Conversation

@josvandervelde
Copy link
Member

Metadata

  • Reference Issue: -
  • New Tests Added: No
  • Documentation Updated: NA
  • Change Log Entry: Do not use test-apikey for unittests that talk with prod.

Details

  • In the unittests, when calling the Prod server APIs, do not add an API key.
  • Because, we should not assume the test api-key is valid in prod.

@codecov-commenter
Copy link

codecov-commenter commented Sep 20, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.72%. Comparing base (eed10f7) to head (69875d7).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1436      +/-   ##
===========================================
+ Coverage    52.69%   52.72%   +0.03%     
===========================================
  Files           36       36              
  Lines         4346     4349       +3     
===========================================
+ Hits          2290     2293       +3     
  Misses        2056     2056              

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@PGijsbers PGijsbers merged commit 4b1bdf4 into develop Sep 22, 2025
13 checks passed
@PGijsbers PGijsbers deleted the feature/do_not_use_test_apikey_for_prod branch September 22, 2025 08:46
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.

4 participants