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

Create testing checklist #343

Open
VivaanBahl opened this issue Mar 3, 2016 · 3 comments
Open

Create testing checklist #343

VivaanBahl opened this issue Mar 3, 2016 · 3 comments
Assignees

Comments

@VivaanBahl
Copy link
Contributor

Normally when software goes out to test we forget to do something that sets us back by about an hour. Previous instances have included:

  • Forgetting to turn on the radio before internal power (snaps steering linkage)
  • Needing to put the brake override in rather than needing to pump and forgetting the pump
  • Not clearing the JVM's lock on serial ports after a faulty disconnect
  • using the wrong COM ports on the system

It would be nice if we had a small checklist that we run through before we take the buggy out to test, so we can skip debugging issues we shouldn't and get to actual testing

@TrevorDecker
Copy link
Contributor

I agree that a check list would be nice, and useful to get people trained on how to operate the buggy. But I really think that we should fix the root of the problems.

https://github.com/CMU-Robotics-Club/RoboBuggy/wiki/Testing-Procedure

@ramensandwich
Copy link
Collaborator

I like the idea of a checklist or a guide book! We can create a systematic approach for prepping, running, and testing the buggy much like flight controllers do

@TrevorDecker
Copy link
Contributor

If we do this I would like to have records kept about which steps fail. For instance we should log on when a specific sensor failed.

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

No branches or pull requests

3 participants