In automation projects, the scripts deal with various user IDs and passwords, be it application credentials or other similar things, and in many cases, the automation scripts are maintained by multiple people/teams. In such situations, encrypted data is used to prevent exposure of original data unnecessarily.
To encrypt critical data using Qualitia:
Qualitia provides two approaches to encrypt data:
I. Using Environment Variable screen:
1. Go to Setting > Environment Variable.
2. Enter the critical data using ENCRYPT(...) token and move out from the cell.
Post encryption, the data reflects as under:
II. Using Development Screen:
- Go to Development > Test case.
- Create a new test case or open an existing test case.
- Enter the critical data using ENCRYPT(…) token and move out from the cell.
- This token uses static data as well as data sheet for encryption.
Post encryption, the data reflects as under:
Using Encrypted Data in Test Case(s)
Qualitia provides the following actions to set encrypt data. ENCRYPT token is only used in the below actions:
- SecureSet
- SecureSetTextinCellEdit
- SecureStoreVariable
These actions decrypt the encrypted data first and then set the original decrypted value in a password field.
You can also use Environment Variable in these actions in encrypted format.
Limitations
- The actions are applicable to non-secured edit box as well. This should be allowed only for the password field and however, it can be done on normal edit boxes as well.
- There is no provision to store secured value at runtime as in encrypted state.
- Data once encrypted cannot be decrypted, not even within the application. This is to ensure utmost security.
- Once you have entered the data and it is encrypted, there is no way to validate if it is correct. This could be an issue if incorrect data is input and then it gets encrypted.
- Data comparisons for secured data will only be done on the encrypted data.
