I eagerly await a release of TestLeft that can be installed inside Eclipse. My developers use Eclipse/Spring Tool Suite and would like to start getting into test writing and investigating how TestComplete sees objects on the screen. Is there any estimate for when this might be available?
I would like to ask to bring the Point-and-Fix Object Browser functionality available in TestComplete's Object Spy to TestLeft. This functionality is extremely useful when investigating and capturing properties of dynamic objects like context menus, submenus, etc.
Hello. We would like the option to use the TestLeft UI Spy to browse a object that no longer exists.
This is relevant for us because we have custom context menus so we cannot use the suggested approach:
In TestComplete we can use Point and Fix and then browse inside the property to find what we need although the context menu would go away in the meantime. We could also find the return type of all the avaliable properties.
In TestLeft UI Spy, we can use Point and Fix to find the context menu, but we cannot browse inside the avaliable properies, and we cannot see the return type of some of them either(which are only avaliable through the IObject interface).
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.
I would like to suggest developement of automated screenshots on Testleft. It makes the test reports more professional, easy to debug and it adds value to the application under test.
Leandro de Araújo Souza