Midterm Rory

TESTING AND QA STRATEGY (RORY) Topic: Midterm deck Our testing strategy focuses on data accuracy, usability, and reliability. After each CSV import, we compare a sample of dashboard records with the original file to confirm that the measurements, dates, units, locations, and quality-control flags match. We also test blank measurements, duplicate rows, invalid coordinates, and flagged values. The dashboard should identify these problems without crashing, hiding valid information, or displaying misleading results. The main dashboard features are tested manually, including location selection, date filters, charts, tables, login access, and data-quality indicators. We also review the dashboard at phone, tablet, and desktop widths to make sure charts resize correctly, text remains readable, controls are usable, and nothing extends off the screen. Before each demonstration, another team member reviews the completed work using a shared checklist. Any problems are recorded, corrected, and tested again before the feature is considered complete. ALGORITHMIC DESIGN - INGESTION SCRIPT (RORY) Topic: Midterm deck The ingestion script first confirms that the CSV file contains the required columns. It then reads each row, converts dates and measurements into consistent formats, and connects the data to the correct plot or tower location. Duplicate location-and-date records are removed, while measurement columns are converted into standardized database readings. Blank measurements are skipped, invalid coordinates are flagged, and the import results are recorded. Clean data is uploaded to Supabase in batches so one bad row does not stop the entire file. For n CSV rows, the ingestion process takes O(n) time because each row is examined once. With an index on location and timestamp, a typical dashboard query takes O(log n + k) time. The index quickly finds the requested range, and k represents the number of readings returned.