Hi Herbert.

Thanks for reporting the issue.

You are indeed right. The plug-in started more as a proof of concept, and I started using it more with testlink and selenium. Then users wanted features, and we have the plug-in the way it is now.

Now I am trying to push as many bugfixes as possible, before starting 2.0

The 2.0 won't have the option to open the TAP file at all. It will be like when you use JUnit or TestNG. If you want to look at the contents of the raw test results, you will have to browse the workspace or archived files in a build.

I will mark this issue as won't fix, but feel free to comment here if you have any suggestion or different idea.

I like having that option to view the file, but as you said, old builds may have broken or invalid links. And unless you archived the TAP files, your older builds won't have anything associated, as the workspace may have been changed in further builds.

Hope that helps
Bruno

It is very useful feature indeed. It is wrong to put it away, unless you allow other easy way to look at the surroundings / output / stacktrace of the failed test (that's what raw tap file was really useful).