{{ theme.skipToContentLabel || 'Skip to content' }}

Dustac Environmental Monitoring Dashboard

Test Plan

Version: 1.2 Date: January 5, 2026 Project: Dustac Environmental Monitoring System Status: Draft


Document Control

VersionDateAuthorDescription
1.02025-12-02Dustac QA TeamInitial test plan for Phase 5+ testing
1.12025-12-20Dustac QA TeamAdded Dust Ranger feature testing
1.22026-01-05Dustac QA TeamAdded Device Timeline Data Gaps visualization testing

Document Structure

This test plan has been split into multiple documents for better maintainability:

Core Documents

DocumentDescriptionSections
TEST_PLAN.md (this file)Overview, introduction, and document index1
TEST_STRATEGY.mdTesting approach, assumptions, constraints, and risks2-3
TEST_CASES.mdPlanned tests and test case management4, 7
TEST_SCOPE.mdTest progression and feature testing scope5-6
TEST_ENVIRONMENT.mdTest environment, tools, and data9
TEST_EXECUTION.mdDefect tracking, deliverables, schedule, roles, metrics, communication8, 10-14
TEST_APPENDICES.mdTemplates, glossary, and reference materialsAppendices A-K

Test Type Specifications

DocumentDescriptionTools
TEST_UNIT.mdUnit testing specifications, test cases, and code examplesVitest, RTL
TEST_INTEGRATION.mdIntegration testing for services, APIs, and databaseVitest, Supabase
TEST_SYSTEM.mdSystem testing for functional, performance, security, usabilityManual, k6
TEST_E2E.mdEnd-to-end testing with Playwright, page objects, user journeysPlaywright

1. Introduction

1.1 Overview

This Test Plan defines the comprehensive testing strategy, approach, and execution methodology for the Dustac Environmental Monitoring Dashboard system. The system is a cloud-native web application built to enable mining operations to collect, analyze, visualize, and report environmental dust monitoring data in compliance with regulatory requirements.

Project Identification:

  • Project Name: Dustac Environmental Monitoring Dashboard
  • Project Code: DUSTAC-2025
  • Current Phase: Phase 5+ (Extended Features & Polish)
  • Technology Stack: React 19, TypeScript 5, Supabase (PostgreSQL), Cloudflare Pages
  • Deployment Model: Cloud-hosted SaaS application

Document Purpose:

This test plan serves multiple critical functions:

  1. Quality Assurance Blueprint: Establishes comprehensive testing framework ensuring system meets functional, performance, security, and usability requirements
  2. Stakeholder Communication: Provides transparency into testing scope, approach, and acceptance criteria for technical and business stakeholders
  3. Risk Mitigation: Identifies potential quality risks and defines testing strategies to detect and prevent defects before production deployment
  4. Resource Planning: Documents testing resource requirements, timelines, and responsibilities for effective project planning
  5. Compliance Documentation: Provides audit trail demonstrating due diligence in quality assurance processes

1.2 System Description

The Dustac Environmental Monitoring Dashboard is designed for mining operations that deploy DustRanger monitoring devices to measure airborne particulate matter concentrations.

Core System Functions:

  • Data Ingestion: Automated data collection from DustRanger devices via Edge Function scrapers
  • Data Management: Multi-site support with RLS-based user data isolation
  • Visualization & Analytics: Interactive dashboards with KPIs, charts, and climate data correlation
  • Report Generation: Automated PDF reports with AI-generated chart descriptions
  • Integration Points: BOM weather API, Dustac scraper API, Google Gemini AI

User Roles:

  • Standard Users: View data, generate reports, manage their own site data
  • Administrators: Multi-site management, user administration, system configuration

1.3 System Architecture

┌─────────────┐
│   User      │
│  (Browser)  │
└──────┬──────┘
       │ HTTPS

┌─────────────────────────────────┐
│  Cloudflare Pages (React SPA)   │
└──────┬──────────────────────────┘
       │ Supabase Client SDK

┌─────────────────────────────────┐
│      Supabase Platform          │
│  • PostgreSQL (RLS enabled)     │
│  • Auth Service (JWT)           │
│  • Storage (Object Store)       │
│  • Edge Functions               │
└──────┬──────────────────────────┘
       │ External APIs

┌─────────────────────────────────┐
│    External Integrations        │
│  • BOM Weather API              │
│  • Dustac Scraper API           │
│  • Google Gemini AI             │
└─────────────────────────────────┘

1.4 Document Scope & Audience

Document Scope:

Included:

  • Functional testing of all feature modules
  • Non-functional testing (performance, security, usability, accessibility)
  • Integration testing with external APIs
  • Database testing including RLS policies
  • End-to-end workflow testing
  • User acceptance testing (UAT)

Excluded:

  • Third-party service internal testing (Supabase, Cloudflare)
  • DustRanger device hardware testing
  • Penetration testing (separate security assessment)

Intended Audience:

AudiencePrimary UseKey Documents
QA EngineersTest execution, defect loggingTEST_CASES.md, TEST_EXECUTION.md
DevelopersUnderstanding test requirementsTEST_STRATEGY.md, TEST_SCOPE.md
Project ManagersTimeline tracking, resource planningTEST_EXECUTION.md
Business StakeholdersAcceptance criteriaTEST_SCOPE.md
DevOps EngineersTest environment setupTEST_ENVIRONMENT.md

1.5 Quick Reference

Test Commands:

bash
pnpm test:unit          # Run Vitest unit tests
pnpm test:e2e           # Run Playwright E2E tests
pnpm test               # Run all tests
pnpm lint               # Run ESLint

Key Coverage Targets:

  • Unit Tests: ≥85% for services/utilities, ≥70% for components
  • E2E Tests: ≥75% for critical user journeys
  • Overall: 96% of in-scope features tested

Test Environments:

  • Development: Local Supabase (Docker)
  • Staging: Production-equivalent cloud environment
  • Production: Live user operations

Core Documents:

Test Type Documents:


Document Location: /docs/testing/TEST_PLAN.mdLast Updated: January 5, 2026 Version: 1.2 (Draft)