hubble-ready-test

# Hubble Ready Testing Framework

## Overview

This testing framework provides comprehensive validation capabilities for Hubble Ready devices over Bluetooth Low Energy (BLE). It wraps the `hubblenetwork ready` CLI commands to enable systematic testing of device discovery, characteristic reads/writes, and the complete provisioning workflow.

The framework is designed for:
- **Device validation** - Verify BLE connectivity and device characteristics
- **Encryption testing** - Validate key writes and encryption mode detection
- **Configuration testing** - Test EID configuration updates
- **Time synchronization testing** - Verify device time reads/writes
- **Integration testing** - Execute and validate the complete provisioning flow
- **Debugging** - Diagnose BLE connection issues and ATT protocol errors

## Test Prerequisites

### BLE Adapter Requirements

- **macOS**: CoreBluetooth (must run in GUI session, not SSH)
- **Linux**: BlueZ stack (user must be in `bluetooth` group)
- **Windows**: Compatible BLE stack with Windows Runtime support

### Permissions

- **macOS**: Bluetooth permission granted to Terminal/iTerm
- **Linux**: User in `bluetooth` group: `sudo usermod -a -G bluetooth $USER`
- **Windows**: Administrator privileges may be required

### Environment Variables (for provisioning tests)

```bash
export HUBBLE_ORG_ID="your-org-id"
export HUBBLE_API_TOKEN="your-api-token"
```

These are only required for the `provision` command which registers devices with the Hubble backend.

## Available Test Commands

All test commands support `--format json` for structured output suitable for automated validation. Always use JSON format for testing to enable programmatic result verification.

### Discovery Tests

#### Test: Device Discovery (`scan`)

Scan for Hubble Ready devices advertising the 0xFCA7 service UUID.

**Command:**
```bash
hubblenetwork ready scan --format json [--timeout SECONDS]
```

**Parameters:**
- `--timeout` (optional): Scan duration in seconds (defau