View Single Post
  #2   Spotlight this post!  
Unread 04-03-2014, 22:51
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Lint for LabView

The tool that fits your description is called the VI analyzer. It is written in LV and parses LV code to test against certain patterns.

Another reasonable way to discover the issues you list is to run against a simulated robot. If you make it through each mode of auto, tele, and disabled with no error messages, that should exercise a good portion of the code. Other code would depend on button presses and sensor values.

Greg McKaskle
Reply With Quote