Orphan Requirements in TFS - tfs

How can I make a query in TFS to say “Give me all the Project_A requirements that do not have any test cases linked to them”
I want to be able to easily look at what requirements have not been looked at by the test team and write/link test cases

You can use 'Work Items and Direct Links' type of query, e.g.

Related

TFS 2013 Queries through multiple work item hierarchies

RE: TFS/MTM: Plan>Contents>Create query-based suites...
I am trying to get all the test cases returned under each feature for targeted testing. But, the features aren't directly linked to the test cases. The features are linked directly to user stories which are directly linked to Test Cases.
So, How do I get a list of test cases by Feature when running query-based?
No, we cannot achieve that, multiple work item hierarchies (more than 2 hierarchies) is not supported for work item query.
We can only query 2 hierarchies (Parent/Child), just using the type of query Work items and direct links or Tree of work items to do that.
So, in your scenario you need to query the test cases by user stories, then filter the stories by Feature.

MTM Direct Links Query vs Query-based suit (direct-links)

Direct Links query can be created two ways in MTM
Plan->Contents->New Query-based suite->(query type)->Work Items and Direct Links
Track->Queries->New Direct-Link Query
First one creates a test suite in the end. Is there any other difference?
Your two techniques are doing different things and have different purposes.
Option 2 is simply doing a Work Item Query, the same way you can do in Team Explorer/Visual Studio and also Team Web Access.
Once you have viewed the information you can discard it or save it in "My Queries" or "Shared Queries". If you save it, you can view the results in Excel for example or perhaps share it with colleagues.
Option 1 is all about creating a Test Suite which is a grouping of Test Cases.
There are static suites which are essentially folders for grouping Test Cases.
There are requirements based suites - for example, add all the PBIs from Sprint 1 and then we can add Test Cases to ensure we have tested against their acceptance criteria.
Then there are query based suites which will add all the test cases which match your specified query. New test cases will be added if they match the query (eg. all high priority test cases)
Organizing Test Cases Using Test Suites(2012)
So, if you want a test plan then use option 1. If you want to simply run queries, use option 2 (or use team explorer/web access to do the same thing)

TFS 2013 - check in policy - require a specific work item type

Is it possible to create a check in policy that enforces developers to associate a specific work item type, like User Story, for example? We are using TFS 2013 here.
Thanks!
Vítor
If you install the power tools you get a work item query policy.
http://visualstudiogallery.msdn.microsoft.com/f017b10c-02b4-4d6d-9845-58a06545627f
I usually create a query that shows only Tasks that are assigned to #me and use that.

How to import legacy requirement IDs into TFS 2013?

I am trying to import some existing requirements into TFS 2013 (currently just maintained in a Word doc). However, I need to preserve the existing, pre-assigned requirement IDs (for tracking against existing test cases outside of TFS, etc.). I've come up with multiple ways of doing it:
Keep it as part of the requirement title
Add it to the description for the requirement
Add a tag with the legacy req id to the appropriate req in TFS
Add a new field for it to the requirement template (or simply use an existing unused field)
All of these seem pretty unclean to me except the "new field" option, but I'd rather avoid changing the work item template if I could.
Are there are other/better ways to do this? Has anybody done something similar before?
I usually add a field to most of my work items called External ID that I use for this purpose. It's also useful to link TFS Work Items to say a ticket ID in a Help Desk ticketing system.

TFS 2010: Queries based on the elements of other queries?

is it possible to create new queries in TFS 2010 based on the result of another query?
For example, one (parent) query selects all work items located under a certain work item (lets say work item with ID=5). And now I want to create other queries, that select all bugs, all tasks etc. from the results of the first query?
There, I only have to change the ID of the "parent" work item once and not in all subsequent queries.
Is this possible in TFS 2010 in combination with VST 2010?
Thanks
Konrad
There is a basic support for what you 're after in the GUI editor for WIQL: try with query of type "Tree of Work Items" - which creates a multi-level structure. There is minimal support to what you can handle in this context, for example it's not possible to pick work items with different criterias from level to level.
On the other hand you can implement a custom tool using the TFS-API. There you should be able to tailor to your needs exhaustively. I can support in such endeavor in case you 're interested.
What you want to do seems to be more of a report than a plain query. I think you should have a look at implementing custom reports.

Resources