IIWII Robotics
  • VEX Engineering Notebooks
    • Overview
    • Notebooking Best Practices
    • Understanding the Engineering Notebook Rubric
      • Engineering Notebook Scoring
      • Engineering Design Process Categories
        • Identify the Problem
        • Brainstorm, Diagram, or Prototype Solutions
        • Select Best Solution and Plan
        • Build and Program the Solution
        • Test Solution
        • Repeat Design Process
      • Additional Categories
        • Innovation/Originality
        • Usability and Completeness
        • Record of Team and Project Management
          • Time Management
          • Team Management
          • Resource Management
        • Notebook Format
    • Parts of a Notebook (Sections)
      • Cover Page
      • Team Overview / Introduction
      • Table of Contents (TOC)
      • Engineering Design Process (EDP)
      • Engineering Notebook Format
      • Game Overview / Analysis
      • Design Brief
      • Notebook Entries
        • General Entry
        • Team Meeting
        • Time Management
        • Resource Management
        • EDP Entries
          • Identify the Problem
          • Research
          • Brainstorm / Evaluation
          • Build / Program
          • Test
          • Repeat Design Process
      • Competition Writeup
      • Innovate Submission
      • Appendix
        • References
    • Engineering Notebook Resources
  • Interview
    • Overview
Powered by GitBook
On this page
  1. VEX Engineering Notebooks
  2. Parts of a Notebook (Sections)
  3. Notebook Entries
  4. EDP Entries

Test

PreviousBuild / ProgramNextRepeat Design Process

Last updated 1 year ago

Test entries should contain try and contain the items noted in the rubric such as recording the key steps to test the solution and any test results.

As previously noted in the ‘understanding the test solution section’ there are a few items we have looked at to be included in these types of entries.

Procedure

What tactic was used to perform the test? Were there specific steps used to ensure the robot performed as expected?

Results

What results were achieved and were they expected or not?

Analysis

Do the results reflect the intended outcome? If not, what does the team think needs to be done in order to achieve the expected outcome.

The below example pages demonstrate data that was collected during a team meeting/practice and analysis of the cumulative data over a period of time to review how the drivers performance, and thus the robot, was doing. This is just one aspect of how testing could be notated in the notebook.

Paired Test Entries

Below are a couple additional examples of testing entries that give some explanation with associated data.