/experience-scripts

AppNeta Experience - Example Selenium Scripts

Primary LanguageHTML

Each folder contains a unique README.md file with specific details regarding the Experience Target (the URL that is entered into the Monitor to... section when configuring a Web App Group - see image below) as well as any specific variables that will need to be defined for the script to work. Please note, variables are already included in the provided scripts so it is imperative that the variables be defined exactly as written to be valid when used by the script.

Image of Web App Group Creation

Image of Transposing the Target URL

The html files in each folder contain the script described by the title pre-formatted to be copy and pasted straight into the AppNeta Performance Manager Workflow creation screen.

HOW TO USE THE SCRIPTS PROVIDED

To insert the scripts, simply select the entire body of the appropriate .html file here in GitHub and copy that data to your clipboard.

Gif of Script Copy

Once that data is in your clipboard, navigate to the Web App Group page in APM and select Configure and then click on the Workflows... section (see image below) to enter the workflow editor.

Image of Web App Group Workflow Example

Once in the editor screen, you'll be presented with a tabular view with just a single entry that says open: Image of Workflow Default Page

On this page, you'll want to click on the Source tab in order to get to the xml view of the script. From the Source tab, select all of the items inside of the code box by either highlighting or clicking and performing a Select All command to highlight the full body of the code. You can then simply paste the copied script (from the earlier step indicated above) over the selected text. Once done, switching back to the Table tab will show multiple inputs as indicated in the below gif.

Gif of Pasting the Script

The next steps in the process include renaming the workflow to be something meaningful (which is especially useful if you are going to be configuring multiple workflows for a single application) and then defining the variables as outlined in the README.md files for each of the script groups.

Renaming the script: Image of rename the script

Defining variables:

Gif of defining variables

When defining variables, it is extremely critical that the name of the variable (i.e. username, password, etc) match the case of the variables listed in the script README.md files. The script will fail if the case and spelling do not match exactly.

Image of Transposing Variables