Jump to content

dpnsw

Members
  • Content count

    6
  • Joined

  • Last visited

  • Days Won

    1

dpnsw last won the day on December 16 2015

dpnsw had the most liked content!

Community Reputation

1 Neutral
  1. There are a number of items that are not adequately covered in the documentation OR (in the case of the video) actually show you the wrong way to do things. This is not intentional on JKI's part but rather the result of improvements to the VI Tester which didn't get added to the pinned getting started stuff. Important things to be aware of (tested with LabVIEW 2014 32 bit): *) Don't copy the testExample.vit as per the video as you won't be able to see your tests EVER! The .vit is a template file and the VI Tester ignores all templates. You need to right click on the testExample.vit and select "New from template" and save your VI starting with the word test and ending with .vi (not.vit) eg. test-anything.vi Rob Calhoun also makes the following important points in this post Test Cases that do not have any test methods do not appear in VI Tester hierarchy. (Maybe this is a feature, but it's not what I would expect.) After creating and saving a new test method the Test Case still does not appear in the VI Tester hierarchy. This is because the Test Case (class) has not been saved, so it still has no test methods from the point of the VI Tester Only test methods that start with the word "test" (at least this appears to be case-insensitive) are considered test methods.
  2. is there any active development

    I too would be interested in a reply on this question. From the outside it seems hard to understand where Unit Testing on LabVIEW is going. The fact there are 2 tools is a little confusing but they are both very different in their nature. NI have their tool which has some good points but is suffers from: 1) lack of class support 2) Difficulty in flexibly specifiying input and output values for certain data structures 3) Speed (ie it is not particularly fast) On the other side of the fence is the VI Tester from JKI which is amazing, handles calsses and flexible data types but doesn't appear to be very active (not that I think NI Unit Test is very active either for that matter). It would be nice to get some sort of an idea about how JKI sees the future. I am trying to figure out where I should put my time. I have learnt how to use the NI Unit Test only to crash into it's limitations and now I am trying to learn the JKI VI Tester only to have another set of struggles. It really doesn't help when the instructional videos show earlier versions that if you follow their steps mean your tests won't be discovered. The difference between a .vit and .vi was not something I knew about previously and had to go trawling the groups to find an answer. Some feedback would be helpful.
  3. May have been a firewall problem in the end. Looks like ZoneAlarm is alot less than clear about what it blocks and why. Flipping ZoneAlarm into Game Mode Allow all enabled me to install another package that it was reporting as unable to download.
  4. I have a work around: If I put the following URL into a browser it allows me to download the file and I can then open and install it with VIPM http://www.jkisoft.com/packages/download.php?file=packages/jki_tool_right_click_framework/jki_tool_right_click_framework-1.0.2.208-1.ogp Still don't know why the download fails from within VIPM though.
  5. I have installed VIPM and have successfully installed a variety of packages but the "JKI Right Click Framework" fails. It used to work ages ago but I can't download the main package. I have tried on VIPM 2013 and just updated to 2014 and tried again with the same result. Can anyone suggest what is going on? Error is as follows: Main Package Name: jki_tool_right_click_framework v1.0.2.208-1 Package Name with Error: jki_tool_right_click_framework v1.0.2.208-1 Error Message: VIPM could not download the package jki_tool_right_click_framework-1.0.2.208-1 from the remote server. Error Code: 59 Error Source: Wininet Network Error: HttpQueryInfo; 2F379E22E1B0998BC7FD4C660109B34D:7430006; 42B0A49C07418030C434BD44E4FE00C2:780002; F305327F032D08CD9BD0C20A305B1B26:4100001; F613CC201C17901C57368E65927E649F; 8C3A0DF023870FEE93625F60B8E0713B; OGPM Class.lvlib:707BE83FFDD028FEF8709673F29DCA3C; 532E719EF4833FD7F3F3D218E8A77F77; VIPM Main Window.vi . URL: "http://www.jkisoft.com/packages/download.php?file=packages/jki_tool_right_click_framework/jki_tool_right_click_framework-1.0.2.208-1.ogp". Many thanks David
  6. I have checked Firewall and AV and I think they are OK but I can't update package lists properly. Error listed below. I have checked the URL http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/addq_lib_g#/addq_lib_g#-1.4.5.10.spec'>http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/addq_lib_g#/addq_lib_g#-1.4.5.10.spec and it certainly 404's even on my browser. The check for updates under VIPM option says I am on the latest version which is V12.0.0 build 1780 Is there some config I am missing or anything else I should check. Could I still have a firewall issue even though I can't see that anything is being blocked? many thanks David The log file shows the following: =========== START of VIPM Error Message =========== An internal VIPM Error has occured on: Friday November 09, 2012 at 10:21:41 AM = Automated Message Start = Error 42 occurred at (http response "404". URL Requested: http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/addq_lib_g#/addq_lib_g#-1.4.5.10.spec) 14280DE39C8DAD756B5BEBFD8359AC0C:1 in 78C0506DEFD3CCC86D23FCCA90820135->D030F07D3EB857F827E844D79BB99400->AAEF77B6BF19CEFD015DEA5AD1F9C242 ->OGPM Class.lvlib:7F68E4B89D07A5FA02A89CD464F2E4E8->OGPM Class.lvlib:61E953ABD2F6709B3366915D2B536345->0C2EB955350C6EABE176EFF4F6B989B6->VIPM Main Window.vi . URL: "http://ftp.ni.com/evaluation/labview/lvtn/vipm/packages/addq_lib_g#/addq_lib_g#-1.4.5.10.spec". Possible reason(s): LabVIEW: Generic error. = Automated Message End = = User Defined Message Start = Check for Package Updates from the network. = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 0C2EB955350C6EABE176EFF4F6B989B6 = Error Handler Call Chain End = =========== END of VIPM Error Message ===========
×

Important Information

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