Skip to content

Comments

test: add SENTRY_TEST_PATH_PREFIX to crash_marker test database path#1437

Merged
vaind merged 1 commit intomasterfrom
fix/test-basic-database-path-prefix
Nov 3, 2025
Merged

test: add SENTRY_TEST_PATH_PREFIX to crash_marker test database path#1437
vaind merged 1 commit intomasterfrom
fix/test-basic-database-path-prefix

Conversation

@vaind
Copy link
Contributor

@vaind vaind commented Nov 3, 2025

Summary

Fixes the crash_marker test to properly use SENTRY_TEST_PATH_PREFIX when creating the database directory, ensuring consistency with other tests in the suite. This PR fixes a regression introduced by #1404

Changes

  • Updated database path creation in crash_marker test to include SENTRY_TEST_PATH_PREFIX prefix in tests/unit/test_basic.c:158-159

Background

The crash_marker test was creating a database directory without using the test path prefix that other tests use. This could cause the test to write to an unexpected location on some platforms or testing environments.

🤖 Generated with Claude Code

… path

The crash_marker test creates a database directory but was not using
SENTRY_TEST_PATH_PREFIX like other tests. This could cause the test
to write to an unexpected location on some platforms.

This change ensures the database path is properly prefixed with the
test path prefix, making it consistent with other tests in the suite.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@vaind vaind changed the title fix(tests): add SENTRY_TEST_PATH_PREFIX to crash_marker test database path test: add SENTRY_TEST_PATH_PREFIX to crash_marker test database path Nov 3, 2025
@vaind vaind merged commit 7e96a5e into master Nov 3, 2025
41 of 42 checks passed
@vaind vaind deleted the fix/test-basic-database-path-prefix branch November 3, 2025 10:34
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.

2 participants