Description

If you are unfamiliar with the File Tab Channel, check out my post about it at

New Window Management Features for Visual Studio 2005.

Nightly Scenarios

1. Verify opening 11 files displays the correct number of visible tabs in the File Tab Channel
2. Verify a tool window can appear in the File Tab Channel (after Tab-Documenting it) and it enters from the left
3. Verify the File Tab Channel drop down menu now contains 12 items, including the tool window
4. Verify a file tab that has fallen off the File Tab Channel reappears in the File Tab Channel after selecting it in the drop down menu
5. Verify the 1st file listed in the File Tab Channel no longer appears in the File Tab Channel after pressing close

Note: If you would like to seed feedback, but the comments are closed, please feel free to contact me via the contact form.

View original comments.

Description

If you are unfamiliar with Tool Window Docking or Dock Targets, check out my post about it at New Window Management Features for Visual Studio 2005.

Nightly Scenarios

1. Verify all 5 IDE-Center and all 4 IDE-Side Docking Targets appear when dragging a tool window around the empty center of the IDE
2. Verify all 4 IDE-Side and 5 Output Window-Center Docking Targets appear when dragging a tool window over the Output Window in a docked state
3. Verify all 4 IDE-Side and 5 Property Browser-Center Docking Targets appear when dragging a tool window over the Property Browser in dockable, but not docked state

Note: If you would like to seed feedback, but the comments are closed, please feel free to contact me via the contact form.

A couple of months ago, I posted an entry called What is a Nighlty Test Case? I mentioned how I’ve been tasked with coming up with a way to share our team’s nightlies with the community for review. I’ve been working on this off and on this week, and I now have several nightlies ready to be posted.

In all fairness, especially since this is something we haven’t done before (to the best of my knowledge), I’m going to post three nightlies that I originally wrote the test spec, implemented the library work, and wrote the test case code for. Even though I own the Editor now, it just didn’t seem right to me to post someone else’s work to “test the waters.” Anyways, I have thick skin, so let me know what feedback you have.  Seriously, we want to hear your feedback.

Once I get a good feel for how to post the nightlies (as articles? As individual posts or combined posts? Etc.), we’ll start posting other feature areas for review on the team blogs. I??m just using my blog right now as the testing-grounds, but if I wrote it, it’s going to show up here, regardless.

If I could, I would disable the 30-day limit for posting comments. I’m hoping that if people have comments after the 30-day limit, they’ll use the blog contact form. I’ll mention this at the bottom of every Nightly post as a reminder that people can still send feedback. Hopefully one day we’ll be able to disable this on a per post / blog basis.