bevy/.github/example-run
François Mockers e57f73207e
Smarter testbeds (#17573)
# Objective

- Improve CI when testing rendering by having smarter testbeds

## Solution

- CI testing no longer need a config file and will run with a default
config if not found
- It is now possible to give a name to a screenshot instead of just a
frame number
- 2d and 3d testbeds are now driven from code
  - a new system in testbed will watch for state changed
- on state changed, trigger a screenshot 100 frames after (so that the
scene has time to render) with the name of the scene
- when the screenshot is taken (`Captured` component has been removed),
switch scene
- this means less setup to run a testbed (no need for a config file),
screenshots have better names, and it's faster as we don't wait 100
frames for the screenshot to be taken

## Testing

- `cargo run --example testbed_2d --features bevy_ci_testing`
2025-01-31 22:38:39 +00:00
..
ambiguity_detection.ron Test for ambiguous system ordering in CI (#13950) 2024-07-17 21:05:48 +00:00
no_renderer.ron new format for ci config file (#13154) 2024-05-02 22:51:47 +00:00
scene.ron new format for ci config file (#13154) 2024-05-02 22:51:47 +00:00
testbed_2d.ron Smarter testbeds (#17573) 2025-01-31 22:38:39 +00:00
testbed_3d.ron Smarter testbeds (#17573) 2025-01-31 22:38:39 +00:00
testbed_ui.ron Add screenshot check on UI (#16486) 2024-11-23 18:38:24 +00:00