Have Group Tester and Provider
Group PROVIDER only edit Bug and not access to Test Case related.
Group TESTER Only CReate and Edit BUG and Test Plan and TEst Case.
how in TFS 2012 to remove access to a PROVIDER group of test cases item?
Thank You
First lets state up front, so as to get it out of the way, that this is ridiculously dysfunctional behaviour. If you don't trust people don't give them permission at all.
That out of the way you can kind of hack this by customising the process template. If you edit the Bug to restrict the permission that can move from state "" to "New" then anyone else will get an error. This works for any work item type.
For Test Suit and Plan you need then"Create Test Plan" permission that isbin "settings|permissions" on the web access.
In TFS 2013.3 Test Suit and Test Plan are now work items so ita a little different.
Related
I'm asking this question on behalf of a colleague (which means I may have the terminology incorrect).
When a colleague adds a Test Case to a card, a requirement test suite is created in the wrong test plan.
We don't want a test suite to be created, we just want the test cases to be on the card itself.
How can we change this behaviour in TFS?
I did not see any settings for the test plan creation. The test plan creation works with next steps (tested on vsts):
System tries to find any plan with requirement. If there is no any plan then next.
System tries to find any plan with the iteration path from requirement. If plan exists system will import requirement to that plan. If there is no any plan then next.
System creates plan with iteration path from requirement and with requirement.
So you may use a workaround:
Create iterations for all test plans that you plan to use.
Assign needed iteration for selected test plan.
Assign needed iteration for requirements that will be used for testing.
There is no option to disable this behavior. But you can create a test plan and then configure the VSTS/TFS to place all the test case there:
Click the "Configure team settings" button:
Navigate to "Tests" panel and then choose "Select a test plan".
Using the power tool I was able to add a new custom field but I want that it take automatically a specific value if present.
Each test case has a "user story" associated but to associate it we have to go in "Tested User Story Section" so I'd like that in the main page appear automatically the ID of the user story.
Sorry for the confusion maybe with the image will be more understandable:
Someone can advice me of what to introduce in the Visual Studio Power Tool please? because I'm finding different example but none explain how to auto-populate with another dynamic item.
If you are asking me why it's because we want to have the "User Story ID" present in the main page so we know directly at which user story the test case is associated:
There is no way to get the User Story ID as a field. Since a single Test Case can test multiple User Stories this makes little sense anyway.
Have you tried adding Requirement based Suits to Test Professional so that you can see all of the Test Cases under a Story? From a testing perspective it makes lots of sense to look from the Story down to Tests rather than Test up to Stories.
Although my screenshots are from the Web App the features at the same in MTM. You can add a Requirement Based Test Suite that relates back to the User Story.
As #MrHinsh mentioned, there is no direct way to get the User Story ID from a field.
From TFS query, it's easy to get the linked User Story, you can select the Work Item and Direct Links in work item query, check the screenshot below:
I've allowed my Stakeholders to create Work Items but I would like to restrict them to only be able to create bugs and NOTHING else. Currently they can create ANY Work Item type including Epics... I'm thinking there has to be a way to stop this but I can't seem to find it.
There is no setting for this. And there is already a similar feature request submitted on VSTS User Voice: Hide Work Item Types (WITs) based on permission/security group.
I have a few users who are not able to see the Details of test cases.
They can see the test plans. The test plan is Active.
They do not have permission to create test cases but they should be able to see them and run them. Some of the test cases in the test plan have a state of Ready. Some have a state of design.
The users have access to see and run tests but their display looks like this:
If they try to run the test case they get the message "You cannot run the selected tests. The test case no longer exists. " which is clearly wrong because I and other users can see the test.
The users in question have visibility to the area and iterations.
I'm stumped and I'm sure it's something simple. Why is all of the column data blank?
This can be an issue with area-path permissions. Even though I see that you have mentioned "The users in question have visibility to the area and iterations", I'd like you to try this simple task:
Ask the user who is not able to see the tests in Test hub to head over to the Work hub and write a simple work item query to see if she can access those test case work items in Work hub. You can find out the test case work item IDs from someone who is able to see the test case work items in this test plan. Or you can write a generic query for all test case work items and see of the test case work items that have gone missing in Test hub are showing up in Work hub.
If you are not able to access the test case work items in Work hub, then its an area path permissions issue. If not, I'll be glad to ask someone on my team to look into this. Please reach out to us at devops_tools#microsoft.com
Thanks,
Manoj
It was indeed a problem with the areas. But not in the project in question.
The test cases in question pulled in from a different project. Everything looked normal if you opened the test case. No errors about invalid area paths. And all the permissions on the project looks ok. The user had all appropriate permissions. If just wasn't until I added up all the pieces I saw the disconnect.,
I am unsure whether this is the correct stackexchange site to ask this question, however it is about software tools commonly used by programmers (sort of).
I am collection administrator of 100s of .net projects that I have recently migrated from an on-premise TFS to VSO. I am receiving requests from developers to grant them permission to create/manage test plans.
Now, these developers are members of the "Developer" and "Contributor" groups and as such have the following permissions:
But even so, they are unable to create test plans (using Microsoft Test Manager 2013). I have searched throughout the VSO control panel and I cannot find out why my developers don't have permission to create/manage test plans.
Even the documention provided by Microsoft seems to fall short when it comes to managing permissions in VSO.
Any help is much appreciated. How do I grant my developers these permissions?
Edit: I should add that I myself am able to create test plans. I have compared my permissions in a given project with one of the developers and they are pretty much equal (with some unrelated exceptions like deleting projects).
You can control the "Manage test plan" permission on area node level.
Go to area part, right click on the area your test plans belong to and then click on "Security"
Now you can grant rights for managing test plans:
If the area "Manage test plans/suites" permissions are set to allowed as suggested above and you still can't create test plans, don't forget to adjust the Access levels of your user!
Basic users (which should be default) can't access the test case management even if they have the right permissions.
This does not work in the local install I have done. It is stating that advanced permissions is deprecated. And the link to learn more goes no where.
For those that haven't found a solution even turning all the options provided in Elena's answer, you can check this out:
https://developercommunity.visualstudio.com/content/problem/80055/cant-add-a-new-test-plan.html
It seems that Microsoft ask you for a subscription in order to manage test plans. If the user doesn't have a subscription, even if you add him to the project administrator group, he won't be able to create test plans.