#10279 closed task (fixed)
TabContainer: automated tests
Reported by: | bill | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | 1.6 |
Component: | Dijit | Version: | 1.4.0b |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Write robot tests [plus some plain DOH tests] for TabContainer, including:
General/api tests:
- initial instantiation
- should have tab label for each pane
- adding panes (addChild())
- confirm tab label is added
- left/right scroll buttons and menu button appear on overflow
- new pane added to menu
- deleting panes (removeChild())
- confirm tab label is deleted
- confirm scroll buttons disappear when no longer needed
- check that removing a tab doesn't delete the widget, just detaches it
- deleted tab removed from menu
- selecting panes
- check that the tab label is scrolled into view
- changing the name of a tab
- confirm left/right/menu scroll buttons appear/disappear as needed
- menu is updated
- icon
- setting the icon initially
- changing iconClass of pane reflects it in the tab label and menu
- showTitle=false
- closable tabs
- check that tab label has close icon when specified
- layout related
- tab alignment (top/bottom/left/right)
- for nested=true, adding many tabs resizes the tab content smaller to make room for the labels
- doLayout=false mode should change size based on content
Robot tests:
- mouse:
- selecting a tab by clicking tab label
- closing a tab
- scrolling left/right
- selecting a tab from the menu (confirm that tab label correctly scrolls into view)
- keyboard:
- tabIndex: pressing tab key goes to selected tab label, then second tab key goes to tab content
- left/right arrow keys navigate to adjacent tab label, focusing it and scrolling tab label into view
- closing a tab via TabButton context menu
I'm sure there are more things I forgot.
There are a few tests already in ContentPaneLayout.html and ContentPane.html and nestedStack.html, but they don't test any keyboard/mouse interaction or anything related to the scrolling tab controller.
Change History (25)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
(In [20847]) In progress TabContainer? (non-robot) DOH tests, thanks to John Ryding (IBM, CCLA), thanks John! Refs #10279.
comment:3 Changed 11 years ago by
(In [20853]) Updated TabContainer? (non-robot) DOH tests, thanks to John Ryding (IBM, CCLA), thanks John! Refs #10279.
comment:4 Changed 11 years ago by
comment:6 Changed 11 years ago by
comment:7 Changed 11 years ago by
comment:8 Changed 11 years ago by
comment:9 Changed 11 years ago by
(In [20867]) More updates to TabContainer? (non-robot) DOH tests, from John Ryding (IBM, CCLA), thanks John! Refs #10279.
comment:10 Changed 11 years ago by
comment:12 Changed 11 years ago by
comment:13 Changed 11 years ago by
comment:14 Changed 11 years ago by
comment:15 Changed 11 years ago by
comment:16 Changed 11 years ago by
Milestone: | 1.5 → 1.6 |
---|
comment:17 Changed 11 years ago by
comment:18 Changed 11 years ago by
This is almost finished. The remaining tasks, AFAICT, are:
- layout related
- tab alignment (top/bottom/left/right)
- for nested=true, adding many tabs resizes the tab content smaller to make room for the labels
- doLayout=false mode should change size based on content
- mouse
- scroll left/right
comment:20 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:21 Changed 11 years ago by
comment:22 Changed 11 years ago by
comment:23 Changed 10 years ago by
(In [23880]) Remove some unnecessary focus() calls, sending focus to the place where it already theoretically is. On IE6 when this test fails for some reason (timing condition?), it tries to focus a hidden element which causes an exception which pops up a dialog and hangs the test run (although I guess that only happens if you have IE setup to popup dialog in that case). Refs #10279.
(In [20846]) In progress TabContainer? robot tests, thanks to John Riding (IBM, CCLA). Refs #10279.