bevy/crates/bevy_ecs_compile_fail_tests/tests/ui.rs

fn main() -> bevy_compile_test_utils::ui_test::Result<()> {
    bevy_compile_test_utils::test("tests/ui")
}
Switch to ui_test in compile fail tests. (#12810) # Objective Make compile fail tests less likely to break with new Rust versions. Closes #12627 ## Solution Switch from [`trybuild`](https://github.com/dtolnay/trybuild) to [`ui_test`](https://github.com/oli-obk/ui_test). ## TODO - [x] Update `bevy_ecs_compile_fail_tests` - [x] Update `bevy_macros_compile_fail_tests` - [x] Update `bevy_reflect_compile_fail_tests` --------- Co-authored-by: Oli Scherer <github35764891676564198441@oli-obk.de> Co-authored-by: BD103 <59022059+BD103@users.noreply.github.com> 2024-04-27 00:00:57 +00:00			`fn main() -> bevy_compile_test_utils::ui_test::Result<()> {`
			`bevy_compile_test_utils::test("tests/ui")`
Assert compiler errors for compile_fail tests (#3067) # Objective bevy_ecs has several compile_fail tests that assert lifetime safety. In the past, these tests have been green for the wrong reasons (see e.g. #2984). This PR makes sure, that they will fail if the compiler error changes. ## Solution Use [trybuild](https://crates.io/crates/trybuild) to assert the compiler errors. The UI tests are in a separate crate that is not part of the Bevy workspace. This is to ensure that they do not break Bevy's crater builds. The tests get executed by the CI workflow on the stable toolchain. 2021-11-13 22:43:19 +00:00			`}`