Hi Guys,
The Finding Usages article says that:
TestComplete does not support searching for usages in script units associated with other units through adding the
module.exportsobject.!
So, the behavior you see is expected.
As an alternative, you can find occurrence via the Search/Replace dialog.
If you're using TestComplete 12.60, you should be able to right click on the routine and select "Find Usages". That will then return all script references and Keyword test references to that script routine.
That does not appear to work consistently. For instance, I have a function called GetRandomString(). It is called many times across various script functions. When I do find instances for that function, my search results show no results.
Is there something I need to do that I am missing? Thanks
I wonder if it might have to do with the implementation. How are you using that script in other locations? Are you using \\USEUNIT or are you using the native JavaScript "import"?
In the unit that the called function is present
module.exports.GetRandomString = GetRandomString;
in the calling unit(s)
var CommonUtilities = require("CommonUtilities");
This is what the Import dialog in TestComplete does. I THINK I saw somewhere that Useunit was being depricated.
Thanks.
Not deprecated, just that it's not necessary for JavaScript.
However, that MIGHT be what's going on. Because you're using the native JavaScript engine method for importing routines, the algorithm that does the "Find Usages" might not be finding it. That MIGHT be something that needs to be brought to the attention of the customer service staff.
As a test, what happens if you use the \\USEUNIT to include your library containing GetRandomString() and then try it. Does it work then?
