Forum Discussion
Thank you for the valuable inputs.
I understood the routine list purpose. Then it would be good if we have something like tree structure of a Unit with its contents (like each functions) under Project Explorer as it would display in Eclipse IDE. Any solutions would be so helpful for us.
And yes, with JavaScript Class, I am able to export/import to another unit and can access its methods. Its working as expected.
Also these are core units files of the Project and we do not want to use as ScriptExtensions, since these are expected to change very often.
As you said Code completion is good with ScriptExtensions.
So as HKosova, I will put this in Features section. Hope Smartbear admins can come up with smart solution.
Many Thanks,
Saravana
If they are core units to a project, I wouldn't expect them to change that frequently... test cases that consume those units, yes... but the actual core units of a test framework should be relatively static. But then, that's just my way of designing things.. YMMV.
I keep my extension code in my TFS repository along with everything else so I can track it, develop it, version it, etc. The only difference between that code and my regular script code is that I need to "package" it as a tcx... but that takes all of 2 minutes... and if I am only changing my core code a few times a quarter, then adding 2 minutes to my work isn't that big of a deal. :)
Related Content
Recent Discussions
- 5 hours agoSvetaG