FREE Subscription to Dr. Dobb’s Digest: Same Great Content, New Digital Edition
Site Archive (Complete)
Testing & Debugging Blog: You Are Not Done Yet: Menus And Command Bars
Testing and Debugging
BREAKPOINTS

Test, Debug, Release, Rinse, Repeat ...

by Kevin Carlson
THE BOOK OF TESTING

Thoughts From a Braidy Tester

by Michael Hunter
October 19, 2006

You Are Not Done Yet: Menus And Command Bars

You are not done testing yet unless...you have put your menus and command bars through their paces. There used to be a distinct difference between menus and command bars: menus could have submenus and were always text (perhaps with an optional icon) while command bars were never nested and were only graphics. Nowadays, however, menus and toolbars are more-or-less the same animal and can be mixed-and-matched, so that the only real difference is that command bars are typically always visible whereas menus are transient.

  • Verify all commands work from menus and from command bars
  • Verify each keyboard shortcut works correctly
  • Verify built-in commands work correctly from a custom menu
  • Verify built-in commands work correctly from a custom command bar
  • Verify custom commands work correctly from a custom menu
  • Verify custom commands work correctly from a custom command bar
  • Verify custom commands work correctly from a built-in menu
  • Verify custom commands work correctly from a built-in command bar
  • Verify custom menus and command bars persist correctly
  • Verify customizations to built-in menus and command bars persist correctly
  • Verify commands hide/disable and show/enable as and only when appropriate
  • Verify command captions are correct and consistent with similar terms used elsewhere
  • Verify menu and command bar item context menus work correctly (although menus on menus is going a bit too far I think)
  • Verify status bar text is correct
  • Verify status bar text is not truncated

Posted by The Braidy Tester at 07:30 AM  Permalink




 
INFO-LINK