hass.tibber_prices/docs/developer/docs/testing.md
Julian Pawlowski d73eda4b2f git commit -m "feat(docs): add dual Docusaurus sites with custom branding and Giscus integration
- Split documentation into separate User and Developer sites
- Migrated existing docs to proper Docusaurus structure
- Added custom Tibber-themed header logos (light + dark mode variants)
- Implemented custom color scheme matching integration branding
  - Hero gradient: Cyan → Dark Cyan → Gold
  - Removed standard Docusaurus purple/green theme
- Integrated Giscus comments system for community collaboration
  - User docs: Comments enabled on guides, examples, FAQ
  - User docs: Comments disabled on reference pages (glossary, sensors, troubleshooting)
  - Developer docs: No comments (GitHub Issues/PRs preferred)
- Added categorized sidebars with emoji navigation
- Created 8 new placeholder documentation pages
- Fixed image paths for baseUrl compatibility (local + GitHub Pages)
- Escaped MDX special characters in performance metrics
- Added GitHub Actions workflow for automated deployment
- Created helper scripts: dev-user, dev-developer, build-all

Breaking changes:
- Moved /docs/user/*.md to /docs/user/docs/*.md
- Moved /docs/development/*.md to /docs/developer/docs/*.md
2025-12-06 01:37:06 +00:00

1,008 B

Testing

Note: This guide is under construction.

Integration Validation

Before running tests or committing changes, validate the integration structure:

# Run local validation (JSON syntax, Python syntax, required files)
./scripts/release/hassfest

This lightweight script checks:

  • config_flow.py exists
  • manifest.json is valid JSON with required fields
  • ✓ Translation files have valid JSON syntax
  • ✓ All Python files compile without syntax errors

Note: Full hassfest validation runs in GitHub Actions on push.

Running Tests

# Run all tests
pytest tests/

# Run specific test file
pytest tests/test_coordinator.py

# Run with coverage
pytest --cov=custom_components.tibber_prices tests/

Manual Testing

# Start development environment
./scripts/develop

Then test in Home Assistant UI:

  • Configuration flow
  • Sensor states and attributes
  • Services
  • Translation strings

Test Guidelines

Coming soon...