GUI WPILib Test Harness Released

[jwakeman]

I also downloaded this and got it up and running this past weekend. I agree this project has some real potential. Dustin, Brian, what do you see as the next steps/features to implement for the project? I would also like to help!

[virtuald]

Originally Posted by jwakeman

I also downloaded this and got it up and running this past weekend. I agree this project has some real potential. Dustin, Brian, what do you see as the next steps/features to implement for the project? I would also like to help!

Did you use the version in SVN or the last file release? I think it's slightly broken right now... though I don't exactly recall where I left the code.

I believe the thing I was working on before I dropped it was porting the rest of the WPILib components to the test harness, and trying to use more of the actual source code for WPILib in the work.

If you guys want to do work on it, join the FIRSTForge project and I'll give you SVN access.

[jwakeman]

I downloaded it from the file releases, WPILibTestHarness-0.1.1. It seemed to be working fine. I was able to run the DefaultCode project and see the solenoid lights flashing in a nice sequence. I am a member of FIRST forge as jwakeman. I can't guarantee I will be submitting anything anytime soon but I would like to be able to get the latest code from the svn to study.

One question for you though. I can see how you can drive outputs and see the solenoid light for example. But if I declared a digital input for example how would I drive the value of that input? Is there some way to drive the digital input high/low from outside of the robot code under test? Or is that a TODO?

[brian3795]

I tried to browse the source, but I was denied anonymous access. I'll see about registering an account.

Jwakeman, I've got this compiled using VC++ Express 2010 (for whatever reason, I was unable to download 2008) as well as the latest dev version of wxWidgets. There were a few minor changes required. Right now, I'm getting error messages on the PWM output widgets (all the other widgets seem to be present and accounted for). I'd like to try compiling against the latest WPILib code.

[Robby Unruh]

Does this only work for C++?
It would be awesome if you'd provide Java/LabVIEW support.

[jwakeman]

It does not currently show any project join requests. :-/

I just sent my join request.

[virtuald]

Project memberships accepted.

No Java/LabVIEW support. I think LabVIEW already supports some kind of test environment where you can test your code outside of the robot, though I've never used LabVIEW myself.

I suspect that doing this same kind of project for Java would be pretty easy if someone wanted to tackle it, but it won't be me since my Java skills are non-existent

[dcarr]

Is there going to be an update to the test harness? I'm working with Python while some other team members are doing Java and I'd like to be able to test it on my PC. Your google code link appears to not work.

[virtuald]

Originally Posted by Friarbots

Is there going to be an update to the test harness? I'm working with Python while some other team members are doing Java and I'd like to be able to test it on my PC. Your google code link appears to not work.

At some point, when it becomes useful to me again, I will update it. However, since the test harness is C++, and we're not using C++, I don't anticipate this happening in the near future. If I create a python test harness, then I anticipate it will be released as a separate project as a component of RobotPy.

It's at FIRST Forge now, I updated the link on my website: http://firstforge.wpi.edu/sf/project...b_test_harness

If you're using python, you might be interested in looking at our 2011 code to see how we did testing. Python makes it significantly easier to do testing. Also see this thread.

[virtuald]

Originally Posted by jwakeman

One question for you though. I can see how you can drive outputs and see the solenoid light for example. But if I declared a digital input for example how would I drive the value of that input? Is there some way to drive the digital input high/low from outside of the robot code under test? Or is that a TODO?

Hmm. I feel like I implemented it... it might be that if you declare it as an input, then it will behave as an input when you click it. That sounds like something I would do

[brian3795]

Originally Posted by virtuald

If you guys want to do work on it, join the FIRSTForge project and I'll give you SVN access.

Don't know how much time I'll have, but I'm game. Sent a project join request...

[virtuald]

Originally Posted by brian3795

Don't know how much time I'll have, but I'm game. Sent a project join request...

It does not currently show any project join requests. :-/