What problem does it solve?
Writing and debugging tests for Feast components (online stores, registries, feature views) requires knowing where tests live, which patterns to follow, and how to diagnose runtime failures like stale registries or empty online lookups. This Skill provides the test organization map, reusable test patterns, and debugging workflows for the Feast codebase.
Core Features & Use Cases
- Targeted Test Execution: Run single test files, single test names, or subsystem suites with pytest, plus Makefile targets for unit and local integration tests.
- Unit Test Patterns: Ready-to-adapt templates for testing online stores (with mocked clients), registry operations, SQL registry dialect DDL compilation, and end-to-end FeatureStore behavior with SQLite.
- Debugging Playbooks: Diagnose stale registries, all-None online feature lookups, mypy type errors, protobuf deserialization failures, and feature server 500 errors using CLI commands like
feast registry-dump and feast plan.
- Use Case: You added a new online store implementation and need to write unit tests. Follow the online store test pattern with mocked clients, run the targeted pytest command, then verify end-to-end with a local SQLite-backed FeatureStore test.
Quick Start
Ask the assistant to write a unit test for a new Feast online store and run it with pytest against the unit test directory.