Jump to content

Jim Kring

Members
  • Posts

    3,905
  • Joined

  • Last visited

  • Days Won

    34

Community Answers

  1. Jim Kring's post in Unit Testing - Preferences? was marked as the answer   
    Hey Guys,

    I just want to mention that JKI is committed to making sure that VI Tester works well in LabVIEW. We can't live without it at JKI and it's going to continue to be improved.  We've been really busy lately, so that's why there hasn't been a new version pushed out.
     
    We see the LV UTF as addressing a totally different market need than VI Tester.  As I see it: UTF is great for people who want to show 100% test coverage through its static analysis tools -- NI created it to address the needs of people developing for regulated industries.  VI Tester is great for people who want to do better and faster software engineering in LabVIEW -- JKI created it to help test object-oriented (and other) LabVIEW applications using the industry-standard xunit architecture.

    I can't comment on time-frames, but please stay tuned and don't give up on us.  BTW, VIPM 2013 SP1 (one of the areas where we've been busy) was just released (do a check for updates)!  We couldn't have done that without VI Tester.
  2. Jim Kring's post in Intended OpenG installation and update flow? was marked as the answer   
    Hey Ryan.  Yes, that's right. The main OpenG Toolkit is just a simple way to install everything. There's actually nothing in the package itself -- it just declares dependencies on all the individual packages.
  3. Jim Kring's post in Duplicate OpenG palette object names was marked as the answer   
    I was on a roll and fixed/released the new OpenG Time and Array libraries too, so this issue should be resolved for now.
     
    Please let me know if there are any issues once you upgrade to the new versions.
×
×
  • Create New...

Important Information

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