Lesson 10 Topic 6 Features
This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of Worksoft SaaS.Please refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 10 :: Topic 6
1. Encrypt/Decrypt Instructions
In most cases, we may have the need to encrypt certain information, especially before executing the test. For Example: This could be the password used to login to the AUT or sensitive information in the Test data. In Worksoft SaaS, you have an encrypt feature available at the Instruction level within the Test Script and also in the UDV's.
For data definitions, you can mark the attributes for which you want all data in any data file to be encrypted.
When tests run that involve any data (from the 3 different entity types listed above) that is marked for encryption, then on the test execution results page the data shows up encrypted.
At a Test Script level, it is important to remember that all users having edit access to the Test Script, can encrypt/decrypt the values that are encrypted by other users and vice versa.
When tests run that involve any data (from the 3 different entity types listed above) that is marked for encryption, then on the test execution results page the data shows up encrypted.
At a Test Script level, it is important to remember that all users having edit access to the Test Script, can encrypt/decrypt the values that are encrypted by other users and vice versa.
At a User Defined Variable level, you can encrypt the UDV value and it is not possible for anyone (including you) to decrypt it. The only option is to edit the encrypted value and override.
Based on your need, you can either encrypt the instruction in the Test Script or you can parameterize the Instruction to a UDV and encrypt the UDV value.
2. Temporary Decryption
There is another icon 'that looks like eye', it gets enabled only when the values are encrypted. It can temporarily decrypt the actual values on click. This is beneficial in case you only want to see the value and avoid you accidentally saving the test script with a clear-text value. In this way, you can optimally use the encrypt/decrypt button only to make changes.