image

Load Testing

Scriptless Cloud Load Testing with Tricentis Tosca + Tricentis Flood

We’re proud to announce the public release of the integration between Tosca and Flood, combining two market-leading solutions to create the first Scriptless Cloud Load Testing solution. 

Historically, teams have needed to invest effort in writing specific scripts just for the sake of running load tests.  Each test can take several days to create — and even worse, these tests are brittle, requiring frequent maintenance.  With this new solution, teams can reuse their existing functional tests as load tests…with no additional scripting work required and minimal maintenance.

With the release of Tosca Version 12.2, Tricentis has delivered a new solution for reusing Tosca functional test cases as load tests.  With this unique integration, Tricentis customers can now easily integrate their Tosca account to Flood, and leverage Tricentis’ Gold Partnership with Microsoft to execute these tests at scale in Azure

Prerequisites to Load Test with Tosca + Flood

The process for reusing Tosca functional tests in Flood is straightforward and simple.  The flow requires the following simple prerequisites before launching your first scriptless cloud load test: 

  • You have created a Flood account by signing up for a free trial
  • You have installed Tosca version 12.2 (Flood integration is not backwards compatible with older versions of Tosca)
  • You have created 1 or more functional UI tests against browser-based apps (web apps, websites) OR API tests you want to use as load tests in Flood
  • You have copied your Flood Token from your Flood Account, as shown below: 
  • You have pasted your token in the “Flood Token” field of their settings in their Tosca Project:

Once these steps are completed, you’re all set to start. 

How to Launch Your First Scriptless Load Test from Tosca

By now, you should have everything set up to launch your first browser-based UI or API test case from Tosca as a load test in Flood.  The following diagram provides an overview of how this process works:

Step 1: User Creates the Tosca Test

For an experienced Tosca user, this will be easy.  You can create any browser-based UI test or API test case and reuse it in Flood.  If you don’t have an eligible test to run, you can always reuse some of the test cases included in your trial for the sample Tricentis Vehicle Insurance Application: 

Step 2: User Uploads the Test to Tosca

To complete this step, the you must first create a load stream object in your Tosca execution list: 

Once the Load Stream has been created, any test that is a browser-based UI test or API test can be dragged and dropped into this folder to create the load test.  Then, just specify the number of users to simulate, length of the test, as well as the regions that the traffic should come from: 

Step 3: Flood Creates Virtual Machines in Azure

To achieve the load needed to simulate the cloud load test, Flood will create the necessary virtual machines in Azure.  Each virtual user will require one virtual machine (Flood calls this a “node”).

There are 2 hosting options for Flood, depending on your requirements around security, cost, and configurability: 

  • Demand option: Use a Flood Azure account to create cloud virtual machines to simulate the load requested
  • Hosted option: Use a Flood account you own, connecting to your Azure account to create your own hosted grids.

To learn more about the different options for hosting, check out our blog on how to make your cloud load testing more secure

Step 4: Virtual Machines Run Tosca via Browser, Browser Calls your App

You have the option to run in various browsers including ChromeFirefox, and Internet Explorer.  Please ensure the cloud load injectors (in our Azure account or your Azure account, depending on your hosting option) can access your application under test. 

Step 5: Virtual Machines Collect Responses from Application

While the report is running, Tosca will open up a browser window showing the live result of the test. The report will update every 15 seconds with new information from the test iterations:

You can monitor the test from this dashboard, with the ability to stop the test as needed. Additionally, you can share the results with stakeholders/team members via a publicly available link:

Step 6: Flood Aggregates Results, Provides Dashboard

Once the test is complete, a dashboard summarizes key metrics like response time (step execution time), number of passed steps, failed steps, and concurrency:

Additionally, there will be a step level detail view, where each step will have its own detailed information on execution time, failure rate, etc.:

Any of these steps can be drilled down further to see information related to the spread of step execution times, specific errors seen, and screenshots of the browser activity (for UI based tests):

Putting it All Together

This general availability release of the Tosca + Flood integration is an exciting step forward in cloud load testing.  Now, organizations can shift more and more of their load testing efforts into their agile development teams to accelerate their development process and increase quality. 

If you want to get started, sign up for a free trial.  If you have any trouble getting the integration setup or questions about how it works, please feel free to drop us a line and we’ll be sure to set up some time to answer your questions.

We hope you enjoy this exciting addition to the Tricentis platform.  Happy Testing!