Testopia Access Control questions
Donovan Stewart
Hopefully someone here will take the time to help me out with Testopia.
I am running Testopia version 2.2 and Bugzilla version 3.2. I have what
I think should be a simple access control question. Below is a list of
what I need to complete.
Abilities of the tester
* Place a test in a running state or idle state
* Pass and fail a test
* Block a test or mark as error
* Pause a test
* Open a bug for a test they are assigned to
* Put notes in the test they are assigned to
No abilities of the tester
* Not edit the test case procedure except for what is listed
above
* Not be able to edit the test case run
* Not be able to edit the plan at all
I can use the current permissions of the test plan for this but write
permissions is too much as they can now do everything that is listed in
the No ability section. If I give read only they get errors stating they
do not have permission to do that and if the test is in the running
state only the assignee can make changes. They are the assignee and it
does not work still.
Thanks
Gregary Hendricks
<4160E32E63CA8047A63...@vs-sbs.Virtensys-US.local>, "Donovan
Permissions are set at a plan level and cascade to items below, meaning that if they have write access to the plan, they are able to change the test cases and runs as well. The level of granularity you describe above is not available in Testopia as of now.
To be honest, I don't see why you would not trust your testers to have write permissions in the test case as that way they can fix test cases that are incomplete or incorrect as they are testing. Besides, any changes that are made are tracked so you could find out who made a change and when if someone did do something malicious.
Greg
Donovan Stewart
You are correct in most cases there should not be a reason to change a
test case but when you are paying remote testers in another country to
run only test cases we come across issues where the expected result is
not understood. So a test will change the expected result to what they
are seeing and mark the test as a pass. This means as a plan owner I
have to monitor these changes.
Maybe a good work around is to get an email notification when something
has been changed is this possible or do I have to look at the change
history?
I have one other question.
Where is the best place to do feature requests at? I think there is a
need for a test case repository. A simple place that I can add test
cases by type and then add them to plans as needed. This is a common
feature in many test case management systems.
Thanks
Donovan
Gregary Hendricks
<4160E32E63CA8047A63...@vs-sbs.Virtensys-US.local>, "Donovan
Stewart" <donovan...@virtensys.com> wrote:
> Hi Greg
>
> You are correct in most cases there should not be a reason to change a
> test case but when you are paying remote testers in another country to
> run only test cases we come across issues where the expected result is
> not understood. So a test will change the expected result to what they
> are seeing and mark the test as a pass. This means as a plan owner I
> have to monitor these changes.
>
> Maybe a good work around is to get an email notification when something
> has been changed is this possible or do I have to look at the change
> history?
This has been another oft requested feature. One that I have never gotten around to yet.
> I have one other question.
>
> Where is the best place to do feature requests at? I think there is a
> need for a test case repository. A simple place that I can add test
> cases by type and then add them to plans as needed. This is a common
> feature in many test case management systems.
You can always create a testplan and call it "Repository" or something like that, and then link the cases to the other plans as you go.
You can open enhancement requests at http://bugzilla.mozilla.org under product Testopia.
Just set the severity to "Enhancement".
Greg
Donovan Stewart
Donovan
-----Original Message-----
From: Gregary Hendricks [mailto:ghend...@novell.com]
Sent: Tuesday, September 01, 2009 9:39 AM
To: support-...@lists.mozilla.org; Donovan Stewart