by Tarun Arora
on Geeks with Blogs
See other posts from Geeks with Blogs
or by Tarun Arora
Published on Sun, 21 Oct 2012 11:01:00 GMT Indexed on 2012/10/22 11:02 UTC
Read the original article Hit count: 167
Just pushed out the 2nd release of the TFS Demo setup on CodePlex, below a quick look at some of the new features/improvements in the tool… Details of the existing features can be found here.
Feature 1 – Set up Work Items Queries as Team Favorites
The task board looks cooler when the team favourite work item queries show up on the task board. The demo setup console application now has the ability to set up the work item queries as team favorites for you. If you want to see how you can add Team Favorites programmatically, refer to this blogpost here.
Image 1 – Task board without Team Favorites
Let’s see how the TFS Demo Setup application sets-up team favorites as part of the run…
Open up the DemoDictionary.xml and you should be able to see the new node <TeamFavorites> this accepts multiple <TeamFavorite>. You simply need to specify the <Type> as Query and in the <Name> specify the name of the work item query that you would like added as a favorite.
Image 2 – Highlighting the TeamFavorites block in DemoDictionary.xml
So, when the demo set up application is run with the above config, work item queries “Blocked Tasks” and “Open Impediments” are added as team favorites. They then show up on the task board, as highlighted in the screen shot below.
Image 3 – Team Favorites setup during the TFS demo setup app execution
Feature 2 – Choose what you want to setup and exclude the rest
I had a great feature request come in requesting the ability to exclude parts of the setup at the sole discretion of the executioner. To accommodate this, I have added an attribute with each block, the attribute “Run” accepts “true” or “false”. If you set the flag to true then at the time of execution that block would be considered for setup and if you set the flag to false, the block will be ignored during the setup.
So, lets look at an example below…
The attribute "Run” is set to true for TeamSettings, Team Favorites, TeamMembers and WorkItems. So, all of these would be setup as part of the demo setup application execution.
Image 4 – New Attribute Run added to all blocks in DemoDictionary.xml
If I did not want to recreate the team and did not want to add new work items but only wanted to add favorites and team members to the existing team “AgileChamps1” then I could simple run the application with below DemoDictionary.xml. Note – TeamSettings Run=”false” and WorkItems Run=”false”.
Image 5 – TeamFavorites and TeamMembers set as true and others set to false
Feature 3 – Usability Improvement
If you try and assign a work item to a team member that does not exist then the application throws a nasty exception. This behaviour has now been changed, upon adding such a work item, the work items will be created and not assigned to any user. The work item id will be printed to the console making it simple for you to assign the work item manually.
As you can see in the screen shot below, I am trying to assign the work item to a user “Tarun” and a user “v2” both are *not valid users in my team project collection* so the tool creates the work items and provides me the work item id and lets me know that since the user is invalid the work item could not be assigned to the user. Better user experience ae
Image 6 – Behaviour if work item assigned to users are in valid users in team project
That’s about it for the current release. I have some new features planned for the next release. Mean while if you have any ideas/comments please feel free to leave a comment. Stay tuned for more… Enjoy!
© Geeks with Blogs or respective owner