I have asked this before a while back but could you please give some consideration to replacing the ancient JScript engine in TestComplete?It's quite annoying when I write something for a modern browser or node.js and have to translate it to clunky 20th Century JS syntax to do the equivalent in TestComplete. I know I can shim stuff like Array.prototype.map but only in the same unit as the script I'm running, which isn't very practical - I want access to the global Array.prototype or have the new stuff built-in.Any chance this can be done?Any interest from anyone else?

Hi, Your vote was added! Thanks.

JSON is part of it, but it's really access to everything available in modern javascript. Looking at http://en.wikipedia.org/wiki/JScript, I believe that TestComplete is using a version earlier than 5.8 (JSON was introduced in version 5.8). The version of JScript we'd really like to use is 9.0, which was introduced back in March of 2011 with IE9, and includes things like Array extras, array comprehensions, and expression closures. See http://en.wikipedia.org/wiki/ECMAScript#Version_correspondence for javascript versions - upgrading from the old version of JScript to version 9.0 would gain us everything introduced in javascript versions 1.6 through 1.8.

I vote for this too. It would be nice to use the modern features of ECMAScript in our test code.As for the complaint about not being able to use prototype functions across Script Units, we have come up with an ugly hack to get around that limitation. Basically, at the top of every script unit, we run the equivalent of this: for(var i in SystemUtilities.Array.prototype) { if(Array.prototype == undefined) Array.prototype = SystemUtilities.Array.prototype; }SystemUtilities is the name of the Scirpt Unit that the prototype functions are written in. We don't actually put these lines in every file, but eval the output of a function which is a string to this effect.

Hi Guys, Thanks for the description! I have registered your request as a suggestion in our DB. All your voices are voted. Thanks! We will think about implementing support for JScript 9.0 in TestComplete.

Modern javascript please? | SmartBear Community

47 Replies

TanyaYatskovska
SmartBear Alumni (Retired)
11 years ago

Hi,

Your vote was added!

Thanks.
mrpalmtree19
Occasional Contributor
12 years ago
JSON is part of it, but it's really access to everything available in modern javascript. Looking at http://en.wikipedia.org/wiki/JScript, I believe that TestComplete is using a version earlier than 5.8 (JSON was introduced in version 5.8). The version of JScript we'd really like to use is 9.0, which was introduced back in March of 2011 with IE9, and includes things like Array extras, array comprehensions, and expression closures. See http://en.wikipedia.org/wiki/ECMAScript#Version_correspondence for javascript versions - upgrading from the old version of JScript to version 9.0 would gain us everything introduced in javascript versions 1.6 through 1.8.
john_meuser
12 years ago
I vote for this too. It would be nice to use the modern features of ECMAScript in our test code.

As for the complaint about not being able to use prototype functions across Script Units, we have come up with an ugly hack to get around that limitation. Basically, at the top of every script unit, we run the equivalent of this:

    for(var i in SystemUtilities.Array.prototype)

    {

        if(Array.prototype == undefined)

            Array.prototype = SystemUtilities.Array.prototype;

    }

SystemUtilities is the name of the Scirpt Unit that the prototype functions are written in. We don't actually put these lines in every file, but eval the output of a function which is a string to this effect.
TanyaYatskovska
SmartBear Alumni (Retired)
12 years ago

Hi Guys,

Thanks for the description!

I have registered your request as a suggestion in our DB. All your voices are voted. Thanks!

We will think about implementing support for JScript 9.0 in TestComplete.
googleid_102416
Contributor
12 years ago
While we are waiting for SmartBear:

1. http://pastie.org/6288077 - save this code to ECMA.sj file and add to you project

2. At the beginning of each your unit type:

//USEUNIT ECMA

eval(ECMA.init());

3. Now you can call javascript functions you got used to:

[1,2,3].forEach(function(e, i, a) {

ShowMessage(e);

});
Anonymous
12 years ago
All

thanks for your votes. I hear the sentiment. I think the earliest we can consider this for, given all the other projects we are pushing forward to keep TestComplete the best tool that it is, is end of the year. At this point, I'd say "this is not infeasible" :)
matt_rasband
New Contributor
11 years ago
Bump.

The original post on this was almost 1.5 years ago, are there any status updates on the subject?

Thanks!
TanyaYatskovska
SmartBear Alumni (Retired)
10 years ago

Hi Aleksander,

Counted.

As for your question, actually, we are working on the on-line suggestions so that all of you could submit your suggestions and vote for others. Give us some time for this :)
- Jesse1
  Regular Visitor
  9 years ago
  Hi,
  
  I'm currently using TestComplete 11 wich uses jscript 5.8, this is way to old. (ECMAScript 3)
  There are so much modern functions missing so ECMAScript >= 5 support would be great!
  Is there any news on introducing a new javascript engine?
  
  Jesse
spatel_1
Occasional Contributor
12 years ago
I second this. I also third it for the other guy who works with TestComplete on my project.
mrpalmtree19
Occasional Contributor
12 years ago
Agreed, modern javascript would be a huge help.