Skip to content

wsCONNECT Overview

Worksoft SaaS wsCONNECT (ws stands for Web Services) is a product of Worksoft SaaS that offers a very powerful and highly secure way for you to integrate your automated tests within Worksoft SaaS platform with web service(s) behind your company's firewalls (or publicly accessible web services).  

The most interesting part is that you will be able to integrate your automated tests with your web services behind your firewalls without any programming or coding.

   

To understand more about wsCONNECT Subscription please click here.

Worksoft SaaS supports a variety of powerful commands that will help you implement the integration of the test scripts within your Worksoft SaaS domain with publicly-accessible web services or web services accessible only within your company's firewalls. Click here to view the list of commands supported, understand their purpose and to view example(s) that will help you easily integrate your automated tests with web services.

In Worksoft SaaS the commands related to JSON / XML can be used in the context of the the following common use cases:

  • You want to read the data from a Web Service (REST & SOAP) and use the data as part of the automated tests running in Worksoft SaaS.
  • You want your automated test running in Worksoft SaaS to read some values from the User Interface of your AUT and/or Data Files within Worksoft SaaS and feed such data into a Web Service (that accepts JSON / XML / Primitive Types as input) that does some processing that is a precursor for any additional automated tests to be executed in Worksoft SaaS.
  • When you need to store a relatively small set of key-value pairs, it may be more efficient for you to store the data in JSON format or XML format.

Use Cases for wsCONNECT:

  • The User-Interface of your Application-Under-Test (AUT, as we refer to it) does NOT display all the data elements you are interested in verifying as part of your tests and such data is available for verification only within the web service(s) behind your AUT.



    A perfect example of this use case is an Insurance Quoting application where the user-interface typically only shows the total premium to be paid by a customer but the database typically stores all interim sub-totals or component values of the total premium, and as part of your test you have to verify not only the total premium but also the sub-components that make up the total premium.
  • The test inputs for your automated tests frequently change and "static" Data Files that you may have used to feed your "Data-driven" tests in Worksoft SaaS may be taking too much manual time for you to constantly/frequently update with the most current data that is available from web services behind your firewalls.

    A great example of this use case is an eCommerce company where in the list of products and/or their details (price, discounts) in your product catalog that may be changing frequently. Instead of periodically spending manual time (supported by some SQL queries and/or programming language based code) to create Data Files that you have to use to replace previous versions of the Data Files that were uploaded into Worksoft SaaS, you can use wsCONNECT to dynamically pull the appropriate data directly from your web services and avoid the effort to constantly update the data in your Data Files.
  • The test inputs for your automated tests are of "one-time use" and your tests always need new data before they are executed the next time and such data is available quickly if you were to make a call to a web service.


    A great example of this use case is an eCommerce Store-Front applications that need Coupon Codes or Promotion Codes that expire after a Single-Use. You can use wsCONNECT to dynamically retrieve the next set of Promotion or Coupon Codes for your automated tests to use directly from your web service(s).
  • Not all workflows within your application are automation-friendly and you need a mechanism to move the processing along to account for workflows that are not automation-friendly

    Using wsCONNECT you can trigger those workflows so that automated tests for subsequent workflows (that are automation-friendly) could be executed. Worksoft SaaS dbCONNECT could be your missing link for end-to-end automation of your tests.

 
 

Feedback and Knowledge Base