changed assert_run_pid and assert_not_run_pid and added a SLEEP! this will have significant impact on testing performance, BUT otherwise test will not work in case of misconfiguration of neo4j. the problem is, that neo4j will start, then the PID is checked and AFTER that neo4j might find out that the config is broken and terminates. Because of this timing problem, all tests will work even though the config is broken. Once neo4j has fixed this problem in bin/neo4j do_start(), the sleep should be removed again fixed tests for v3.0.x regarding server address
changed assert_run_pid and assert_not_run_pid and added a SLEEP! this will have significant impact on testing performance, BUT otherwise test will not work in case of misconfiguration of neo4j. the problem is, that neo4j will start, then the PID is checked and AFTER that neo4j might find out that the config is broken and terminates. Because of this timing problem, all tests will work even though the config is broken. Once neo4j has fixed this problem in bin/neo4j do_start(), the sleep should be removed again
fixed tests for v3.0.x regarding server address

cohesivestack/ineo