Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/11/2011 in all areas

  1. Over the past couple years I've tried unit testing in various projects. Sometimes successful, sometimes not. Even on those rare occasions when I've been successful I usually felt like I was going in circles with my tests, trying to figure out how to best build and organize them. Unit testing was more of a brawl than a ballet. Several months ago I picked up what is now my second favorite book recommendation (right after Head First Design Patterns,) a gem called xUnit Test Patterns. If you're doing OOP, understand patterns, and want to improve your ability to deliver good software, this is the book to get. (There's even lots of information on the website if you don't want to purchase the book.) The book is written for xUnit frameworks so it is a natural fit for JKI's VI Tester. There are a few minor things VI Tester currently doesn't let you do, such as inherit from a test class, but 96+% of the book is directly applicable to your Labview projects.
    3 points
  2. The VIPC will install the version that is needed. So if the VIPC calls for version 1.0 and VIPM sees that version 1.5 is installed, V1.5 will be uninstalled and V1.0 will then be installed. From my understanding, you shouldn't just delete files that VIPM installed. Let VIPM uninstall the files. One of the beauties of VIPM is that packages can have dependencies so you can make sure you have all the code you need.
    1 point
  3. Nope, It affects the users more than NI. Ni are probably more worried that their whole licensing scheme has been compromised since 2009.
    1 point
  4. For formatting the string I would prefer the ISO8601 format. Current timestamp 2011-10-10T17:43Z .
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.