Access Sqlx Database within Test

[adamsdally]

I'm attempting to write some integration tests where I would like to access the sqlite database after visiting a route.
Below is the basics of my test setup.

Some things I have tried are accessing the database with sqlx directly, but the file is still locked. I would rather not have to switched databases to solve this. I also couldn't figure out a practical way of pulling it out of client, but hopefully I'm just overlooking something.

#[cfg(test)]
  mod test {

    use super::rocket;
    use rocket::figment::util::map;
    use rocket::figment::value::{Map, Value};
    use rocket::http::Status;
    use sqlx::sqlite::{SqliteConnectOptions, SqlitePoolOptions};
    use crate::{rocket_build, Task};
    use crate::rocket::futures::TryStreamExt;

    async fn async_client_from_sqlite_connect_options(
        sqlite_connect_options: SqliteConnectOptions,
    ) -> rocket::local::asynchronous::Client {
        use rocket::local::asynchronous::Client;
        let db_url = format!(
           "./db/{:?}",
           sqlite_connect_options.get_filename()
        );

        let db_config: Map<_, Value> = map! {
          "url" => db_url.clone().into(),
        };
      
         let figment = rocket::Config::figment()
            .merge(("databases", map!["mydb" => db_config]));
      
        let client = Client::tracked(rocket_build(figment)).await
          .expect("valid rocket instance");
      
        return client;
    }

    #[sqlx::test]
      async fn index(_sqlite_pool_options: SqlitePoolOptions, sqlite_connect_options: SqliteConnectOptions) -> sqlx::Result<()> {
       let client = async_client_from_sqlite_connect_options(sqlite_connect_options).await;
       let response = client.get(uri!(super::index)).dispatch().await;
       assert_eq!(response.status(), Status::Ok);

      //
      //access the database here
      //

       Ok(())
    }
}

[the10thWiz]

Depending on your needs, you may be better off creating an in-memory database for your test code. It uses the same sqlx client, so your code under test will work just fine. Since it's an in-memory database, it doesn't persist, which means you can modify it in any way you want while the test is running, and don't have to worry about rebuilding the database between tests.