test: save fixtures

[chemelli74]

Summary by CodeRabbit

• Chores
  • Expanded test fixture data for multiple system modules to enhance validation coverage.
  • Refined development tooling configuration to properly manage test fixture files during code quality reviews.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds configuration updates and new test fixture data files. A pre-commit configuration entry is modified to exclude JSON fixture files from spell checking, while 11 new JSON fixture files are introduced across bridge and vedo domains containing structured test data for room configurations, lighting, irrigation, scenarios, shutters, and security zones.

Changes

Cohort / File(s)	Summary
Pre-commit Configuration .pre-commit-config.yaml	Added args: ["--skip=src/fixtures/*.json"] to codespell hook to exclude JSON fixture files from spell checking
Bridge Fixture Data src/fixtures/bridge/clima.json, src/fixtures/bridge/counter.json, src/fixtures/bridge/irrigation.json, src/fixtures/bridge/light.json, src/fixtures/bridge/other.json, src/fixtures/bridge/scenario.json, src/fixtures/bridge/shutter.json	Seven new JSON fixture files added containing room/zone metadata, environmental descriptors, status indicators, and numeric values for climate control, counters, irrigation zones, lighting configurations, miscellaneous devices, scenarios, and shutter controls
Vedo Fixture Data src/fixtures/vedo/vedo_area_desc.json, src/fixtures/vedo/vedo_area_stat.json, src/fixtures/vedo/vedo_zone_desc.json, src/fixtures/vedo/vedo_zone_stat.json	Four new JSON fixture files added containing security/alarm system metadata including area descriptions, area statistics, zone descriptions, and zone status arrays

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

Poem

🐰 With whiskers twitching, I hop with glee,
New fixtures bloom like clover in a spree!
Bridge and vedo data, organized with care,
Pre-commit skips the JSON over there—
Testing grounds now flourish, bright and fair! ✨

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'test: save fixtures' directly reflects the main change—adding multiple JSON fixture files for testing purposes. It is concise, clear, and accurately summarizes the primary intent of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (24dd490) to head (fa84783).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #363   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           50        50           
=========================================
  Hits            50        50           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR adds test fixture files containing JSON data for a home automation system, including alarm/security (vedo) and bridge controller configurations. The fixtures appear to represent a real home setup with Italian room and device names.

• Adds vedo alarm system fixtures for zones and areas (statistics and descriptions)
• Adds bridge controller fixtures for various device types (lights, shutters, climate, irrigation, scenarios, counters, other devices)
• Updates pre-commit configuration to skip codespell checks on fixture JSON files

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/fixtures/vedo/vedo_zone_stat.json	Zone statistics including status codes, authentication, and operational flags
src/fixtures/vedo/vedo_zone_desc.json	Zone descriptions with presence indicators and Italian room names (doors, windows, sensors)
src/fixtures/vedo/vedo_area_stat.json	Area statistics for alarm states (ready, armed, alarm, sabotage, etc.)
src/fixtures/vedo/vedo_area_desc.json	Area descriptions defining security zones (perimeter, volumetric, garage)
src/fixtures/bridge/shutter.json	Shutter/blind configuration for external awning and velux window
src/fixtures/bridge/scenario.json	Scenario definitions for exit automations (total, partial, robot)
src/fixtures/bridge/other.json	Other device configuration for a bedside outlet
src/fixtures/bridge/light.json	Light configuration for 32 lights across various rooms
src/fixtures/bridge/irrigation.json	Irrigation zone configuration for 4 garden zones
src/fixtures/bridge/counter.json	Counter/meter data with timestamp and instant readings
src/fixtures/bridge/clima.json	Climate control configuration for 4 zones with temperature and mode settings
.pre-commit-config.yaml	Adds codespell skip pattern for fixture JSON files to avoid false positives on Italian text

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 24dd490 and fa84783.

📒 Files selected for processing (12)

• .pre-commit-config.yaml
• src/fixtures/bridge/clima.json
• src/fixtures/bridge/counter.json
• src/fixtures/bridge/irrigation.json
• src/fixtures/bridge/light.json
• src/fixtures/bridge/other.json
• src/fixtures/bridge/scenario.json
• src/fixtures/bridge/shutter.json
• src/fixtures/vedo/vedo_area_desc.json
• src/fixtures/vedo/vedo_area_stat.json
• src/fixtures/vedo/vedo_zone_desc.json
• src/fixtures/vedo/vedo_zone_stat.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: release

🔇 Additional comments (11)

src/fixtures/vedo/vedo_zone_stat.json (1)

1-7: LGTM! Valid test fixture structure.

The JSON structure is valid and appropriate for test fixture data. The long comma-separated status codes in the status field are typical for zone status test data.

src/fixtures/bridge/other.json (1)

1-24: LGTM! Consistent fixture structure.

The JSON structure is valid with proper parallel array alignment. The num field (1) matches the array lengths, and the env index correctly references the env_desc mapping.

src/fixtures/bridge/counter.json (1)

1-40: LGTM! Valid counter fixture data.

The JSON structure is valid and appropriate for counter/meter test fixture data. The instant array with 31 elements and the timestamp in dataora follow a typical pattern for this type of fixture.

src/fixtures/bridge/shutter.json (1)

1-24: LGTM! Consistent shutter fixture structure.

The JSON structure is valid with proper parallel array alignment. The num field (2) matches the array lengths, and both env indices correctly reference the env_desc mapping.

src/fixtures/vedo/vedo_area_desc.json (1)

1-19: Fixture data looks good.

The JSON structure is valid and well-formed with consistent array dimensions (8 elements). Presence and descriptor data appear reasonable for a test fixture.

src/fixtures/bridge/irrigation.json (1)

1-29: Fixture data is well-structured and consistent.

Array dimensions are properly aligned (num: 4 with four 4-element arrays for zones). The env_desc mapping of 13 location descriptors is a reasonable set of environment options, and zero-valued status arrays are appropriate for an initial test state.

src/fixtures/vedo/vedo_zone_desc.json (1)

1-409: The arrays in vedo_zone_desc.json are properly aligned—description, in_area, and present all contain 382 elements, not the dimensions claimed in the original review. The sparse description array (with only 13 non-empty labels among 382 elements) reflects the intentional design for zone labeling in the VEDO fixture schema.

src/fixtures/bridge/clima.json (1)

1-45: LGTM!

Valid JSON fixture with consistent parallel arrays (all match num: 4). The env_desc array correctly serves as a separate lookup table for environment descriptions.

src/fixtures/vedo/vedo_area_stat.json (1)

1-15: LGTM!

Valid JSON fixture with consistent zone arrays (all 8 elements). The structure correctly represents area statistics for a Vedo security system.

src/fixtures/bridge/scenario.json (1)

1-55: LGTM!

Valid JSON fixture with correct array lengths matching num: 32. The empty type and env_desc arrays appear intentional for scenario fixtures.

src/fixtures/bridge/light.json (1)

1-72: LGTM!

Valid JSON fixture with consistent parallel arrays matching num: 32. The env_desc lookup table aligns with the environment IDs used in the env array.