From 8fe4052f64e5755092ba1237fc99429ee54a4dd5 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 21 Mar 2026 17:12:03 +0000
Subject: [PATCH 1/2] Initial plan


From 513e2d9f62324d93b52211896961b5a7685bfc97 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 21 Mar 2026 17:14:26 +0000
Subject: [PATCH 2/2] Add How to Test a Prototype page to Build Season wiki

Co-authored-by: TaylerUva <8679670+TaylerUva@users.noreply.github.com>
Agent-Logs-Url: https://github.com/FRCTeam3255/Wiki/sessions/201938e4-c81e-4426-ab73-d2c885b1b129
---
 Build Season/How to Test a Prototype.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 Build Season/How to Test a Prototype.md

diff --git a/Build Season/How to Test a Prototype.md b/Build Season/How to Test a Prototype.md
new file mode 100644
index 00000000..75e36a9a
--- /dev/null
+++ b/Build Season/How to Test a Prototype.md	
@@ -0,0 +1,16 @@
+# How to Test a Prototype
+
+When testing a prototype, it is important to gather data in a consistent and structured way so that results are meaningful and comparable.
+
+## Data Collection Guidelines
+
+1. **Limit your variables** - Change one thing at a time so you can clearly identify what is causing a change in performance
+2. **Check battery between tests** - Battery voltage affects performance; always verify battery charge before each test to ensure consistent results
+3. **Record with video** - Film every test run so you can review details you may have missed during the test
+4. **Write out all variables** - Before testing, document all relevant variables such as:
+   - Angle
+   - Speed
+   - Battery voltage
+   - Compression
+   - Any other mechanism-specific settings
+5. **Write out results** - After each test, record the outcome, including metrics such as accuracy percentage