Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User webapi is unnecessary #65

Closed
kirantpatil opened this issue Jan 10, 2015 · 6 comments
Closed

User webapi is unnecessary #65

kirantpatil opened this issue Jan 10, 2015 · 6 comments

Comments

@kirantpatil
Copy link
Contributor

In reality we don't see a separate user for automation purpose.

So, IMHO it is better to remove webapi user and allow by default QA manager, Senior Tester and Tester to act as webapi user.

Thanks.

@kiranfractal
Copy link

Any thoughts on this change ?

@joffems
Copy link
Member

joffems commented Jan 12, 2015

I prefer having a separate user for tracking and auditing purposes.

@kirantpatil
Copy link
Contributor Author

How about combining roles ?

Ex: Tester + Webapi user, Senior Tester + Webapi User

That way we will have more granularity for user roles.

On Mon, Jan 12, 2015 at 8:35 PM, joffems notifications@github.com wrote:

I prefer having a separate user for tracking and auditing purposes.

Reply to this email directly or view it on GitHub
#65 (comment).

@joffems
Copy link
Member

joffems commented Jan 12, 2015

I don't have a problem with assigning multiple roles to a user, but that is a lower priority task.

I'm still not sure what the major issue is that we're trying to address here. Why do you want automated script tasks to be run by users?

@kirantpatil
Copy link
Contributor Author

In product companies a person who is testing a module has to automate the same. He is the owner for both manual testing and automation.

With this combining roles we will have most flexibility and satisfies the requirement for different people needs.

@kirantpatil
Copy link
Contributor Author

Closing this for now and feel free to reopen if it make sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants