This is a migrated thread and some comments may be shown as answers.

Locking down Test Scripts in Runtime

2 Answers 19 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Josh
Top achievements
Rank 2
Josh asked on 11 Dec 2012, 03:41 PM
We are looking for the correct way to lock down a test script that is being executed on a Runtime license. Essentially we do not want to allow the user to make any changes, edits , deletions etc .. to a test script that has been written on a Full License. We only want them allowed to check out and execute a script and save the results. Does Telerik have a recommened action on how to do this?

2 Answers, 1 is accepted

Sort by
0
Mario
Telerik team
answered on 11 Dec 2012, 11:20 PM
Hello Joshua,

We would normally recommend that you Integrate your project with a Source Control System such as (but not limited to) TFS, but please note that any user on a machine with only Run-Time installed is already locked out from making any changes to existing test scripts. This is essentially the key difference between a Full and Run-Time license. These users can only specify various options related to running the script and publishing results (including to TFS server). For a full list of available options, as well as additional information please see our online documentation regarding the ArtOfTest.Runner and MSTest.

Please let me know whether you have any further questions.

Kind regards,
Mario
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
0
Josh
Top achievements
Rank 2
answered on 11 Dec 2012, 11:24 PM
Thanks we currently use SVN. We just werent sure that Runtime actually enacts that protocol we had read somehwere but werent sure. thanks.
Tags
General Discussions
Asked by
Josh
Top achievements
Rank 2
Answers by
Mario
Telerik team
Josh
Top achievements
Rank 2
Share this question
or