ContributionsMost RecentMost LikesSolutionsSwitch between different Script Extension Versions It would be great to have a way, via API and TestComplete menu, to decide which ScriptExtension version of a specific ScriptExtensions or a set of ScriptExtensions should be loaded when TestComplete is in design mode. In our case we do a have a set of keywords based on ScriptExtensions (JScript) and a set of keywords are supporting us to test the SUT. This would give our tester the advantage to switch between different versions of some keywords. Reload ScriptExtensions via API call It would be great to have way to reload script extensions via API call. Like developer would do via key combination ALT + F + E and pressing reload button at ScriptExtensions menu. Convert/Develop custom keywords / runtime objects with TestLeft/C# and VisualStudio for TestComlete Hi, we made a lot of script extensions for TestComplete (Custom Keywords and Runtime Objects). I would like to convert our custom keywords from JScript to C#. It would be great to have the keywords as deployable dlls, and shown up as keyword on TestComplete, which we can drag'n'drop via TestComplete UI to arrange keyword test scripts. For this it would be necessary to have a regarding Extension folder below of TestComplete which will accept the dlls in the same way as it do for normal ScriptExtensions as it is for now. TestComplete the specific folder like "..TestComplete/Bin/Extensions/Extensions/ScriptExtensions" as before etc. maybe some folder like "..TestComplete/Bin/Extensions/TestLeft/OurDllFolder". After deploy our users would open TestComplete and work as before. From my developer perspective, i would have the benefit of TestLeft but would also ensure that our users could work in the same way. It would be easier to debug our converted scriptextensions byTestLeft and use these converted script extensions for normal use by TestComplete We also had the benefit to use MSTest for the keyword dlls to test the code by TestLeft and VisualStudio. Regards, Norman Mark a Custom Keyword via API call or Description.xml as deprecated. It would be great to mark a keyword via description.xml to be deprecated. It would be also great to set this deprecated status for a keyword also via API call. The call would include the name of the keyword. The deprecated keyword should have a different color or visual effect.