Sharing a test and hiding a password?

Ask general questions here.
Fergal
Certified Professional
Certified Professional
Posts: 298
Joined: Tue Feb 18, 2014 2:14 pm
Location: Co Louth, Ireland
Contact:

Sharing a test and hiding a password?

Post by Fergal » Mon Feb 20, 2017 1:09 pm

(Ranorex 6.2.1)

Scenario
A number of testers are working on the same test suite. Each tester has their own username and password to access the system under test. The test suite includes a Test Case to log into the system.

How can the test suite be shared among the testers, in such a way that the Log In test runs on each individual tester's machine, but that each user's password is kept private to that individual?

Thanks!

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 3934
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Sharing a test and hiding a password?

Post by odklizec » Mon Feb 20, 2017 1:56 pm

Hi,

I'm afraid, there is no possibility to hide user names/passwords in test suite files. The only possibility I see is to not include the user credentials in the test suite at all and simply pass them via command line and global parameters connected to required test module variables. This way, nobody is able to read the credentials of other users from the Test Suite files (test modules or data connectors). Hope this helps? ;)
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration

Martin
Posts: 152
Joined: Fri Aug 15, 2014 12:24 pm

Re: Sharing a test and hiding a password?

Post by Martin » Mon Feb 20, 2017 2:17 pm

odklizec wrote:Hi,

I'm afraid, there is no possibility to hide user names/passwords in test suite files. The only possibility I see is to not include the user credentials in the test suite at all and simply pass them via command line and global parameters connected to required test module variables. This way, nobody is able to read the credentials of other users from the Test Suite files (test modules or data connectors). Hope this helps? ;)
Still depending on the setup it might be visible. Lets take Jenkins for example where logs display this kind of info. Probably there are plugins to hide some data in logs.

But locally using .bat files for example to run the tests will not have an issue.

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 3934
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Sharing a test and hiding a password?

Post by odklizec » Mon Feb 20, 2017 2:30 pm

Hi Martin,

Of course, it's possible to hide user credentials (and other sensitive data) in Ranorex output (either log or report file). This can be done via Mask combo in Manage Data Sources dialog.

But I guess Fergal's problem is different. He just don't that members of the dev. team see each others credentials? And if they store them in data connectors/test modules, they are available to all people working with the test suite. In this case, the only solution is to not include credentials (and other sensitive data) to Test Suite.
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration

Fergal
Certified Professional
Certified Professional
Posts: 298
Joined: Tue Feb 18, 2014 2:14 pm
Location: Co Louth, Ireland
Contact:

Re: Sharing a test and hiding a password?

Post by Fergal » Mon Feb 20, 2017 3:41 pm

Thanks for your replies.
odklizec wrote:...the only solution is to not include credentials (and other sensitive data) to Test Suite.
Will go with that approach for the moment and will try to get a testing account set up that can be used by all testers.

Thanks again.

krstcs
Ranorex Guru
Posts: 2683
Joined: Tue Feb 07, 2012 4:14 pm
Location: Austin, Texas, USA

Re: Sharing a test and hiding a password?

Post by krstcs » Mon Feb 20, 2017 4:48 pm

You should not be using real user's information in tests. You should have a (or a set of) test user(s) that have a known password, and that are only available in the test environment.

Again, real user data should not be used due to issue like what is happening here.
Shortcuts usually aren't...