Managing AUT passwords
TestArchitect can save and encrypt passwords which are used for access to an application under test. Encrypted passwords can then be used within tests in combination with the enter built-in action.
Typically, the built-in enter action is used to automate the process of supplying login credentials when so prompted by the AUT. TestArchitect recognizes the security risk posed by this aspect of the test process, and so allows for encryption of passwords within both the test editor and test results. For example, if you create an automated test procedure that logs into an e-banking system and retrieves the current balance, you would not want unauthorized users to be able to read the login information from the test editor or generated test results.
Password encryption is implemented in such a way that only authorized users (for example, administrators or test managers) can read, modify, and manage passwords. Passwords are managed using the Manage Passwords dialog box.
- The Manage Passwords dialog box is available from the context menu of a project when it is right-clicked (select Manage Passwords).
- Password encryption can only be used in combination with the enter built-in action.
Adding new AUT passwords
TestArchitect allows new encrypted passwords to be added to all types of controls for security enhancement.
Editing AUT passwords
After creating an encrypted password, you can edit it.
Deleting AUT passwords
If you no longer need to use an encrypted password, you can delete it.
Using encrypted AUT passwords
Encrypted passwords can be used in combination with the enter built-in action.
Rules for executing AUT passwords
A summary of the guidelines for executing encrypted passwords.