How to run the tests of the sdk?

[szabgab]

After cloning https://github.com/surrealdb/surrealdb I can run the tests in the root of the repo as described in https://github.com/surrealdb/surrealdb/blob/main/CONTRIBUTING.md but that does not seem to test the examples in the sdk folder.

If I cd into the sdk folder I can run the tests using cargo test (actually I use cargo test -j 5 -- --test-threads 5 because a plain cargo test crashed my computer) but then I get the following errors:

running 9 tests
test access_bearer_revoke_db ... FAILED
test access_bearer_namespace ... FAILED
test access_bearer_revoke_root ... FAILED
test access_bearer_revoke_ns ... FAILED
test access_bearer_database ... FAILED
test access_bearer_root ... FAILED
test permissions_access_grant_root ... FAILED
test permissions_access_grant_db ... FAILED
test permissions_access_grant_ns ... FAILED

failures:

---- access_bearer_revoke_db stdout ----
thread 'access_bearer_revoke_db' panicked at sdk/tests/access.rs:334:30:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")

---- access_bearer_namespace stdout ----
thread 'access_bearer_namespace' panicked at sdk/tests/access.rs:143:30:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")

---- access_bearer_revoke_root stdout ----
thread 'access_bearer_revoke_root' panicked at sdk/tests/access.rs:402:30:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")

---- access_bearer_revoke_ns stdout ----
thread 'access_bearer_revoke_ns' panicked at sdk/tests/access.rs:368:30:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- access_bearer_database stdout ----
thread 'access_bearer_database' panicked at sdk/tests/access.rs:35:30:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")

---- access_bearer_root stdout ----
thread 'access_bearer_root' panicked at sdk/tests/access.rs:251:30:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")

---- permissions_access_grant_root stdout ----
thread 'permissions_access_grant_root' panicked at sdk/tests/access.rs:604:37:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")

---- permissions_access_grant_db stdout ----
thread 'permissions_access_grant_db' panicked at sdk/tests/access.rs:470:37:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")

---- permissions_access_grant_ns stdout ----
thread 'permissions_access_grant_ns' panicked at sdk/tests/access.rs:537:37:
called `Result::unwrap()` on an `Err` value: Ds("Cannot connect to the `memory` storage engine as it is not enabled in this build of SurrealDB")


failures:
    access_bearer_database
    access_bearer_namespace
    access_bearer_revoke_db
    access_bearer_revoke_ns
    access_bearer_revoke_root
    access_bearer_root
    permissions_access_grant_db
    permissions_access_grant_ns
    permissions_access_grant_root

test result: FAILED. 0 passed; 9 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

I could not find any information about this in the CONTRIBUTING.md file.