Skip to content

[TEST] Hardware Tests Not Automated - Manual Execution Required #52

@DonHugo

Description

@DonHugo

Test Issue

Hardware tests require manual execution on Raspberry Pi, slowing development.

Current State:

  • Hardware tests must be run manually
  • No automated test runs
  • Easy to skip testing
  • Inconsistent test coverage
  • No regression detection

Desired State:

  • Automated test execution on Pi
  • Scheduled test runs (nightly)
  • Automatic test reporting
  • CI/CD integration where possible
  • Test results tracked in GitHub

Benefits:

  • Catch regressions faster
  • Consistent test execution
  • Less manual work
  • Better quality assurance
  • Confidence in deployments

Implementation Plan:

  • Create SSH-based test runner script
  • Schedule automated test runs (cron)
  • Set up test result reporting
  • Create test failure notifications
  • Document test infrastructure
  • Integrate with GitHub Actions (if possible)

Test Categories to Automate:

  • Sensor reading tests
  • Relay control tests
  • MQTT integration tests
  • State persistence tests
  • Complete workflow tests

Acceptance Criteria:

  • Tests run automatically daily
  • Results reported clearly (pass/fail counts)
  • Failed tests trigger alerts
  • Test logs archived
  • Documentation complete
  • Coverage > 80%

Infrastructure Needs:

  • SSH access to Raspberry Pi
  • Cron job for scheduling
  • Test result storage
  • Notification system (MQTT/Email)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions