fai/chain-studio
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
chain-studio/test/integration
History
flemming-it a5bcde6446 feat(studio): HubService.invokePluginTheme + integration test 
Wraps the new InvokePluginTheme RPC and ships an end-to-end
test that loads studio-theme-solarized into a fresh
HubFixture and asserts the light/dark schemes round-trip.

Signed-off-by: flemming-it <sf@flemming.it>
Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>
2026-05-25 21:49:40 +02:00
..
capabilities_test.dart chore(studio): flutter_markdown_plus migration + integration-test scaffold 2026-05-25 13:22:04 +02:00
hub_fixture.dart chore(studio): flutter_markdown_plus migration + integration-test scaffold 2026-05-25 13:22:04 +02:00
install_install_planned_test.dart chore(studio): RadioGroup migration + second integration test 2026-05-25 14:05:43 +02:00
plugin_theme_test.dart feat(studio): HubService.invokePluginTheme + integration test 2026-05-25 21:49:40 +02:00
README.md chore(studio): flutter_markdown_plus migration + integration-test scaffold 2026-05-25 13:22:04 +02:00

README.md

Integration tests

These tests spin up a real fai serve subprocess against a fresh temp dir and exercise Studio's Hub-facing data layer against it. They cover the "kind of regression that survives unit tests because the system-shape only manifests across the gRPC boundary".

Status

Scaffold. One canonical test (capabilities). The harness is production-quality (proper teardown, idempotent, port-clean) so new tests slot in by importing hub_fixture.dart and calling HubFixture.start() / dispose() in setUp / tearDown.

What's NOT here yet:

  • A full "install dep → run echo → assert title" scenario. The harness can do it (install_module is a real RPC), but building the fixture for module-bundle downloads against a hermetic local registry is its own scaffold. Tracked as follow-up to S-21.
  • Studio-side widget testing against the live hub. The flutter integration_test package supports it (testWidgets + IntegrationTestWidgetsFlutterBinding), but pumping a full StudioApp against a real gRPC channel needs binding.enableSurfaceBindingHack() ceremony we haven't designed yet.

Running

cd fai_studio
flutter test test/integration/

Prereq: a fai binary on PATH or at ../fai_platform/target/release/fai. The harness skips with a clear message when neither exists, so this command does not fail on a fresh checkout — it just reports skipped tests.

To get the binary:

cd ../fai_platform
cargo build --release --bin fai

First-time-start gotcha

A cold fai serve spends its first ~30s building the curated-model database and initialising SQLite migrations. HubFixture.start() waits up to 60s by default; if your local hub takes longer the first time, run fai serve once by hand against any temp FAI_DATA_DIR to warm the per-user cargo / SBOM caches:

FAI_DATA_DIR=/tmp/fai_warmup fai serve --bind 127.0.0.1:0
# wait for "hub started", Ctrl-C

Subsequent integration-test runs are quick.

Not yet wired into CI

.forgejo/workflows/ci.yml doesn't run these yet. Adding them needs an artifact-passing pattern: the platform build job publishes target/release/fai as a CI artifact; the studio test job consumes it. Pattern is straightforward once we want it; it's deferred because we don't yet have enough integration tests to justify the CI runtime.