Repository: False Search Results via 'Find All Code Refs'
Posted: Thu Oct 17, 2013 4:52 pm
PROBLEM SUMMARY: Repository - Search Results: The 'Find Code References > Find All Code References' feature is resulting in 0 items found for numerous Repo items that are in fact confirmed to be in use. This problem was not observed until we upgraded to Ranorex 4.1.0. Yet, the Repository - Cleanup feature seems to much more accurately state what Repo Items are not in use and are therefore safe to delete.
DESIRED BEHAVIOR: Repository – The 'Find Code References > Find All Code References' function should be just as trustworthy as the Repository – Cleanup function in regard to judging if a given Repo item is in use.
EXAMPLE SCENARIO: In Ranorex 4.1.0, we've opened our Smoke Test. Within that Smoke Test, we've opened a given .rxlog file. One of the action lines (Action = Mouse - Click) is mapped to a given Repo item. We open that repository file in Ranorex, right-click it, and perform the above-stated 'Find Code References > Find All Code References' action on that Repo item. The result is that about half the time, the correct search result will occur stating what files this Repo item is referenced in. However, there are numerous instances where 0 results are found. This '0 results found' is a problem / fail of the 'Find All Code References' feature in cases where in fact the selected Repo item is in use (by an existing .rxlog or usercode.cs file). Numerous instances of this problem type have been found.
BUSINESS IMPACT: The customer may then be inclined to Delete the Repo Item if this problem is encountered. If this is done (like our organization did), the script will fail to compile (due to being mapped to no longer existing repo items), and the customer will have to create new repo items / map these new repo items to the failed scripts. This process can come at a great expense in regard to both productivity and function. This can result in the loss of numerous man-hours to correct the problem, loss in the ability to run the Ranorex automation that will no longer compile due to the missing Repo Item references, etc. We deleted about 20 - 30 good, in-use Repo Items due to this problem, and had to re-create them and update the affected scripts to map to them. This took hours. Also, this problem can lead to loss in confidence in how accurrate the 'Find All Code References' feature is.
SYSTEM INFO:
Ranorex Studio Version 4.1.0.25227
Internet Explorer 8 Version 8.0.7601.17514
Java Version 7 Update 25 (build 1.7.0_25-b17)
Flash Player 11.8.800.94
Windows 7 Ultimate N Service Pack 1 64-bit Operating System - Installed Memory: 4.00 GB - Processor - Intel(R) Core(TM @ 2.67GHz)
DESIRED BEHAVIOR: Repository – The 'Find Code References > Find All Code References' function should be just as trustworthy as the Repository – Cleanup function in regard to judging if a given Repo item is in use.
EXAMPLE SCENARIO: In Ranorex 4.1.0, we've opened our Smoke Test. Within that Smoke Test, we've opened a given .rxlog file. One of the action lines (Action = Mouse - Click) is mapped to a given Repo item. We open that repository file in Ranorex, right-click it, and perform the above-stated 'Find Code References > Find All Code References' action on that Repo item. The result is that about half the time, the correct search result will occur stating what files this Repo item is referenced in. However, there are numerous instances where 0 results are found. This '0 results found' is a problem / fail of the 'Find All Code References' feature in cases where in fact the selected Repo item is in use (by an existing .rxlog or usercode.cs file). Numerous instances of this problem type have been found.
BUSINESS IMPACT: The customer may then be inclined to Delete the Repo Item if this problem is encountered. If this is done (like our organization did), the script will fail to compile (due to being mapped to no longer existing repo items), and the customer will have to create new repo items / map these new repo items to the failed scripts. This process can come at a great expense in regard to both productivity and function. This can result in the loss of numerous man-hours to correct the problem, loss in the ability to run the Ranorex automation that will no longer compile due to the missing Repo Item references, etc. We deleted about 20 - 30 good, in-use Repo Items due to this problem, and had to re-create them and update the affected scripts to map to them. This took hours. Also, this problem can lead to loss in confidence in how accurrate the 'Find All Code References' feature is.
SYSTEM INFO:
Ranorex Studio Version 4.1.0.25227
Internet Explorer 8 Version 8.0.7601.17514
Java Version 7 Update 25 (build 1.7.0_25-b17)
Flash Player 11.8.800.94
Windows 7 Ultimate N Service Pack 1 64-bit Operating System - Installed Memory: 4.00 GB - Processor - Intel(R) Core(TM @ 2.67GHz)