Skip to content

Creating a New Product within a Project

Before reading this you might want to read: 

Main Article


A Product in Worksoft SaaS represents an "application" for which you want to develop and execute automated tests. 

A project may involve developing test automation in the context of more than one application. Typically you define 'environments' at the project level. For example, you may have a 'Dev/Integration environment', 'QA environment' and a 'Production environment' for all apps (products) that your project involves.

In Worksoft SaaS, the automated test scripts are at the product level whereas the 'test scenarios' and 'run definitions' can span test scripts across products. 

A Project must have at least one Product. There is no limit on the maximum number of Products a Project can have.

Steps to create a Product:

1. Navigate to Products screen from "Hamburger Menu". All the Products that are created for that specific Project are listed on that screen.

2. Click on New Product button and enter the following details:
  • Enter Product Name (Mandatory)
  • Add a Description (Optional). It is a best practice for you to key in a description for your product.
  • Select the 'Application Type'. The available options are:
Based on the Application Type selected the 'Application Access Type' populates. To understand more about the Application type read through the document.

Web Apps: 


To configure a Web App, edit the environment by clicking on edit icon in "Actions" field for the corresponding environment. In the overlay that opens up choose "Application Access Type" as Public URL or Secure Tunnel Based Access.



  • Public URL: Enter the environment specific Web URLs of the application in the respective cells.  Your application will have a different URL in each of the environment they are deployed in. For instance, the next generation/version of your application most likely is always deployed into your dev/integration or QA environment while the most stable version is probably deployed into your production environment and each of these versions is accessible by a different URL.
  • Secure Tunnel Based Access:  If your app is not publicly accessible and is hosted on servers behind your company's firewalls, you can allow Worksoft SaaS access to it using the 'Secure Tunnel  Based Access'. To read more about Secure Tunnel Access and set up a tunnel, click here. 

    For 'Secure Tunnel Based Access' an additional step to provide the Tunnel name configured during the setup is required for the environments that are behind the firewall.

    • While on the overlay, in the accordion "Product-Environment Details" select option  Secure Tunnel Based Access  in the "Application Access Type" field.
    • In the accordion "Secure Cloud Tunnels" you can configure one or more Secure Tunnels by providing a combination of the Cloud Platform, Tunnel Name, and the Default Tunnel for an environment.
    • Once done click on Submit


    NOTE: While creating a Testing Context on the environment with Secure Cloud Tunnel, you will given an option to either choose the default tunnel or  select specific tunnel that you would like to use.

    Native/Hybrid Mobile Apps:

    If your Application is a Native/Hybrid Mobile App, you have additional details you need to fill before you can upload the mobile binary for usage in Worksoft SaaS.

    • Select the corresponding "Application Type" (Native or Hybrid) from the drop-down that is populated. 
    • Upon selection, any of these application types select the "Mobile Operating System" (Android, iOS) for which the application is built for. If you have the app available for both the operating systems, you can chose to check both the check boxes.
    • Select the "Device Type(s) on which the App can be used" on which the application is supposed to be tested (Mobile Phone, Mobile Tablet).


        Uploading Mobile App Binary:
        Once the above options are chosen as a last step you need to upload Mobile App Binary OR provide the link where the binary is available. To complete this step refer to the article   here .

        Once you have Mobile App binaries uploaded and tests executed, you may want to delete the app and upload a new one as a new version is available Or just replace the mobile binary. It is important for you to delete the old mobile binaries, especially if you have no intention of using them in the future. This will keep the list of available mobile app binaries short and crisp that will make it easy for you to search for and link one of those binaries for additional project environments.

        The delinking/deleting can be done standalone or implicitly as part of replacing the previously used binary with a new mobile app binary. This functionality is made available from two places; you can access this functionality either from Edit Product page or the overlay.



        When you access the option, you will be provided with three options.

        1. Delink the Mobile App binary and also delete from Worksoft & External secure storage
        2. Upload New Mobile App binary and delink & delete old binary from both Worksoft & External secure storage for the selected environment
        3. Cancel the request.

        If you select option (1), Mobile App binary is delinked immediately from the selected environment. If you choose option (2), you are shown the "Edit Product Configuration for an Environment" overlay with "Manage Mobile Application Binary" accordion expanded. You can edit version and also choose new binary to be uploaded.


        NOTE: While in the message it is stated that Mobile App binary would be deleted from Worksoft & External secure storages upon delinking of the binary, it doesn't happen immediately. System checks if the same binary is used in any other environment. If it finds that the binary is used elsewhere it doesn't delete the app. Mobile App binary is deleted only if it is not used in any other environment.

        After reading this you might want to read: 

         

        Feedback and Knowledge Base