From 93bc32dbd055813c6d02f1f077277e02a5eb4669 Mon Sep 17 00:00:00 2001 From: Bamidev Date: Sat, 2 Mar 2024 16:06:45 +0100 Subject: [PATCH] Fix tests. --- docs/GETTING-STARTED.md | 1 - src/tests.rs | 3 ++- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/GETTING-STARTED.md b/docs/GETTING-STARTED.md index 0351e99..b51f2b1 100644 --- a/docs/GETTING-STARTED.md +++ b/docs/GETTING-STARTED.md @@ -19,7 +19,6 @@ Here are the pros and cons of each browser framework. Choose wisely: * Is available on all major platforms: Windows, MacOS, Linux (although MacOS support in _BrowserWindow_ needs some work). If you want the exact same behavior of your app on all platforms, CEF is recommended. * The cookie API of _BrowserWindow_ is supported. -* Is the only framework option which can be decently cross-compiled to Windows. *Cons:* * Can be a pain to set up correctly; requires a lot of files to be present for the executable, and needs the sandbox to have specific permissions. diff --git a/src/tests.rs b/src/tests.rs index 473d425..1b47f42 100644 --- a/src/tests.rs +++ b/src/tests.rs @@ -17,6 +17,7 @@ fn tests() { let settings = ApplicationSettings { engine_seperate_executable_path: Some(exec_path), resource_dir: None, + remote_debugging_port: None, }; let app = Application::initialize(&settings).expect("unable to initialize application"); @@ -56,7 +57,7 @@ fn async_tests(application: &Application) { let exit_code = runtime.run_async(|app| async move { let _bw = async_basic(app.clone()).await; #[cfg(not(feature = "webkitgtk"))] - async_cookies(app).await; + async_cookies(app.clone()).await; //async_correct_parent_cleanup(app).await; app.exit(0); });