[ASTDan]

Hello,

I am running VI tester with LabVIEW 2009.

I have created about 13 test cases.

When I call VI tester to run my tests it takes a few minutes to load. Is this normal? Is there a setting or technique I can use to speed this up?

Thanks

Dan

[Jim Kring]

Hi Dan,

I'm happy to hear that you're using VI Tester!

This slowness is "expected". It is caused by LabVIEW taking a long time to reserve class members for execution.

We're looking into the best way to solve this problem, We've got some ideas about how to speed it up.

Thanks,

[ASTDan]

Thanks Jim!

Is this a LabVIEW thing? For example when people implement an OO paradigm is "LabVIEW taking a long time to reserve class members" something that needs to be taken into consideration?

I don't have a lot of experience with OO and am trying to learn more about it.

Thanks

Dan

[Jim Kring]

Hi Dan,

It's a LabVIEW thing and only affects us at development/edit time, not run time. Basically, when you load a bunch of classes into two parallel application contexts, it can take a while for LabVIEW to perform certain edit time operations and checks.

-Jim

[ASTDan]

Jim Kring, on Mar 3 2010, 02:46 PM, said:

Hi Dan,

It's a LabVIEW thing and only affects us at development/edit time, not run time. Basically, when you load a bunch of classes into two parallel application contexts, it can take a while for LabVIEW to perform certain edit time operations and checks.

-Jim

Good luck trying to figure out a good solution! I look forward to VI tester updates. So far I like working with VI tester. It is turning out to be an easier transition than I thought.

[Jim Kring]

ASTDan, on Mar 3 2010, 07:10 AM, said:

Good luck trying to figure out a good solution! I look forward to VI tester updates. So far I like working with VI tester. It is turning out to be an easier transition than I thought.

Hi Dan. That's music to my ears!

We were hoping that the object-oriented features of VI Tester (and the xUnit architecture) would make users' lives easier.

We're glad you're a unit testing "convert" and look forward to more VI Tester updates, too. We use VI Tester every day at JKI to test every JKI software product and consulting project that we work on, so you can rest assured that we care about solving this slow-down issue.

Cheers,