Creating Tests from Templates

  • 5 minute(s) read
Prev Next

Overview

Catchpoint maintains numerous pre-built Script Templates that make it easy to create Transaction tests for commonly used SaaS (software-as-a-service) applications.  We maintain and update the scripts for each application as needed, so that you only have to provide the bare minimum of information to set up a test, allowing for easy setup and configuration.

Note that you can also create your own Script Templates using the Script Templates Library.

Create a test from a Script Template

To create a Test from a Script template, click on the [+New] button in the Control Center, choose Test > Script Template, and then select the desired template from the list. Next you will select the Product or Folder location for this test. Then the Transaction Test Properties blade opens with the script field already populated with Catchpoint's script. Catchpoint maintains the scripts for each test so that you don’t have to worry about creating the scripts, or updating them as SaaS vendors change things.

A template description will be displayed on the top section of the test, as in this example: 
temp2.png

If your template requires you to input any settings, you will complete those in the  Template Fields section (see accompanying graphic in step 4). You may also modify the Script if needed for your use-case.

If the template requires user account information, the description will instruct you to provide these details.
temp3.png

The Template Fields are mandatory, and the remaining details remain the same as a Transaction or API test.

Special Authentication Scenarios

Some template-based SaaS tests support SSO via OKTA and/or Onelogin, Microsoft Live login services, or Google Account Login services. To utilize any of these login method, you must set up two template-based SaaS tests: one Authentication Test which simply performs an authentication transaction and stores the resulting authentication token/cookie as a global variable, and a second Application Test which uses this global variable to authenticate and do the actual performance testing. The following sections show how to set this up for each system.

OKTA/OneLogin SSO Configuration

To test a system that supports OKTA or OneLogin SSO, configure the following two template-based SaaS tests:

Authentication Test

  1. Click on the [+ New] option in the Control Center then select Tests > SaaS Tests.
  2. Select the appropriate authentication test for your scenario (**OKTA or OneLogin).
  3. Input your SSO URL in the URL field.
  4. Input user credentials with 2-factor authentication disabled in the Requests section:
    temp5.png
  5. Make sure that the test is scheduled to run frequently enough per your system's login time-out policies (every 60-120 minutes is sufficient in most scenarios.)
  6. Save the Test.

Application Test
Now you can configure the desired Application Test(s) using another SaaS test template, and it will automatically use the authentication cookies generated by the authentication test to bypass the login step and go directly to the application's default landing page.

Setting up Microsoft Live and O365 Tests

To test a system that supports Microsoft Live login service, configure the following two template-based SaaS tests:

Authentication Test

  1. Click on the [+ New] option in the Control Center then select Tests > SaaS Tests.
  2. Select Microsoft Live from the list.
  3. Input user credentials with 2-factor authentication disabled in the Requests section:
    tem8.png
  4. Make sure that the test is scheduled to run frequently enough per your system's login time-out policies.
  5. Save the test.

Note: Microsoft Live URLs are not unique to the organization and thus you do not need to provide a URL for Microsoft Live authentication.

Application Test

Now you can configure the desired Application Test(s) using another SaaS test template, and it will automatically use the authentication cookies generated by the authentication test to bypass the login step and go directly to the application's default landing page. The following steps show how to set up the Sharepoint (MS Login) test:

  1. Click on the [+ New] option in the Control Center then select Tests > SaaS Tests.
  2. Choose Sharepoint (MS Login) from the list.
  3. Input your organization'ss unique Sharepoint URL in the URL field.
    Note: Not all O365 tests require this field. Sharepoint, Outlook, and Yammer are exceptions where a unique URL is required.
  4. Complete the test configuration settings per your requirements.
  5. Save the test.

The Sharepoint (MS Login) test will use the Microsoft Live authentication cookies generated by the Microsoft Live authentication test to bypass the login step and go directly to the default Sharepoint landing page.

Setting up Google Account and GSuite tests

To test a system that supports Google Account login services, configure the following two template-based SaaS tests:

Authentication Test

  1. Click on the [+ New] option in the Control Center then select Tests > SaaS Tests.
  2. Select Google Account from the list.
  3. Input user credentials with 2-factor authentication disabled in the Requests section:
    tem8.png
  4. Make sure that the test is scheduled to run frequently enough per your system's login time-out policies.
  5. Save the test.

Note: Google Account URLs are not unique to the organization and thus we do not need to provide a URL for this test.

Application Test
Now you can configure the desired GSuite Application Test(s) using another SaaS test template, and it will automatically use the authentication cookies generated by the authentication test to bypass the login step and go directly to the application's default landing page.

***Note: ***GSuite applications do not need a unique URL associated with an organization.

Your tests will now use Google Account authentication cookies to bypass the login step and go directly to the default landing page.

List of Script Templates by Catchpoint

Catchpoint currently provides Script Templates for the following systems:

  • Microsoft Live (to authenticate Office 365 application tests)
  • Office 365
    • Sharepoint
    • Outlook
    • OneDrive
    • Word
    • Excel
    • Excel (MS Login)
    • PowerPoint
    • OneNote
    • Teams
  • Yammer
  • PowerBI
  • Google Account (to authenticate Gsuite application tests)
  • Gsuite
    • Gmail
    • Calendar
    • Drive
    • Docs
    • Sheets
    • Slides
    • Chat
    • Hangouts
    • Meet
  • Dropbox
  • Box
  • Atlassian
    • JIRA Software
    • Trello
  • SSO via OKTA/OneLogin/OneLogin (MS Login) (to authenticate any of the following application tests)
    • WebEx
    • GoToMeeting
    • Zoom
    • Asana
    • DocuSign
    • Github Enterprise
    • Slack
    • Zendesk login
    • Zendesk Dashboard
    • Catchpoint Logins
    • Dell Test Template
    • iPerf Bandwidth
    • Media Playlists
    • Salesforce