Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Testing Framework Architecture #53

Open
EdHurtig opened this issue Nov 5, 2017 · 0 comments
Open

Define Testing Framework Architecture #53

EdHurtig opened this issue Nov 5, 2017 · 0 comments
Assignees

Comments

@EdHurtig
Copy link
Member

EdHurtig commented Nov 5, 2017

Design a flexible test harness for performing tests on various subsystems.

Example: A test for the brake modules could involve repeated clamp/release cycles of a brake module. The brake module would be connected to an Arduino or a Paradigm Node Board and would run some firmware written by us. The firmware would be communicating with a Host Computer/Server over USB or Ethernet or some other medium. That host computer would also have some form of application to archive the test results.

Things to think about:

  1. What drives the test? The Arduino or the Host Computer?
  2. What is the communication mechanism (USB, Ethernet, Other)
  3. Where/how are the test results stored? Look at existing test results storage mechanisms.

This isn't "think about the specific tests to run" but "what is the unified architecture of the framework and harness to use across all submodule tests". It is important to keep things consistent and unified to make data analysis easy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants