Skip to content

Quick Guide to Regression Testing with Worksoft SaaS

← Getting Started with Worksoft SaaS

Before you read this article:


Note: Some of the tasks listed in this article require customer administrator privileges. 

Main Article


If you are a first time Worksoft SaaS user, this is the right place to start. This article helps you get started with Worksoft SaaS and QaSCRIBE. Here you will see the sequence of steps that you will have to follow to create a project, automate test scripts, assemble test scenarios and run tests.

If you are the person that signed up for Worksoft SaaS, and have logged into Worksoft SaaS for the first time, you will go through the following process (screens) in Worksoft SaaS to set up/configure the Worksoft SaaS domain to meet your company's needs:
  1. Set up your personal profile: You can change your password, set up security question & answers, choose your preferred timezone and language. Please refer to the article 'First Time Login - Set Up Your Profile' on how to set up your profile.

  2. Project Set Up (Quick Start): You will be be taken through a fast-track or quick start process where in you can set up your first Project in Worksoft SaaS. Worksoft SaaS will automatically create a Project with the name you enter and create a Product under that Project with the same name as the Project and create an environment called 'QA environment' for that project and will prompt you to enter the URL that points to the first application (we call it a Product in Worksoft SaaS) you want to use Worksoft SaaS to run automated tests against in your QA environment. As part of this process, you will also be given an option to create one or more additional users that you would like to have access to your Worksoft SaaS domain. Please refer to the article 'Create New Project' on how to set up your first project. 

  3. Decide where you want to go next: Once you set up your first project and optionally create (other) users for your domain, you will be provided options to jump to perform one of the following tasks:
  • Go to download QaSCRIBE, the Test Script authoring tool so that you can start your journey with automating your manual test cases OR
  • Continue further configuring your first Project you created
  • Set up additional Environments that you will use for the first project you created via the Quick Start process OR
  • Configure the modules/components and requirements/use cases for your first Project OR
  • Configure the 'notifications' you want Worksoft SaaS to automatically send via email when key events happen within your first Project
  • Integrate your Atlassian JIRA account with Worksoft SaaS

Project Selector drop-down:


This is the drop down at the top right of the page right below your name. We call this the Project Selector.

If you are a Customer Administrator for your domain, when you login, you will see the Project Selector default to "Administration". This tells you that you are in the administration Work Area for your domain.

This dropdown also lists the Projects that you have access to once the Project(s) are set up within your domain. Once you go through the Quick Start process and choose any of the options (step 3 above), Worksoft SaaS will automatically switch the Project Selector context to your first Project.

Creating Projects and Users


To create the project(s) and add the user(s) that you want to work on those project(s), follow the links below to complete these steps:
Remember that you will have to add yourself to the project if you want to have access it (and have it show up in the list of projects in the Project Selector).  

Setting Up / Configuring a Project as Project Admin once Project is created.


If it is the first time the project is being accessed, Worksoft SaaS will prompt you to complete the project setup. The following article will walk you through this process:
Once you have completed this setup, your Worksoft SaaS project is ready for you to create test scripts, assemble test scenarios and run tests.  

First Time Logging in as a (non-administrative) User


If you are a Worksoft SaaS customer user (i.e. you are not an administrator), you will also be expected to set up your authentication profile first and to set up your password (change it from the initial password emailed to you by Worksoft SaaS when your domain's administrator set up your user account on Worksoft SaaS). Once you set up your authentication You will be directly taken to the project Work Area of your first project. You will see all the projects to which you have access in the Project Selector dropdown.

Building Test Scripts


'Test Scripts' are the lowest level of an automation artifact in Worksoft SaaS. QaSCRIBE is the primary vehicle for you to 'author' and 'unit test' your Test Scripts. Test Scripts are akin to the lowest level of Lego blocks. 

  It is a 'programming-less' scripting tool that supports a wide variety of commands and constructs including constructs for:
  • Identifying and interacting with User-interface elements within your applications
  • Conditional (Branching) Logic (If, ElseIf, Else, EndIf)
  • Looping & Jumping Flow Control (While, For, ForEach, Continue, Break, GoTo, GoToIf, Label, SkipNext, and ExitTest)
  • Testing UI Look & Feel/Styles (font style, size, colors, etc.,)
  • Encryption of sensitive data within your tests
  • Simultaneous capture of all available location schemes for UI elements
Once you are satisfied with the results of your unit testing, you can save your Test Scripts to project-level 'Test Script Library' within your Worksoft SaaS domain (Worksoft SaaS application). The test scripts within your Test Script Library are available for you and your peers that have access to the project within your Worksoft SaaS domain. You all can collaborate to maintain the test scripts from that point in.
                                               
The Test Scripts in your Library can then be assembled into Test Scenarios using an intuitive and user-friendly workflow within the Worksoft SaaS application. You can validate/certify the Test Scenarios against each Browser and/or Device of interest to you (we call them testing platforms). This is equivalent to your 'integration testing' if you will. Then you assemble one or more Test Scenarios into a higher level of an automation unit called 'Run Definition', which then can be scheduled for execution from within Worksoft SaaS application or from your CI environment on a schedule.  

Each test will run as a 'Web Driver' (or 'Appium') test on a freshly provisioned machine with the appropriate testing platform from one of the ready-to-use 900+ combinations of browsers, mobile devices, and operating systems). In other words, QaSCRIBE is only needed for your script authoring and NOT required (or is not utilized) when your automated tests get executed on the Worksoft SaaS Cloud. 

While QaSCRIBE is the primary vehicle for you to begin your automation, Worksoft SaaS application offers you a significant number of additional powerful features that allow you to further enhance your Test Scripts further:
  • You can make your Test Scripts 'data-driven', a really powerful feature that Worksoft SaaS offers to help you very easily and efficiently increase your test coverage without requiring too much effort. 
  • You can make use of user-defined variables that you can configure for each of your application environments and make your Test Scripts save and retrieve values from such user-defined variables
  • You can make use of one of many system-level variables that Worksoft SaaS offers you.
  • You can create nested data loops to satisfy your complex automation requirements
  • You can build and maintain traceability of your Test Scripts to your functional requirements (user stories, use cases or whatever name you use to refer to your functional requirements), application modules/components. 
  • You can also use 'Google-style' labels to categorize/label your Test Scripts in as many ways as you want to categorize them for easier search-ability and maintenance. 
We are confident that you will very quickly be able to tap into the rich features mentioned above. But for now, we'd like you to help you first with installing QaSCRIBE, getting familiarized with it, and proceeding to create test scripts and schedule the tests in the Worksoft SaaS application.

These articles will walk you through the process of installing QaSCRIBE and build your first test script:
Once you have gone through these articles, you should be comfortable using QaSCRIBE to build and run tests. If you run into any automation challenges you can also take a look at the article on "Common Challenges in Automation of Web Application Testing"

Test Assembly


You can now directly use the automated test scripts or upload your test scripts (only product type of native/hybrid applications) on to Worksoft SaaS and assemble test scenarios that can run on the Worksoft SaaS Cloud. The following articles will walk you through the process of getting your test scripts on Worksoft SaaS, assembling test scenarios and running your tests.
Congratulations! You have successfully automated your tests without any programming and run your tests on Worksoft SaaS Cloud. You can create and run more tests at this time or you can continue on to take a look at Worksoft SaaS Analytics.

Worksoft SaaS Analytics


Do you want to know if your software quality is improving over time?

It is great to know if your test passed or failed, but this information by itself has limited use if your goal is to improve software quality. You need to get specific, actionable intelligence to show you where and when the software fails.

Worksoft SaaS® can tell you where your test failed and show you screenshots of your application’s response. It can then show you how the failures in a test run compare to tests that were performed earlier. Detailed analytics that allows you to compare the response to a test scenario (or test script) across browsers, operating systems, development environments, time periods or software versions can help you isolate problem areas in your code. You can also identify software modules that are most trouble-prone or product features that tend to break in specific browsers.

This is just the tip of the iceberg when it comes to what you can learn from Worksoft SaaS® Analytics.

Feedback and Knowledge Base

(thinking…)