The Files Library enables you to centrally store and manage files for use in your Transaction Tests (using the Chrome monitor.) For example, you may wish to configure several Transaction Tests which upload a test file to different websites. Using the Library, you can easily store the test file and then refererence it in each of your Transaction Test profiles.
Adding a File
To add a new File to the Library:
- Navigate to Control Center > Library > Files
- Click New
- Input a friendly name for this file in the File Name field. (e.g. "website transaction script")
- Optionally enter a description, such as the purpose of the file.
- Click "Upload File" and then navigate to the desired file on your local system and click "Open".
- Optionally input one or more labels for this file. (Labels can make it easier for users to locate files in the Library later.)
- Click Save
Using Stored Files
Once you have saved a file in the Library, you can access it when configuring a Transaction Test with the Chrome monitor. Follow these steps to access a stored credential in your configuration:
- Create or edit a Transaction Test (Chrome Monitor)
- Click the "Add File" button.
- Select the desired File from the list of files stored in your Library.
- You can sort the list by any of the displayed columns, and you can search by file name or label.
- If the desired file has not been uploaded yet, you can select the "Create New" tab and upload a file, following steps 3-7 in the previous section.
- You will now see the selected file listed in your Test's configuration blade next to "File." You can reference this file by name in your Transaction Script. For example, if you have selected a file called "test.txt" and you want your Transaction Test to upload it to a remote server, you could include a step in your script similar to the following:
// Step-1
open("https://<somewebsite>.com/")
uploadFile("//*[@id='uploadFile']", "test.txt")
waitForNoRequest("5000")