| || |
Manage Accounts for Testers in Large Organizations
We have 50 some applications (homegrown and off-the-shelf) in our testing environment that need testing on a regular basis. Different application has different security model i.e. some requires account in domain controller, some need account in both DC and application, some need database level access, some requires you to login to the workstation as certain user... etc this gets extremely complicated. Tester/developers ask system admins to create accounts for them and request various permissions on those systems ad-hoc and most of the time they don't even know what kind of permission they need as various dissimilar systems are interconnected. This creates nightmare for the admins especially when he has to keep track of who is doing what on which system (this is mandatory). For some application we created generic accounts and associated privilege based on role e.g. auditclerk, uat-tester, sit-tester, surveilanceclerk etc. Or is it a better idea to use named account for each tester, how do I stragise the access with that account on so many different system especially in a very dynamic environment? The problem with generic account is that there's no way of knowing who is doing what.
I'm new in QA world and right now I'm really clueless as to what's the best way to put some method into the madness. How are you managing test accounts in your organization? I couldn't find any relevant documentation regarding this. There has to be a way to simplify this process, strategise account/role need and channel them coherently to system admins, there must be a way to cut down the number of account to perform testing into manageable size. Have you ever faced this kind of problem? Any help is much appreciated.
Re: Manage Accounts for Testers in Large Organizations
Doesnt this depend on the kind of the testing , qa does ?, if the tester does unit testing, i am sure he will require same level of access as developer,it all depends on the kind of testing one is doing?
What kind of environment do you provide to testers? are you providing seperate DB to the testers ? if yes than i think it should not be an issue.While DC accounts can be a pain, but still you can create the Dummy DC accounts.
Hope you are talking about the accounts where your application is binded with your DC account since as intranet sites.
Re: Manage Accounts for Testers in Large Organizat
QA does only SIT (Systems Integration Testing) and UAT (User Acceptance Testing) Developers do the unit testing themselves. The testing environment is identical to that of production on a smaller scale (i.e no fault tolerance, redundancy built into it) But testers have their own separate environment with all the bells and whistles (app servers, DB etc)