Bugzilla – Bug 418916
QA team needs information about different "subelements" for each control
Last modified: 2009-07-14 19:51:08 UTC
Andrés made a good observation that the QA team is not currently tracking/testing different "subelements" or "styles" of the WinForms controls. An example he used was for the ComboBox control, which has three different drop down styles (Simple, DropDown, and DropDownList) that each have different provider implementations and therefore each one should be tested. Similarly the TextBox control can be "normal" or "multiline"; each one has a different provider implementation. We discussed this problem on the mailing list and IRC and I think the consensus was to have the developers inform the QA team when a certain control had different subelements or styles that required a different implementation and would therefore need to be tested separately from the default control. The problem is we have no system or guidelines in place to make sure this information is passed from developers to QA.
Mass change of QA contact. Sorry for bugspam. Update your watch-lists.
Is this still the case Brian, or can we close this?
We don't have any centralized information for this, QA has just been doing their best as we've been creating the sample applications and reading about the controls on MSDN. This is not what I had in mind, but it seems to be working okay.
Brian -- that's what I was trying to solve with the Bridge specification. If there's anything I can do to assist to make things clearer, you've got to let me know.
Unfortunately, I agree with Brad that this is difficult to achieve. We can just *try* to remind developers when they see potential controls that require special tests depending on their properties. For instance, I just realised that you guys should create a separate test (specially for the Atk.Text interface) for the widget TextBox when it's not acting as its default behaviour due to the property PasswordChar being modified. We'll leave this bug open for this purpose. Anyone is welcome to warn here more potential controversial widgets. (Reassigning bug to the mailing list and CCing all developers.)
This isn't tied to a particular milestone.
Did I do that again? Sigh.