These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
Song Chen suggested an idea (#1997) · Sep 11, 2017 at 10:25 PM · job schedulingportaltestshell
Currently test suite is associated to domain, but test and test folder is not associated to domain.
Request feature to associate any Shared test/folder to one or multiple domains. By default a Shared test/folder can be associated to all domains (current behavior) or only Global (similar to domain association for resource, topology, etc.)
When user creates a new test suite, it would be good that user can only see Shared tests and Shared test folders that are associated to the domain, in which the user logs in.
We have customer Verizon MTCE requesting this feature, as they have many Shared tests. In their use case, a test is supposed to be used only for certain domain(s). Right now, user can see and select any test to add into test suite. This is not desirable.
Alona Getzler commented · Sep 12, 2017 at 08:02 AM
Hi, thank you for posting this idea. It definitely makes sense to associate a shared test to domain in Job Scheduling. However, it is currently not in our plans. Looking forwards to see the votes on this one.
Anyway, you can filter a test by user/group - it is possible to define permissions on a test which will determine which users or groups will be able view and associate the test to a job. To do that right-click on the test in TestShell Studio, select Properties and go to the Permissions tab.
I hope this helps, Alona.
Song Chen commented · Sep 12, 2017 at 02:57 PM
Thanks Alona. Is there API to set such Permissions? At Verizon MTCE, we batch create Shared tests. We can set appropriate Permissions for each test if API is available. But it is not practical to manually do it.
There is no API for this action, only TestShell Studio UI.
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
Help us make things better. Share your great idea or vote for other people's.
provide method to provide cloudshell portal encrypted user input password in test suite
Full Report Search added to Job Scheduling section of the portal
add a link to the deployed sandbox from scheduling suite/job
Customize Report Template per Job in a Suite
Copy TestShell Studio modules into CloudShell Authoring
Set of quali components informations published on cloudshell portal
Cloudshell Portal should consider Teardown time as time remaining instead of end time
Expanding the upper limit of the number of characters in TextToReport