1. Unskip the test: remove Vitess from the exclude list.

Use this commands to see occurrences of the exclusion.

cd prisma-engines/query-engine/connector-test-kit-rs
grep -R exclude |grep -i Planetscale

Run the test and see it fail

Use the script below to test each individual test (eg. new::interactive_tx::interactive_tx::batch_queries_failure):

make dev-planetscale && RUST_BACKTRACE=1 cargo test -p query-engine-tests new::interactive_tx::interactive_tx::batch_queries_failure -- --test-threads=1 --nocapture

Determine the outcome

• Fixing it with the same test path

• Won't fix:

  The test won't be fixed, This failure is accepted under the perspective of planetscale. Add exclude(Vitess("planetscale.js")) to the test.

• Fixing it with an alternate test path:

  This might be the case in small variations of error messages for instance.

  1. Create a variation of the test, and add the only(Vitess("planetscale.js")) attribute to the test
  2. Bring back the exclude(Vitess("planetscale.js"))

Assurance

• The issue can be closed when for each test, an outcome has been determined
• None of the tests above fail anymore