Back to projects
Testing and AutomationWeb PlatformTypeScriptTest Automation

Sonace Beta Portal

Manufacturing test and validation portal for audio product beta program with traceability and reporting

Problem

Beta programs for hardware products require rigorous tracking: which units went to which testers, what issues were found, what firmware versions were tested, and how to connect feedback to specific serial numbers.

Without a centralized system, feedback lives in scattered emails and Slack threads, making it impossible to answer: "Which units failed acoustic tests?" or "Has firmware v2.3 been validated across all beta units?"

Approach

The Sonace Beta Portal is a web-based platform for managing beta hardware units, tracking test results, and maintaining traceability from serial number to firmware to test outcomes.

Key Requirements:

  • Unit registry: track every beta unit (serial number, firmware version, tester assignment)
  • Test result submission: testers upload acoustic measurements, subjective feedback, issue reports
  • Firmware coordination: link test results to specific firmware builds
  • Traceability: map issues back to specific units/configurations for root-cause analysis

What I Built

Backend (Node.js + Express + TypeScript):

  • RESTful API for unit management, test submissions, and reporting
  • Postgres database with schemas for units, testers, test results, firmware builds, issues
  • File upload service for test data (audio files, measurement CSVs)
  • Notification system (email alerts on test failures or critical issues)

Frontend (React + TypeScript):

  • Unit dashboard showing all beta units, their status, and latest test results
  • Test submission form with validation (required fields, file formats)
  • Firmware version tracker (which units have which builds)
  • Issue board (similar to Jira): link issues to units, firmware, test cases
  • Reporting page with exportable summaries (pass/fail rates, issue counts by category)

Integration Layer:

  • APx measurement parser (imports audio test results automatically)
  • Firmware version API sync (pulls latest builds from engineering repo)
  • Slack webhook for real-time notifications

Architecture

Diagram placeholder: Beta Testers → Web Portal → API + Database → Reporting + Notifications

Beta Testers (submit test results)
    ↓
Web Portal (React UI)
    ↓
API Layer (Express + TypeScript)
    ↓
Database (Postgres: units, tests, issues, firmware)
    ↓
Reporting Engine (aggregations, exports)
    ↓
Notifications (Email, Slack)

Outcomes

Qualitative Impact:

  • Eliminated email/Slack chaos: all beta feedback now lives in one place
  • Reduced time to generate beta program reports from days (manual spreadsheet wrangling) to minutes (dashboard export)
  • Improved firmware coordination: engineering knows exactly which builds have been validated
  • Enabled targeted recalls: when a firmware bug is found, quickly identify which units need updates

What worked well:

  • Unit-centric data model made traceability straightforward
  • Test result parser reduced manual data entry (testers just upload APx CSVs)
  • Slack integration kept the team informed without constant portal checking

What I'd improve:

  • Add automated test result analysis (flag outliers automatically)
  • Build mobile-friendly UI for field testing scenarios
  • Integrate with manufacturing ERP for seamless production handoff
  • Add statistical trending (e.g., "is this firmware version improving acoustic performance?")

What's Next

  • Expand beyond beta: use same platform for production validation tracking
  • Add support for multiple product lines (not just audio devices)
  • Build API for contract manufacturers to submit test results directly
  • Create automated reports for regulatory submissions (FCC, CE)
Back to projects