When using MS Test Manager 2013 there does not seem to be any way of adding/editing tags on a test case. I can however select tags as a column to be displayed in for test cases in MTM.
If I open the test case work item in the TFS web portal, I can add/edit tags on the test case there.
Am I missing something? Is there any way to add tags in MTM without having to flip over to web access every time.
Make sure you update your Test Manager / Visual Studio installation to the latest Visual Studio Update, that should enable the Tags field on your work items.
If I remember correctly, your TFS server also needs to have at least TFS 2013 update 2 installed, but as Microsoft only supports the latest released update, I'd recommend to update to TFS 2013 Update 4.
Related
I am not able to add associated automations in visual studio 2013 like the tutorials tell me to. (https://msdn.microsoft.com/en-us/library/dd380741.aspx)
My screen when I query for a testcase is slightly different and does not have a button for me to add associated automations. Any ideas?
Just check connecting to VSO, and I could reproduce your issue. So I assume you are using VSO, correct?
There is already a feedback submitted for this issue on Visual Studio page, refer to this link for details: https://connect.microsoft.com/VisualStudio/Feedback/Details/2137069
Similar case: Issue linking Ranorex CodedUI tests to MTM/VSO 2013 CI following recent VSO update
We currently have our Source Control settings set to enforce a Check-In Note called 'Reviewer' is set for every check-in in our projects.
However, for two of my developers, the Reviewer field is not showing up, and they can check in their changes without having to fill in the field!
I've cleared the Cache (as mentioned in many posts, this one in particular) on one of the developer's machines, but this did not correct the problem.
I've grabbed the "devenv /log" output from both developers and compared it to mine, but nothing jumps out at me there either - the versions of Team Foundation assemblies that both are loading into their IDE's are the same as mine, and any 'Power tools' that we load are also identical other than tools that we don't share at all.
We are using TFS 2013 Update 3, and Visual Studio 2012 Update 4, Visual Studio 2013 Update 4. The Developers on my team might typically switch between VS2012 and VS2013 at least once a week.
When you have a custom check-in policy, everyone will need to have that check-in policy installed on their development workstation.
I'm using VS2013 to development and maintain a couple of SP2013 projects. However, I think somehow I managed to corrupt one of the projects.
When I go to the "Package.package" designer, I see only (mapped SP) folders in there (it should also include the feature of the project). When I double-click, thus remove, one of these and try to re-add it, I get the following error msg
http://i.imgur.com/nC8RdOq.png
Same goes when I try to add the feature to the package
What's also strange is that if I go into the Feature designer, I cannot add any items. VS gives a similar type of err msg:
http://i.imgur.com/wqC5nAg.png
Few more details:
the projects were SP2010 projects and I successfully converted these to SP2013 some time ago.
using Visual Studio Premium 2013, Update 3, running as an administrator.
tried removing the feature and re-adding it; did not help.
tried running VS in safe mode, resetting the user settings via the command line devenv; did not help.
tried closing the designer, VS, rebooting; did not help.
i am able to add/remove items to the package/feature in other projects so I suspect it not to be a VS2013 bug
I just had the same Issue when adding items to feature or including features in package. I solved it by updating Visual Studio 2013 Developer Tools.
After updating to: Microsoft Office Developer Tools for Visual Studio 2013 - August 2015 update
We have recently upgraded to windows 7 and have noticed that there are compatibility issues with my previous version of MS visual Studio 2005.
From taking a look around the web I believe that this issue is due to SP1 for Windows 7. My organisation will not get rid of SP1 just for one or two developers so I need to figure out a work around.
This is the issue...
I have an old MS visual studio website that has a report located on the home. This report was created in MS VS 2005.
Other versions of Visual Studio in have are 2010 and 2012. I have tried to convert the 2005 report into 2010 and this does state that it has been converted but I still cant open or do anything with the report. My 2005 web site is too large to convert or move into 2010 and we can still maintain this 2005 site by opening this up in 2010. It just seems to be a problem with the 2005 report.
I'm running out of options to make a simple change to a report. Anyone else got any ideas? I have even tried to create this report in 2010 and then add this to my 2005 site but this doesn't work.
Regards
Betty.
You say a report and then say that it is a whole site? Why not run a second site in tandom? Make a whole new site and name it differently like
http:// (servername)/Reports2012
Then put reports there. You cannot open a converted report in a site that is for a prior version, you can view it in Microsoft Business Intelligence Studio, BIDS, which is an add on to Visual Studio. If you can upgrade but cannot view it there, there is something wrong with the language file potentially. I would then make a copy of it in the old 2005 BIDS, then take that copy and see if you can upgrade that and if it will work. If that STILL does not work you could make a test report in BIDS 2010(SQL 2012 works on VS 2010, yes weird but true) to assure you can create reports there. Many times people try to open SQL Server 2012 Reports on VS 2012 and it won't work. You need 2010 add on you can find it under All Programs>MS SQL Server 2012>SQL Server Data Tools(They made the naming very confusing as it opens up and display BIDS, but calls itself 'Data Tools' under the programs). Every other version of SSRS lines up with that year of SQL Server to that year of VS. Not 2012.
If the report upgrade still does not work, yet you can create a run a new report fine; I would suggest potentially opening up the file dircectly. Your projects in a Reports solution generally have a file '(something).rdl' that RDL is the actual file and is just XML markup of the language. This is a last resort as you are essentially trying to do manually what the upgrade is failing to do in the xml. You merely copy a working report, and then paste the parts of the old report into their correct sections. Ensure the XML is valid as well.
If you cannot manage that to work you will need to recreate the report from scratch.
I have TFS 2010 integrated with share-point 2010, inside the project portal i try to add a new task but there is no start date neither due date ?
is that normal ? how can i add these fields ?
It is normal I'm afraid, the web page view of a Work Item is usually identical to the view of the same item in Visual Studio. For some reason these fields are hidden.
You have 2 options. You can change the Work Item template on your Team Project so that these fields are not hidden, or you can use the Office integration features of Team Explorer.
To edit the template you'll need the TFS 2010 power tools.
To use Office integration you'll need Team Explorer installed, plus either Excel 2007+ or MS Project 2007+. Project automaticaly hooks in to the start and due date, with excel you can select which fields you want to view and sync with TFS