neo4j-ruby-driver
neo4j-ruby-driver copied to clipboard
neo4jrb
Upgrade async gem fix specs 5.0
Hi @klobuczek
As you mentioned in https://github.com/neo4jrb/neo4j-ruby-driver/pull/235
Here you have code changes against the 5.0 branch.
About cluster tests and Testkit.
If I understand correctly, the ultimate goal is to eliminate cluster integration tests, that are setup with neoctrl-*.
What about other Ruby specs in the main project? Do you want to keep them? Is Testkit gonna be the only source of truth?
I haven't run Testkit yet in the docker container. I am not sure what is your point of view of having dockerized version.
Waiting for your comments :)
@petergebala sorry for the delayed response.
Hi @klobuczek
As you mentioned in #235 Here you have code changes against the
5.0branch.About cluster tests and Testkit. If I understand correctly, the ultimate goal is to eliminate cluster integration tests, that are setup with
neoctrl-*.
It is not so much a goal to eliminate the cluster tests as it is a pain to maintain them. They are quite brittle and do not work on driver 5.0 at all.
What about other Ruby specs in the main project? Do you want to keep them?
Yes, keep all tests that run against a single neo4j instance or no instance at all.
Is Testkit gonna be the only source of truth?
Not the only source but having them all pass would be fantastic.
I haven't run Testkit yet in the docker container. I am not sure what is your point of view of having dockerized version.
testkit on github actions runs in docker container. Some of the testkit tests run against a stubbed server, which can easily simulate different scenarios that would be hard to do on a real server. On local I run neo4j in docker, but then for debugging purposes, I run the testkit-backend and the python script directly in shell. I haven't gotten yet to a point where everything passes, so there is always debugging involved.
Waiting for your comments :)
I pushed changes. I was also able to run testkit locally and replicate failing tests. I will work on them in free time.
@petergebala could you refresh your branch with the current 5.0. We will try to merge your PR as the failing testkit is not related.