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

Skip C++ neo4j tests if C++ frontend is not enabled #1918

Closed
wants to merge 2 commits into from

Conversation

oxisto
Copy link
Member

@oxisto oxisto commented Jan 4, 2025

This PR skips the C++-based neo4j tests, if the C++ frontend is not enabled. We should also add more language-neutral tests to neo4j in the future.

This PR skips the C++-based neo4j tests, if the C++ frontend is not enabled. We should also add more language-neutral tests to neo4j in the future.
@oxisto oxisto requested a review from peckto as a code owner January 4, 2025 17:07
Copy link

codecov bot commented Jan 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.06%. Comparing base (d2e1343) to head (470c7be).
Report is 1 commits behind head on main.

Additional details and impacted files

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

@oxisto oxisto requested a review from konradweiss January 8, 2025 12:38
Copy link
Collaborator

@konradweiss konradweiss left a comment

Choose a reason for hiding this comment

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

LGTM

@oxisto
Copy link
Member Author

oxisto commented Jan 8, 2025

Thanks. I will keep it un-merged until we discuss it tomorrow.

@oxisto
Copy link
Member Author

oxisto commented Jan 9, 2025

We will move the C++ tests in neo4j to integration tests instead and exclude integration and performance test from build.

@oxisto oxisto closed this Jan 9, 2025
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