Load Asset with AsserServer in Test

[thmsgntz]

Hello!

I am trying to test systems with assets loading from filesystem.
After several tries, I can not manage to load an image from the AssetServer in a test configuration.

Sorry if this is trivial, I could not find the proper documentation or example.

I do not understand if this is a pathing problem or something else, I tried:

• to move the assets directory into the test environement
• to change the asset_folder parameter of the AssetPlugin

Neither do work.
Note : I can load the asset outside the test. In my original code, the AssetServer can load the file.

Code :

#[test]
fn test_load_asset_from_filesystem() {
    // Given
    let mut app = App::new();

    app.add_plugin(TaskPoolPlugin::default());
    app.add_plugin(AssetPlugin { 
        asset_folder: String::from("assets"),
        ..Default::default()
    });
    app.add_plugin(ImagePlugin::default());

    let handler: Handle<Image> = app
        .world
        .get_resource::<AssetServer>()
        .unwrap()
        .load(Path::new("image_test.jpeg"));

    // With
    app.update();
    
    // Then
    assert_eq!(
        app.world
            .get_resource::<AssetServer>()
            .unwrap()
            .get_load_state(handler),
        LoadState::Loaded
    );
}

Error+backtrace :

---- test_load_asset_from_filesystem stdout ----
thread 'test_load_asset_from_filesystem' panicked at 'assertion failed: `(left == right)`
  left: `Failed`,
 right: `Loaded`', src/main.rs:33:5
stack backtrace:
   0:        0x10487bc66 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hae51cb91d407e2ef
   1:        0x1048db18b - core::fmt::write::h746bc0969202388b
   2:        0x10487081c - std::io::Write::write_fmt::haf5bf6c31546d75e
   3:        0x10487ba3a - std::sys_common::backtrace::print::h8360bf0158e89b36
   4:        0x10487ec20 - std::panicking::default_hook::{{closure}}::hedf04c568eb6e0bc
   5:        0x10487e969 - std::panicking::default_hook::h62889b2c29e2347d
   6:        0x1041376f6 - test::test_main::{{closure}}::h421153d21ccc3479
   7:        0x10487f38a - std::panicking::rust_panic_with_hook::h22edd02828aff274
   8:        0x10487f124 - std::panicking::begin_panic_handler::{{closure}}::h6895f44a9b7e2caa
   9:        0x10487c0a9 - std::sys_common::backtrace::__rust_end_short_backtrace::h013519e9b77978c5
  10:        0x10487ee6d - _rust_begin_unwind
  11:        0x1049070d3 - core::panicking::panic_fmt::h2a51b60c12d11322
  12:        0x1049074db - core::panicking::assert_failed_inner::hb78e88c3e26c29e0
  13:        0x103ea5a8e - core::panicking::assert_failed::h263067ddd386cdb1
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/panicking.rs:228:5
  14:        0x103ea1feb - bevy_test::test_load_asset_from_filesystem::h084efdc20ef5c741
                               at /Users/guntho/Documents/Programmation_slash_dev/rust/bevy_test/src/main.rs:33:5
  15:        0x103ea1feb - bevy_test::test_load_asset_from_filesystem::{{closure}}::h019ec27d4067b46d
                               at /Users/guntho/Documents/Programmation_slash_dev/rust/bevy_test/src/main.rs:11:38
  16:        0x103ea1feb - core::ops::function::FnOnce::call_once::h7b84ef30607b4d60
                               at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/ops/function.rs:250:5
  17:        0x10413c962 - test::__rust_begin_short_backtrace::h460edc73ee3d7292
  18:        0x104107181 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hdfe6b8e984779cce
  19:        0x10413b761 - test::run_test::run_test_inner::{{closure}}::h6df30ee50946e418
  20:        0x1041010b7 - std::sys_common::backtrace::__rust_begin_short_backtrace::he77a8a07f5d086a1
  21:        0x104107031 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hc09679af1629946e
  22:        0x104888ad9 - std::sys::unix::thread::Thread::new::thread_start::ha9b8d2206382b425
  23:     0x7ff80b2a74e1 - __pthread_start

Dependences and systems:
bevy = "0.10"
MacOS Monterey 12.6.6
cargo = 1.70.0

[NiklasEi]

Any other logs before the stack trace? For example something about a missing asset loader?

[thmsgntz]

This is the full backtrace logged with RUST_BACKTRACE=full

[NiklasEi]

Works fine for me once I remove the Path::new in the load call.

[thmsgntz]

Well I do not know what to say.. I try both, Path::newor &str.

[oliver-dew]

This passes for me:

    #[test]
    fn test_image() {
        let mut app = App::new();
        app.add_plugins((MinimalPlugins, AssetPlugin::default(), ImagePlugin::default()));
        let assets = app.world.resource::<AssetServer>();
        let handle: Handle<Image> = assets.load("studyMV.jpg");
        app.update();
        assert_eq!(app.world.resource::<AssetServer>().get_load_state(handle), Some(LoadState::Loading));
    }