bevy-testing
/bevy-testing
Testuje Bevy 0.19 przez App::update, TimeUpdateStrategy, FixedUpdate, MessageCursor i On<E>: deterministyczne kroki, opróżnianie zadań async bez sleepów, światy headless i regresję wizualną z przechwytywaniem obrazu.
- Autor
- chrisgliddon ↗
- Repozytorium
- bevy-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.08.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 25.08.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Testuje Bevy 0.19 przez App::update, TimeUpdateStrategy, FixedUpdate, MessageCursor i On<E>: deterministyczne kroki, opróżnianie zadań async bez sleepów, światy headless i regresję wizualną z przechwytywaniem obrazu.
Oryginalny opis (EN)
Use when testing Bevy 0.19 with `App::update`, `TimeUpdateStrategy`, `FixedUpdate`, `MessageCursor`, or `On<E>`: deterministic stepping, async-task draining without sleeps, headless worlds, and capture-based visual regression.
Jak działa
- When to use this skill
- Canonical pattern
- Gotchas
- Test through observable contracts
- Async without sleeps
- Headless versus rendered tests
- Choose the relevant deep dive
- Review checklist
- See also
Podgląd SKILL.md
---
name: bevy-testing
description: "Use when testing Bevy 0.19 with `App::update`, `TimeUpdateStrategy`, `FixedUpdate`, `MessageCursor`, or `On<E>`: deterministic stepping, async-task draining without sleeps, headless worlds, and capture-based visual regression."
license: MIT
compatibility: opencode,claude-code,cursor
metadata:
tier: "2"
area: testing
bevy_version: "0.19"
---
# Bevy 0.19 — deterministic testing
## When to use this skill
- Systems/plugins need a minimal `App` harness and direct world assertions.
- Fixed schedules, timers, messages, or observers need deterministic stepping.
- Async work must complete in tests without arbitrary sleeps.
- Rendered output needs capture-based visual regression.
Build the smallest `App` that owns the behaviour under test, control its clock and
inputs, step it explicitly, then inspect world state or emitted output. Do not call
`App::run()` in an ordinary unit/integration test.
## Canonical pattern
```rust
use bevy::{prelude::*, time::{TimePlugin, TimeUpdateStrategy}};
#[derive(Resource, Default)]
struct TickCount(u32);
fn count_tick(mut count: ResMut<TickCount>) {
count.0 += 1;
}
#[test]
fn fixed_system_runs_exactly_three_times() {
let mut app = App::new();
app.add_plugins(TimePlugin)
.insert_resource(Time::<Fixed>::from_hz(60.0))
.insert_resource(TimeUpdateStrategy::FixedTimesteps(1))
.init_resource::<TickCount>()
.add_systems(FixedUpdate, count_tick);
// The first update initializes Bevy's real-time clock; it has zero delta.
app.update();
for _ in 0..3 {
app.update();
}
assert_eq!(app.world().resource::<TickCount>().0, 3);
}
```
After the first clock-initialising update, `FixedTimesteps(n)` makes each
`app.update()` advance by the fixed timestep times `n` and run exactly `n` fixed
loops. Use `ManualDuration` when the test must exercise zero-tick frames, accumulated
time, or catch-up. Use `ManualInstant` when exact absolute instants matter and advance
its resource before each update.
## Gotchas
- The first `app.update()` initialises real time with zero delta; warm it up before
counting `FixedTimesteps` ticks or assert that zero-step frame deliberately.
- Running `FixedUpdate` directly bypasses fixed-main clock/message semantics.
- Deferred `Commands` are invisible until a synchronization point.
- Async completion must use an injected fake or a bounded predicate loop, never sleep.
- `DefaultPlugins` adds platform/render/audio state most world tests do not need.
## Test through observable contracts
- Insert resources/components and call `app.update()` for scheduled behaviour.
- Invoke pure helper functions directly for algorithms and state machines.
- Read world state, messages with a test-owned `MessageCursor`, or observer effects.
- Keep deferred-command boundaries visible: a command is not applied until the
schedule reaches a synchronization point.
- Assert invariants and externally meaningful ordering, not arbitrary query/entity or
same-event observer order.
## Async without sleeps
Production systems should poll `Task<T>` with
`bevy::tasks::futures::check_ready`, or drain a result channel non-blockingly. Tests
should inject a deterministic inline/fake executor when possible. Otherwise step the
app until an observable completion predicate with a strict maximum step/deadline and
fail with queue/task state. Never use “sleep 100 ms and hope the task finished.”
Dropping a Bevy `Task` cancels it unless it was detached. Keep task ownership explicit
and ensure tests cover completion, cancellation, failure, and stale-result paths.
## Headless versus rendered tests
For ECS/gameplay logic, use `App::new()` plus only required plugins (`TimePlugin`,
`AssetPlugin`, etc.). Avoid `DefaultPlugins` when no window, renderer, audio device, or
filesystem is part of the contract. For render acceptance, launch a real render app,
capture a `Screenshot`, wait for `ScreenshotCaptured`, and compare a saved artifact
against a versioned baseline with documented tolerance.
## Choose the relevant deep dive
| Problem | Read |
|---|---|
| Minimal apps, manual time, fixed loops, schedule stepping | [App and time](references/app-and-time.md) |
| Messages, observers, deferred effects, tasks and no-sleep draining | [Messages, observers, and async](references/messages-observers-and-async.md) |
| Screenshot capture, deterministic scenes, diff thresholds and artifacts | [Visual regression](references/visual-regression.md) |
## Review checklist
- The test owns time; wall-clock speed cannot change its expected result.
- Each test installs only the plugins/resources the subject requires.
- Inputs and random seeds are explicit, and persistent/global state is isolated.
- Fixed input tests cover zero, one, and multiple fixed ticks per update.
- Message cursors are created before/after writes intentionally.
- Async tests have a deterministic fake or a bounded progress loop with useful failure.
- Visual failures retain actual, expected, and diff images plus run metadata.
- Baselines are updated only through an explicit reviewed operation.
## See also
- [`bevy-input-actions`](../bevy-input-actions/SKILL.md) — frame-to-fixed input invariants.
- [`bevy-physics`](../bevy-physics/SKILL.md) — Rapier headless and determinism boundaries.
- [`bevy-diagnostics-profiling`](../bevy-diagnostics-profiling/SKILL.md) — acceptance replays and performance evidence.
- [Bevy `TimeUpdateStrategy`](https://docs.rs/bevy/0.19.0/bevy/time/enum.TimeUpdateStrategy.html)
- [Bevy `Task`](https://docs.rs/bevy/0.19.0/bevy/tasks/struct.Task.html)
Pliki w paczce (4)
- SKILL.md 6 KB
- references/app-and-time.md 3 KB
- references/messages-observers-and-async.md 3 KB
- references/visual-regression.md 2 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · chrisgliddon/bevy-skills | 100 | MIT |
| ianpurton/disposable-heroes | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 531ffaa505f4 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100bevy
Kieruje zadania Bevy 0.20 do właściwego podskilla, pilnuje wyboru Update lub FixedUpdate i flag funkcji Cargo. - 100bevy
Kieruje do właściwej umiejętności Bevy 0.19 i przypina wersję silnika, przy wyborze między Update a FixedUpdate oraz flag Cargo, ECS, zasobów, renderowania lub migracji. - 100bevy-core-concepts
Składa aplikację Bevy 0.20: App, Plugin, harmonogram Update i FixedUpdate, kolejność systemów i wykrywanie niejednoznaczności. - 100bevy-game-loop-time-trial
Buduje w Bevy 0.20 wyścig na czas jako dane ECS: jeden zasób z zegarem, bramki międzyczasów i meta połączone przez chain, podczas gdy ruch idzie w FixedUpdate. - 100bevy-core-concepts
Wyjaśnia podstawy Bevy 0.19: składanie App i Plugin, wybór między Update a FixedUpdate, kolejność Startup, PreUpdate i PostUpdate, systemy wyłączne oraz graf harmonogramu. - 100bevy-combat-system
Buduje walkę w Bevy ECS: Health, Team i Invuln na aktorach, komunikaty Hit, zasięg broni wręcz i usuwanie po obrażeniach w FixedUpdate.