What problem does it solve? It gives contributors a single reference for how to test the GRID Craft Launcher codebase correctly, covering unit tests, HTTP mocking, snapshot review, CLI tests, GUI flow tests, and end-to-end recipes, so tests stay hermetic and CI-safe. ## Core Features & Use Cases - Test commands and workflow: Run just check for fmt, clippy, and all tests, filter with nextest syntax, and review insta snapshots before CI fails. - HTTP mocking patterns: Point Mojang, Modrinth, CurseForge, loader, and Microsoft auth endpoints at wiremock servers using debug-only GCL_*_BASE_URL overrides or Launcher::open_with_endpoints. - Test doubles and fixtures: Use FakeSource, FakeRunner, MemoryStore, recorded JSON fixtures with host rewriting, and shared helpers in tests/common/mod.rs. - GUI and e2e testing: Drive the Slint UI through the testing backend with flow tests, run just e2e / just e2e-modpack for real-network checks, and use just ui-xtest for real X input. - Use Case: When adding a new content-source feature, read this Skill to build a wiremock-backed test with a trimmed fixture and an insta snapshot instead of hitting the real network. ## Quick Start Ask the assistant to read the testing skill and then write a wiremock-based unit test for a new Modrinth source function following the project's fixture and snapshot conventions.