Improve behavior of Integrity Test Control plugin with duplicate test resources #257
Description
When jumping into Integrity scripts by doubleclicking some fixture invocation or suite in the Integrity Test Control plug-in, the mechanism currently only uses the fully-qualified path of the fixture/suite to look up the .integrity script file containing the respective source code, and then a line number indication to jump to the correct line.
This mechanism can fail if a workspace contains duplicates of the same fully-qualified entities, but within different execution contexts, such that at runtime, only one of the entities is actually visible to the test runner, but at development time within Eclipse, both of them are visible to the Integrity Test Control plugin. The plugin will currently jump to the first match, regardless of whether that happens to be the correct one.
It would be preferable for the plugin to somehow "guess" which of the potential matches from the workspace is the most likely correct one. This is not trivial, because the Integrity scripts may be contained within JARs or be integrated into the runtime system via a different path than they are visible to the workspace (such as from a "build target" folder, while the workspace sees them from a "source" folder), hence even if the plugin would get access to the source path of the script that contained a particular entity in addition to the entitys' fully-qualified name, an intelligent "fuzzy matcher" would have to be developed in order to actually get good results and correct matches, as straight-forward exact matches will probably fail in a lot of cases.