I don't think it's possible to migrate from one language to another. Once a project is created around one language, that's it from there forward.
For instance, we have one project that we coded in C# before we decided to go to JScript for everything. One of my tasks is to re-create that project from scratch, manually. Just being able to save it in another language would be cool, but technically infeasible.
If you have 300+ projects in another language, I'm afraid your best bet is to leave them in that language. If you want to embrace Python, work every new project in Python from here forth, and assign resources to translate the past projects as available. If they have shared libraries, that would make it go even faster, but I don't think there's an easy way around this.
Thanks Kirk. I considered a "common" project and/or Script Extensions, but in the end I agree with the strategy you outline. For TC 12.0 I hear there is JavaScript support and that projects using JScript could be converted with a SmartBear utility. No such thing for JScript to Python (obviously they are too different).
I'm wondering if those that are using Python within the context of TestComplete are happy with it, especially if they've used other languages previously.
Hi,
FYI
The JScript to JavaScript 'translation' does not change the code at all: it only marks the code to be run by another interpreter. The differences between the two languages are so small that this works for most cases, and in the cases where there are differences, you are yourself responsible for changing the code.
/
Søren Harder,
QA/test-engineer, Zmags
kirk_bottomley absolutely correct, it's very painful to convert/migrate project from one language to another, It is a manual task and management expect ROI same as past. its better to start new project in python instead of migrate existing.
We had deadly painful movement. :( Finally dropped that idea.
