Jump to content

All Hail JKI!


Recommended Posts

Understanding the benefits of unit testing is one thing--experiencing the benefits of unit testing is a whole 'nother feeling.

Even internally at JKI, every few months someone says "wow, unit testing really saved me on xyz". I'm glad that you're getting some value out of your time investment!

Thank you JKI!

Thank you too! Keep on feeding us suggestions on how to improve VI Tester as well, we're definitely listening :)

  • Like 2
Link to comment

I'm glad that you're getting some value out of your time investment!

Me too... but to be honest I'm more grateful for the time *you* invested in creating and releasing an awesome tool. :worshippy: I'm sure my investment was a pittance compared to yours.

I did experience one inconvenient issue. After opening VIT, running some tests, and closing it, opening it again would cause an insane object error and LV would exit. I had to close the project and reopen it before starting VIT again. This is with LV9 sp1, Win7, and the latest version of VIT. It could be part of LV's object growing pains or something unique in my environment. I haven't had time to investigate the error at all and while inconvenient, it wasn't a big enough problem to prevent me from using the tool.

One minor wish--I use the project dependencies folder a lot. Is it possible to wrap all those dependencies in a library?

Link to comment

One minor wish--I use the project dependencies folder a lot. Is it possible to wrap all those dependencies in a library?

Wow, I didn't know that you could use the dependencies folder for something useful. I use it only as a sort of garbage collector of things that I don't care about that happen to be in my project (I thought that was all it could do). How do you use the dependencies folder?

(Also - yes I can look into wrapping all dependencies in a library).

Link to comment

Wow, I didn't know that you could use the dependencies folder for something useful.

Sure... to figure out what my project is still dependent on. ;)

Mostly I use it for project maintenance when I'm refactoring and cleaning out dead code. During development I end up with a lot of vis (and classes and libraries to a lesser extent) that I used for preliminary work but have since discarded as the application evolves. I don't want to delete them from the repository or my hard drive unless I'm sure there aren't any lingering dependencies. Right-click, remove from project, check the dependencies folder to see if it showed up there.

It's really useful when trying to disentangle someone else's code to exact a bit of useful functionality, or when replacing one library with a functionally similar library. (Say... switching from LapDog Message Library v1 to LapDog.Messaging v2.)

I've also used it in the past when I've had private packages I've deployed using VIPM but haven't created palettes for. I don't really want them to be part of the project, but I do need them to be accessable.

Link to comment
  • 4 weeks later...

Sure... to figure out what my project is still dependent on. ;)

Mostly I use it for project maintenance when I'm refactoring and cleaning out dead code. During development I end up with a lot of vis (and classes and libraries to a lesser extent) that I used for preliminary work but have since discarded as the application evolves. I don't want to delete them from the repository or my hard drive unless I'm sure there aren't any lingering dependencies. Right-click, remove from project, check the dependencies folder to see if it showed up there.

It's really useful when trying to disentangle someone else's code to exact a bit of useful functionality, or when replacing one library with a functionally similar library. (Say... switching from LapDog Message Library v1 to LapDog.Messaging v2.)

I've also used it in the past when I've had private packages I've deployed using VIPM but haven't created palettes for. I don't really want them to be part of the project, but I do need them to be accessable.

Wow, thats a great tip!!

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

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