The JS-over-Rust driver can take advantage of existing tests.
However, some tests (especially unit tests) make assumptions about driver's inner working that is not true for the Rust driver, so they should be deleted.
OTOH, integration tests that are valid for the new driver, too, should be used to track progress clearly.
Let's have a (grouped) list of tests that we want to pass, together with priorities. We will be able to mark tests that already pass.
The JS-over-Rust driver can take advantage of existing tests.
However, some tests (especially unit tests) make assumptions about driver's inner working that is not true for the Rust driver, so they should be deleted.
OTOH, integration tests that are valid for the new driver, too, should be used to track progress clearly.
Let's have a (grouped) list of tests that we want to pass, together with priorities. We will be able to mark tests that already pass.