Secure test information

When a test must contain sensitive information, such as user names or passwords, to access the application being tested, you can use the OpenText Functional Testing for Developers SDK to make this sensitive data harder to access.

1. Use the Password Encoder tool to generate an encoded string resembling a mix of jumbled characters. This prevents the password from appearing in cleartext.

   Caution: The Password Encoder tool does not use a global standard for encryption. It is not considered nor is it intended to be secure. Its only purpose is to ensure that passwords do not appear in cleartext while editing or running a test. The actual passwords and/or data are stored with your test's source code. If you are using real customer data or other sensitive information, you should take additional steps to ensure the security of that data.

   Run the Password Encoder tool as follows:

   OS	How to run the Password Encoder tool
   Windows	From the Start menu In your IDE after you install the IDE plugin: Functional Testing for Developers > Tools menu
   Mac/Linux	In Terminal: Change to the <Installdir>/Tools directory Run ./password-encoder <password-to-encode> [-me], where <password-to-encode> is the password you want to encode.

2. When entering a password into a password field, use the generated string as the argument for a <TestObject>.SetSecure step (instead of the normal Set method). This hides the password, preventing it from being displayed in cleartext, but does not fully secure the password.

   For usage details, see the relevant SDK Reference.