Jump to content

JKI

JKI Team
  • Content Count

    482
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by JKI

  1. Yes, EasyXML works great on LabVIEW Real-Time (RT). However, EasyXML depends on some OpenG Array Tools (oglib_array) package, which has some version dependencies you should be aware of: On LabVIEW Real-Time 2009 or newer, you should have no problems. On LabVIEW Real-Time 8.x, you should install oglib_array 2.7 or earlier. The reason for this is that oglib_array 3.0 added support for LabVIEW Classes and Objects (objects-oriented programming), which is supported in LabVIEW 8.x, but is not supported in LabVIEW Real-Time 8.x (and therefor causes the OpenG Array Library and EasyXML to be
  2. For some reason, upgrading to LabVIEW 8.6.1 can cause the "VI Server: Exported VIs" settings to get reset in a way that prevents VIPM from being able to connect. To fix this, do the following: LabVIEW's VI Server permissions are not configured correctly for VIPM. In the LabVIEW options dialog (Tools>>Options) go to the "VI Server: Exported VIs" page and ensure that you entered a value of "*" (see below).
  3. This is the Known Issues list for VI Tester 1.1.2. For issues fixed in current & previous releases of VI Tester, please see the Release Notes. Known Issues Case 10909: 'Run Single Test' generates an error when pressed after reloading a project Reloading a project does not disable the 'Run Single Test' button which makes it possible to press the button when no test is selected, resulting in an invalid test selection error dialog. Workaround: Do not press 'Run Single Test' until you've selected a test on the test tree after reloading project. Case 10911: VI Tester UI Doesn
  4. VI Tester requires the following software: LabVIEW 8.2.1 or greater on any operating system VI Package Manager 2.0 or greater (free download)
  5. Here are some of the things that are on our radar. If you've got ideas or feedback please post them in VI Tester forum -- everything here is open for discussion. Run Test Programmatically -- high-level VIs for running tests programmatically (instead of from the VI Tester GUI) Right-click on tests in VI Tester GUI: Skip / Don't Skip, Run Test, Open Test VI Performance optimizations Inheritance and overrides of custom Test Cases and Test Suites Export test report 'Detailed Status' to printer/disk/clipboard Improved project file integration
  6. Moved here: https://github.com/JKISoftware/JKI-VI-Tester
  7. Background VI Tester is a LabVIEW implementation of the xUnit test framework architecture. It is an object-oriented framework with several core classes and a graphical user interface for loading and running tests. Terminology VI Tester - Graphical Test Runner UI The graphical user interface that loads and runs tests (which you launch by selecting Tools >> VI Tester >> Test VIs... from the LabVIEW menubar). When you open a Project, Test Case, or Test Suite, VI Tester searches for tests in Test Cases and Test Suites. You can then run the tests. Core Class: TestCase.lvclass
  8. JKI

    Debugging Tests

    VI Tester is a tool to help you pinpoint problems with your code. As your application evolves, you will want to regularly run unit tests to validate that none of the tests fail. If a test fails, it generally means that there is a problem with the code that is being tested - but it can sometimes mean that there is a bug in the test itself. Either way, you'll want to fix the problem. A test can fail in three places: in the actual test method (most likely), but also in "setUp.vi" (called once before each test method is executed) and "tearDown.vi" (called once after each test method is exe
  9. Add a new test case to your project. A "test case" is a special LabVIEW class that contains unit test methods. VI Tester recognizes unit test methods as members of a test case class whose name starts with "test". To get started, please watch this brief tutorial video and then follow the walkthrough below. You can create a new test case by selecting Tools >> VI Tester >> New >> Test Case... from the menubar of the Project Explorer window. Browse to a folder where you want to create the test case, type a name for the test case, and press the "
  10. JKI

    Designing Tests

    Unit tests should be designed around the following principles: Unit tests should be simple - you don't want to spend time debugging tests Unit tests should only test one thing (a "unit" of code) - unit tests should help you pinpoint problems so performing multiple tests within a unit test defeats this purpose Unit tests should be independent of other unit tests - they should not depend on or affect other unit tests To facilitate these principles, unit tests should be designed to work within a test harness. A test harness is a set of VIs called 'setUp.vi' and 'tearDown.vi' that run
  11. Please watch this short tutorial on how to run unit tests from VI Tester. After watching the video, you can follow them step by step in the walk through below. Open the VI Tester example project located at: \examples\JKI\VI Tester\VI Tester Example.lvproj The example project, shown below contains two TestCase classes: Expand the "Merge Errors TestCase.lvclass" class in the tree to show the class members. You will find several member VIs whose names all begin with "test" -- these are unit tests that validate functionality of the "Merge Errors" VI that ships with LabVIEW.
  12. You have a few minutes and just want to learn what VI Tester is about. VI Tester helps you perform unit testing on your VIs. Unit testing is a way to validate that your code works at the lowest (i.e. unit) levels. In LabVIEW, the lowest level of testing is the VI. When you write effective unit tests you get two benefits: 1) you can verify that when you modify code, you don't create unintended bugs 2) when your tests fail, you can quickly pinpoint the root cause of your failure. To start, you launch VI Tester window from the LabVIEW Tools Menu. Next, open a project file that co
  13. Moved here: https://github.com/JKISoftware/JKI-VI-Tester/wiki/VI-Tester-FAQ
  14. Download and Install VI Tester from JKI Labs Note: The full-featured version of the JKI VI Tester is licensed under the JKI Toolkits Evaluation License. To download and install VI Tester, you will need VIPM (VI Package Manager), which is made freely available by JKI. If you don't already have VIPM installed, you can get it from our website, here. Also, make sure to check the System Requirements for VI Tester. Installing VI Tester takes less than a minute. Here are the steps: Update Your Package List Install VI Tester Restart LabVIEW 1) Update Your Package List
  15. What's New in VI Tester 1.0 Initial public release.
  16. Moved here: https://github.com/JKISoftware/JKI-VI-Tester/wiki/Getting-Started-Guide-and-Resources
  17. VI Tester™ (jkisoft.com/vi-tester) Copyright © 2007-2009 James Kring, Inc. All Rights Reserved. VI Tester, JKI Labs, and other JKI Software logos and design are trademarks of James Kring, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. OpenG Toolkit libraries (openg.org) The OpenG Toolkit libraries used in VI Tester are licensed under the terms of the BSD (http://www.opensource.org/licenses/bsd-license.php) and are copyright of the following: 2002 Cal-Bay Systems, Inc., 2002 Jean-P
  18. Hi Jed, Sorry for the trouble. BTW, we've got some info in our FAQ about this: Can I install VIPM on Windows Vista? We haven't added any special features for Vista, yet, as it's still not officially supported. But, it's on our roadmap. Thanks, -Jim
  19. We at JKI are excited to announce the release of VIPM 2.0.3 on the Mac, Linux, and Windows operating systems. This release includes fixes for several minor issues as well as minor usability improvements. Please see the VIPM 2.0.3 Release Notes page for more information. To download and install the latest version of VIPM, visit http://jkisoft.com/vipm/.
  20. jkisoft.com First, you should ask your IT department to allow access to jkisoft.com (this one is required, since this is where VIPM gets the package list from). *.dl.sourceforge.net Next, you'll need access to one or more sourceforge mirrors: *.dl.sourceforge.net (where * can be any one of the sourceforge mirror names). For example: easynews.dl.sourceforge.net kent.dl.sourceforge.net switch.dl.sourceforge.net superb-east.dl.sourceforge.net puzzle.dl.sourceforge.net Here is the most recent set of mirrors and their geographic locations: easynews: Phoe
  21. I can see a case for having VIPM bring itself to the front after the package build is complete -- it does present a dialog telling the user that the build has completed. I'll pass this along to the rest of the VIPM developer team. The window title of VIPM's package building window is "PACKAGENAME - VIPM - VI Package Builder". Note that PACKAGENAME does not include the version number.
  22. The reason for this is that build hook VIs run in the target LabVIEW development environment and VIPM is its own executable application. So, opening a modal dialog in LabVIEW won't make the build hook's dialog come frontmost, if LabVIEW isn't frontmost (which it won't be, since you're probably interacting with VIPM). Also, build hooks can do anything they like, but VIPM has no way to know that you intend them to have user interaction. There are at least a couple possible ways to address your use case. 1) VIPM could possibly make LabVIEW frontmost while it is running the build hook
  23. Nowhere. The paid version of EasyXML does not need to be activated or unlocked. The serial number sent to you when you purchased EasyXML is simply for your records. You may need this SN in the future for upgrades and special offers to existing customers.
  24. After you have completed the download and installation process, restart LabVIEW. You should then be able to find the EasyXML VIs in the Functions palette at JKI Toolkits >> EasyXML (shown below). See also: How come I can't see EasyXML in the Functions palette?
  25. One of the trickiest little features of EasyXML is creating scalar elements with attributes. Granted, it's not entirely obvious -- but, don't worry, it's still as easy as creating a cluster Before we show you how it's done, let's review some of the EasyXML basics. (If you'd like to skip the review, scroll down to the Scalar Elements with Attributes section, below.) Scalar Elements Scalar elements can be created from strings, Booleans, numerics, and other scalar LabVIEW data types. For example, here is a scalar numeric: EasyXML treats clusters and arrays as compound element
×
×
  • Create New...

Important Information

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