Community
Participate
Working Groups
This issue was raised during the Sept 15 Hyades UI Meeting: The rationale behind the test navigator was not to show the filesystem; we already have a navigator for this. Instead we would like the test navigator to show a logical representation of the test artifacts in a meaningful way that is easy for the user to understand. Currently, the UI is inconsistent in this respect; some things show the filename while others show the logical name. We want to be consistent throughout the navigator, so it was proposed to adopt the logical view throughout the navigator. There were a few issues raised about this: 1. Logical names are not necessarily unique; so how to guarantee that the underlying filename would be unique. A proposed solution was to annotate the logical name with some unique ID that would be used to construct the filename. 2. There may be more than one test suite stored in a file, but there are problems representing this in the UI. A few other comments that were made: - Logical names have more flexibility than filenames, as there are no character restrictions, etc.
During usability studies for a product that uses the Test Navigator, users experienced difficulties navigating the Test Navigator and locating results. Logical representation of artifacts can help by better organizing different artifacts such as tests, test suites, test results, etc.
Created attachment 16065 [details] Two test assets with the same name.
I think that using logical name in the navigator is the best choice. IMHO the issues listed above do not really exist: 1. The filenames are entered in the first page of the new wizards and a check is done to avoid multiple files with the same name. 2. If a test suite file contains more than one test suite object, these test suite are displayed as children of the test suite file node. Each of those test suites is dsplayed using its name. The unique problem that can occur using the logical name is: A user can create two seperate asset files (test suites or whatever) with different name containing objects that have the same name. In such situation, the user can select one of those similar assets to show in the status bar the name of the container file (see attachment).
Propose to push this out of 3.2 and retarget to - for now, this feature will be raised to the RG and get review there for the proposed new target 3.3
Updating this description from the Dec 1, 2004 TPTP UI Meeting: This feature still consists of two realted items to improve the user experience: 1. Use of logical names 2. Logical organization of test artifacts (1) It was agreed that Bug 71745 did address the use of logical names in the Test Navigator, but it was determined that there was still a need to simplify the UI around the wizards (i.e., no longer prompt users for both a file name and a (logical) name, rather only prompt users for the (logical) name and under-the-covers create/map a file name; it is still necessary to show users the mapping to the file name in the wizard and potentially via a properties dialog for the test artifact). It was decided to keep 71745 closed and to clarify Bug 74962 to reflect point 2 as this work has a large impact on the wizards and is not containable for 3.2i2 (as part of bug 71745). (2) Design discussion is still required to define how to improve the organization of the Test Navigator and to consider whether multiple organizations (and an ability to switch between organizations) is helpful.
*** Bug 76948 has been marked as a duplicate of this bug. ***
Since Bug 76948 has been marked as a duplicate of this feature, should this feature be targeted for 4.0? The logical test navigator feature (Bug 76948) was marked as committed for 4.0 in the TPTP Features list. I would think this bugzilla should now reflect the 4.0 target. Either that or Bug 76948 should be kept open and this Bug marked as duplicate.
Wayne, Should we align the content of this TPTP feature with the design provided by UTUX ?
Fixed. The logical view of the test navigator has been released. Two new extension points have been added to allow customization of this view. - org.eclipse.hyades.test.ui.testNavigatorTypeProvider allows clients to specify a way to freely populate thier type container (the type should have been declared has a Test type using the extension point org.eclipse.hyades.ui.typeDescriptions) - org.eclipse.hyades.test.ui.testnavigatorTestAssetGroupProxy allows to customize the way that the test navigator gather the test assets of a same kind (the kind of the test asset is given by the extension of their files).
ACTION: Please verify/close this defect.
closing
