Community
Participate
Working Groups
After installing Jubula I get a couple of Infos in the Problem View. "Import, open or create a new Project." "You have to connect to the AUT Agent." Why do I want these when I'm not actually using Jubula? Why is it necessary to search Bugzilla to discover that "AUT Agent" is a Jubula facility.? Surely "Jubula" should be mentioned in the "Type" description?
I agree that the information isn't very useful when you're not using Jubula at the time. I haven't been able to find out whether problems view entries are supposed to be limited to the perspective / context for which they are valid - do you happen to know whether this is a UI guideline? If it's usually the case that problems view items are universal, then it would be worth adding Jubula as the type.
I've not seen perspective-filters problem markers, but I don't use Mylyn. The intent is that markers are clearly annotated so that users filters can be applied; so regardless of other changes they should be annotated as Jubula markers. Infos that are useful for developers during development should be removed prior to release.
I had a look at the current setup in the problems view, and the entries do have the marker "Functional Test Problem" as a type designation. They are not remnants from development, but are there to give pointers about the first steps when beginning using Jubula. My tendency would be to either: - talk about removing these two pieces of information completely (with the existence of the cheat sheets, hopefully people can find out themselves what the first steps are) - leave them as they are, on the basis that "Functional Test Problem" can meaningfully be traced back to Jubula. - Switch the text "Functional Test Problem" to "Jubula" (this would involve making sure that we can change it to "GUIdancer" for GUIdancer users - the idea of "Functional Test" is that it is relevant to both tools). What are your thoughts?
"Functional Test Problem" is a completely useless term. This all started because I assumed it was a new e4 report about some startup inconsistency. Infos are a very poor way to guide users. THey lack focus and are niot necessarily visible. Just imagine if every Eclipse facility populated the Problem, view with every FAQ every written. - a welcome page entry is suitable for completely new users. - a New Project..., or New... or Configure... entry are suitable for existing users. My first choice is to remove them. With a clear Jubula as a second best.
We've discussed that we're going to remove the two entries. The "First Steps" Cheat Sheets cover the necessary steps to get started, so these entries are no longer necessary.
Thanks.
Created attachment 224303 [details] Fix the bug by deleting the two useless markers shown in the problems view The two useless messages * "Import, open or create a new Project." and * "You have to connect to the AUT Agent." in the problem view are deleted including all associated code necessary to show these messages. This means the check for the connection and the two methods for showing the markers.
I checked the provided patch and you still need to address the following issues: - these problem types have not been removed: - ProblemType.REASON_CONNECTED_TO_NO_SERVER - ProblemType.REASON_NO_PROJECT - and the code for the corresponding quickfixes has also not been removed @Raimar: Could you please provide a patch which also addresses these necessary modifications and mark the current patch as obsolete?
Created attachment 224354 [details] Fix the bug by deleting the problems view markers including resolutions In addition to comment 7: Also the resolutions offered by the problem markers are deleted: - ProblemType.REASON_CONNECTED_TO_NO_SERVER - ProblemType.REASON_NO_PROJECT - and the code for the corresponding quickfixes
Patch reviewed and applied with changeset http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=c918122a18889d41e096698caf63c175ab410156
Fix tested using current GD and Eclipse SDK 4.2.1 with Jubula feature from Jubula development update site.
