Tag Archive: VI Tester

Don’t Throw Away Your “Throw-Away” Code

Lately, software testing has been on my mind. I’ve been trying to dial in the sweet spot where automated testing is directly profitable by decreasing net development time, and indirectly profitable by increasing the intangible perception of quality. Here’s the problem: unit testing can seem tedious. Prohibitively expensive. Tough to justify. Even intimidating! As a result, applications and application components can easily get starved of any form of automated testing. A colleague let me in on a secret that helps break down these misconceptions. It’s simple, and maybe even obvious, but it’s still a secret worth sharing: a unit is as big

Read More

NIWeek 2011: “Five Clever Debugging Techniques” Slides and Code Now Available

First, I’d like to thank everyone who attended my presentation at NIWeek 2011. I know that the room was a schlep for everyone since it was not in the typical presentation area, so I was really excited that the session was full!  I’d also like to thank Michael Aivaliotis for helping me with impromptu technical support and a special guest appearance during the presentation with great comments about his own debugging tricks and tips. This presentation came about after I was working with several other JKI Engineers and it became obvious that many of us were using debugging techniques that others had

Read More

Speeding Up Large Application Build Cycles with VI Tester

JKI’s VI Tester is a LabVIEW unit testing framework that helps developers write and execute automated tests to guarantee their software components work as designed.  Although this usually means verifying that software components meet certain functional requirements, VI Tester can be used for creating other kinds of software tests, too.  Instead of finding bugs, these tests can do things like perform status and configuration checks on your software, and work around pain points in the LabVIEW build process.  Let’s look at one example. LabVIEW Checks for Broken VIs Late in the Build Process Recently I was working for a JKI customer on

Read More