Request for Feedback on TestStand Source Code Control Support

[Lars_L]

Hello!

I am currently looking for feedback on TestStand's support of source code control (SCC) from our existing customers. Here are a few questions that I have:

1. Are you currently using TestStand with a source code control provider? If so, what SCC provider are you using? AccuRev, ClearCase, CVS, Git, Mecurial, Merant PVCS, MKS Source Integrity, Perforce, Subversion, Team Foundation Server (TFS), Visual Source Safe, Other (please specify)
2. If you are using SCC with TestStand, are there any general functionality or feature gaps that you'd like to see implemented in future versions of TestStand?

To answer, just reply to this post. Thanks!

Lars

National Instruments

[j_dodek]

Hi Lars,

We are using Subversion and there were have many feature gaps.

I am having a contribution next week on the German VIP Days 2012, dealing  excatly with this topic.

If you also participate, we can make an appointment after contribution to discuss about or you may forward

it to the German Ni-TestStand Product Manager.

You may ask the administator to get my e-mail address.

Regards

juergen 

[Lars_L]

Hey juergen,

Thanks for the reply! The list of sessions for the German NI Days happened to cross my desk and I wanted to track down the presenter to get more information so this worked out quite nicely. I'm emailing you now to discuss the details of your presentation. Thanks!

Lars

National Instruments

[Josh_W]

We use TortoiseSVN (a shell extension) to connect to Subversion servers hosted both internally (ours) and externally (our customer's).

My biggest complaint is that we have TestStand type files that are under source code control, and diffing those is annoying and sometimes difficult using the type differ tool; but that's not specific to source code control.

Unfortunately, I'm still stuck on 4.2.1 (the version my customer uses), so I can't comment on the updated TestStand diff/merge tool.

[david_jenkinson]

Hi,

We've used Perforce with teststand for close to 6 years.   There is a gripe I have.  In order to use SCC and make it conveniently accessible and seamless in teststand, you need to have a workspace defined.  That is all fine and well, however the pain in using a workspace, at least for me, is that it is not auto-populating.  That is, when you define a directory in your workspace/project, and add a file to the directory via windows explorer or other means, the workspace does not detect it.  You need to manually add the file in the workspace as well.  For us and our project, this becomes unweildy, and as a result, I have always just used the P4V client, and go back and forth between teststand and the client when working, hence I don't enable scc support in teststand for this reason.  I did notice that labview project files had an update a while back involving auto-populating directories, I'm  hoping this capability will make it into teststand workspaces/projects as well in a future release.

Thanks

David Jenkinson

[david_jenkinson]

And to add to my previous post, it would be great to have it auto-populate code modules of sequences in the project as well.

Thanks

David J.

[shew82]

I don't use the TestStand source code control because we use subversion (so, instead, we uses TortoiseSVN's Explorer add-in). I always find it surprising that NI's source code control support (on all products, not just TestStand, lacks SVN support)

[j_dodek]

Hi

Just a presentation that shows how SVN could be integrated in NI-TestStand.

http://natinst.de/2012/events/vip/downloadfiles/01_mittwoch/pruefstandsautomatisierung/06_dodek_mtu....

Regards

Juergen

[shew82]

unfortunately my German is practically non-existent, so I wasn't able to understand the text of that presentation, but it looks to be very different so the simple integration that NI offers for Perforce and Microsoft version control systems.