If you are like me and a fan of Shelving in TFS you are going to love TFS11.
Here are some new features for Shelving that have me excited about the next release.
Instead of a copy, unshelve is now a merge. You can take those changes and Merge them in with your current local changes. Also this means that on a Gated Check in the Shelveset is merged with the main base of code prior to the private build.
In the new Team Explorer you can select work items that are In progress. So that when you check in the changes the changeset is associated to the work item.
If you Shelve this work to do something else the Work item is stored with the Shelveset. When you Unshelve to work on it you will get the work item also.
Select a shelveset while you have work in progress. Notice the Switch command below. This allows you to take your In Progress work and swap it out with a Shelevest.
TFS11 beta power tools are now available for download.
In the power tool are:
Best Practices Analyzer
- Team Explorer Enhancements
- Team Foundation Power Tool Command Line (tfpt.exe)
- Test Attachment Cleaner
- Process Template Editor
- Windows Shell Extensions
Read more about what all these power tools give you and download TFS11 Beta Power Tool.
If you are interested in following
any of the MSDN Forum’s there is a gadget you can download that makes access to
your favourite threads quick and simple.
It is Methodology May at the TALMUG
Methodology. In the world of software development there are not many words that raise contention quite as quickly as this. But why is that? What are the differences between Agile, Iterative, and Rigorous software development methodologies? There has been buzz about Scrum, XP, Lean, Waterfall, Kanban, and RUP for years; how do they fit into this discussion? But most importantly, why should you care? What does the test team think of all this?
In Methodology May the TALMUG brings you a panel of ALM professionals to discuss and debate these very questions and maybe help you see what methodology could work best at your company.
Pizza and Pop will be available at 5:30pm - Come out and join in on the discussions.
Being held at 40 University, Suite 1301, Toronto meeting starts at 6pm.
Follow on twitter @TOALMUG
Click here to Sign Up
I had a customer that was looking for a way to see the history of a work item in an easier to compare format then the work item itself. I searched for such a tool, didn’t find one, so I wrote this.
I uploaded it to CodePlex in case anyone would like to use it or extend it. If you just want to try it out you can download the latest version from CodePlex.
The app is pretty simple. Simply run GetHistory.exe select the server and projects you want to query and hit connect.
On the main form below, the Project drop down will be populated with the list of projects you selected from the connection screen.
Enter a Work Item ID from that project and hit enter or click Get History.
The grid will fill with each revision of the work item. If the data in a field is different than the previous revision it will be displayed in red.
Go to the Fields to Ignore tab to select work item fields you don’t care to see. Some are obviously pointless and should be turned off by default. (ie: Rev, ID, Area ID, Iteration ID, History, Work Item Type)
Connect to TFS: Use this button to switch to another server or collection or add or remove a project from the drop down.
Clear: Clears the form of the last retrieved work item data.
Export to Excel: Do I really need to tell you what this does?
I hope someone out there finds it useful.
Dave Lloyd has updated GetHistory a power tool for displaying work item history. Now you can export the work item history to excel. If your company has a audit process that has to be followed this tool may help you report on changes to requirements, test cases, bugs in just a few steps.
Click Get History to get the newest version. Keep your eye out on this tool you never know what features Dave may add!
Here is what you will see and hear from ObjectSharp's Microsoft MVPs at this event:
Metro (Win 8 + Mobile)
The Metro interface has the potential to change how a lot of people use computers. You've already seen a little of it in the Windows Phone. More if you have downloaded the Windows 8 consumer preview. In this session, we will demonstrate how the power exposed by Metro (through live tiles, push notifications, immersive user experiences, etc.) can be harnessed to provide a usable and intuitive application.
VS 11/.NET 4.5
We're still a few months away from its release, but the beta version of Visual Studio 11 and .NET 4.5 is available and with a Go-Live license too. With Visual Studio, reduction and simplification are the keywords. For .NET, assistance with parallelism this session is the big topic. Between these and other topics, the tools that will make your development life easier are covered.
TFS 2012/Test Manager 2012
The word in the TFS/Test manager world for 2012 is "Agile". Lightweight requirements gathering through PowerPoint Storyboarding. Additional reporting, including a task board, in TFS and exploratory/agile testing through Test Manager. Lots of new features to delve into and they will be in this session.
Check out all about it here.
Tomorrow Barry Gervin and I will be interviewed on AlignIT with Ruth Morton and Jonathan Rozenblit.
We will be discussing the Pros and Cons of upgrading to the next version of VS and TFS. Affectionately known as vNext or Dev11.
Feb 29th MS announced the release of Windows 8 Customer Preview and Visual Studio 11 Beta.
Looking forward to the discussions. Watch for it on AlignIT.
MTM needs a feature that allows testers to describe what an individual test case iteration is testing.
Right now I add a parameter to the last steps expected results "@Notes" and for each iteration of a test case I add to the Notes what I am testing in each iteration. Example would be testing a address site. My test case will go through all the address fields so any testing I would need can be done with parameters and iterations even boundary. But I need a easy way to identify what is being tested by an iteration.
Vote for this feature “Identifier that describes what each test case iteration is testing”
Check out instructions on how to create reports for your TFS2010 Test Results. There is also an example that you can follow.