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

Revisit how tests are setup #496

Open
tjmadonna opened this issue Oct 9, 2024 · 1 comment
Open

Revisit how tests are setup #496

tjmadonna opened this issue Oct 9, 2024 · 1 comment
Assignees

Comments

@tjmadonna
Copy link
Contributor

tjmadonna commented Oct 9, 2024

This would apply to ingest-api as well. The json files with the test configurations have become cumbersome to update when new features are added.

@tjmadonna tjmadonna added this to CODCC Oct 9, 2024
@tjmadonna tjmadonna converted this from a draft issue Oct 9, 2024
@tjmadonna
Copy link
Contributor Author

One possible solution is to use docker-compose to create a temporary neo4j database inside docker. This way we wouldn't have to mock all the database calls. We would still need to mock UBKG and calls to other microservices, but it would cut down on the number of mocks.

@tjmadonna tjmadonna moved this from Backlog to Ready in CODCC Dec 10, 2024
@tjmadonna tjmadonna moved this from Ready to In Progress in CODCC Dec 10, 2024
@tjmadonna tjmadonna self-assigned this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant