Release Notes - 01 Oct 2018
Included in this release are the following features:
- Ability to distribute the 'Capacity' and 'Concurrency' of your Worksoft SaaS Domain to Projects and Users using Worksoft SaaS QaCONNECT REST API Service
-
Allocate (distribute) the capacity and/or concurrency available at the domain level to projects within the domain and for each project within the domain, distribute the capacity and/or concurrency available to the users that are authorized to the project. You can also reserve a minimum capacity and/or concurrency to specific projects and/or users and also set the execution priority/precedence for test runs within projects and triggered by specific users
-
Deallocate the capacity and concurrency limits previously assigned for one or more projects. Capacity and/or concurrency allocations, if any, that exist for the users that are authorized for each project in the JSON input to the service request, will be unassigned first and then project-level allocations will be removed.
-
Deallocate the capacity and concurrency limits previously assigned for one or more users within a specific project within a specific domain.
This is a major feature requested by many of you. Though it took a while for us to prioritize this feature within our product roadmap, we are excited that we have been able to give you lot more capability within this feature than what was requested.
As you all know, in Worksoft SaaS, for each type of subscription (UI/Functional/API Testing, Volume Testing) that a domain is subscribed to, finite capacity (max hours of test execution per a specific time window) and concurrency (max number of parallel tests that could be run) is available. So far, the capacity and concurrency that is available at the domain level was 'shared' across all the projects within that domain and the users that had access to those projects 'shared' that capacity or concurrency.
With this release, you will be able to allocate (distribute) the capacity and/or concurrency that is available at the domain level to projects and/or users within the domain, based on the needs and projected usage patterns within the projects and by the users that have access to those projects. This allows projects or teams that execute more tests or more hours of tests to be allocated higher capacity and/or concurrency. You will also be able to adjust the capacity and/or concurrency allocated to the projects and/or users as the needs or usage patterns change from time to time.
You will also be able to set an execution priority (precedence) for tests triggered for execution within a project and or users 'relative' to the tests executed within other projects or triggered for execution by other users. For those of you that are familiar with the 'nice' command in Linux and Unix, the execution priority works in a similar fashion. The lower the execution priority that is assigned, the higher precedence/priority that is given to tests executed by specific users or within specific projects.
The visual below illustrates the power of this feature. The picture showcases for a (fictitious) domain that has two different subscriptions (a) UI/Functional/API Testing and (b) Volume Testing how the capacity and concurrency available at the domain level is distributed to various projects and users.
In this release, the allocation and deallocation of capacity and/or concurrency to projects and/or users can be done very easily using three new services available within the Worksoft SaaS QaCONNECT REST API . Refer to the 'Account' section in the docs page of Worksoft SaaS QaCONNECT REST API.
You may be thinking, "Ok, Using the three new powerful services I can allocate and maintain (adjust) the capacity and/or concurrency that is available at the domain level to projects and/or users. But how do I get visibility into the how the capacity and/or concurrency is currently distributed?". Don't worry. We now have a new (excel) report called "Subscription Capacity and Concurrency Allocation Report" that is available as part of the 'Subscription Usage' report set within Worksoft SaaS Analytics.
We strongly recommend that you tap into the power of this feature and allocate the capacity and/or concurrency to projects and/or users within your domain. If you need any help in doing so, please do not hesitate to reach out to the Worksoft SaaS helpdesk or the extended product support.
Share your ideas – Help us improve Worksoft SaaS!
We could not have gotten Worksoft SaaS to where it is without some brilliant ideas from all of you. Keep the suggestions and ideas for improvement flowing!
To submit an idea or vote on some of the features requested by other customers, click here