Community
Participate
Working Groups
The equivalence class column does not have a label. Providing a label may help users better understand what the type of information the column is reserved for.
Hi Wayne, This seems like a fair problem, but the proposed fix seems dubious to me. I agree that equivalence classes are confusing to some users, but adding a label to the equivalence class column (at least in the table itself) seems very confusing as well. All of the other labels (in the first row of the table) are variable names that can be included in test script code. Also, the only available place for an equivalence class column label is in cell 0,0 of the table (which could just as eaily be considered a label for the first row, and is counter-intuitive to the current spreadsheet nature of the UI.) Maybe we can concentrate on coming up with a UX that allows products to hide the notion of equivalence classes entirely, and assume that if a product chooses to expose them, their users will be able to understand this type of UI. Feel free to reopen this if you disagree, but for now I will close this as "wontfix".
Hi Joe, I tend to agree with your assessment. The larger issue deals more directly with confusion over equivalence classes for certain user types. This issue is already covered in Bug 73178.
Talked with Joe and Wayne. There's been a little confusion about what the label for equivalence class column refers to. This defect meant to address the appearance of the first column in datapool. Cells in this column look the same as regular table cells for data entry but are actually row labels(except cell (0,0)) that are not editable. So cells in first column are really row headers and should has the same look and feel as the column header. This defect should be reopened to address this problem.
Per Bianca's clarification, I am reopening thsi defect.
SWT Table currently does not provide support for Row Headers. Submitted request for SWT: https://bugs.eclipse.org/bugs/show_bug.cgi?id=79727. Before SWT support becomes available, I experimented with a workaround to simulate the look and feel as column headers. However, the workaround doesn't work as well with equivalence class names in the label. So I am marking this one as a dup to equivalence class enhancement 73178 so that the enhancements can come together. *** This bug has been marked as a duplicate of 73178 ***
The workaround to mimick the look and feel of row headers with buttons does not look as well as desired and also may introduce performance issues. Equivalence class enhancement is implemented to present each equivalence class in a separate data table. The first column of the datapool table now (from 3.3.i1) only contains index of rows. Row headers will make them look better but will not provide much usability. This should be an enhancement when SWT table row header support is available. (see bugzilla# 79727). If row headers in SWT table will not be provided, this enhancement may be closed as won't fix.
[sizing = 2 days]
This enhancement depends on a SWT enhancement: https://bugs.eclipse.org/bugs/show_bug.cgi?id=79727. According to Steve Northover: "Since there is no native support on Windows at least, odds are very low that we can do much about this. Veronika to add this to the collection of table bugzilla feature requests." Thus changing version to future.
Changing the priority to P3 since TPTP only uses P1 - P3 priorities.
Correcting version for this enhancement (defaulting to the current release). See http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html for more information.
Correction: Future is a valid version for this enhancement based on http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html. As such, the implicit assumption is that is enhancement is of a lower priority. If incorrect, the originator should correct the version.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
