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.
VISIT OUR DIFFERENT FORUMS:
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 >.
Mohamed Hamdi suggested an idea (#4871) · Nov 21, 2019 at 11:40 AM · testshellstudiolibraries
Automatically refactor tests if a TestShell library has been renamed or moved without revisiting every test to refer to the new library name.
For example, if there is a library (tool) named "dummy1" in TestShell, it is used in a lot of tests, and we need to change its name to "dummy2" for example. If we do this now, all the created tests should be revisited to refer to the new library name because the old one doesn't exist anymore.
Our suggestion is if an admin is going to rename/move a library (TestShell Studio >> Admin >> Libraries), all tests get refactored to point to the new name/location. There is a similar feature but for tests not libraries, which is if a user rename/move a test, all the tests that is using it will get refactored to point to the new name/location.
Dan Michlin commented · Dec 11, 2019 at 12:16 PM
Hi @Mohamed Hamdi, thanks for the suggestion, it's not currently planned in our roadmap to change this behavior.
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.
Add a “SOAP Client” library to TestShell Studio
Run API requests through SSH using TestShell Studio
Support “application/x-www-form-urlencoded” content type on REST Client
Retrieve the output of a REST Client request if the response was 4xx or 5xx
Add “Failure Handling” feature
Run part of a TestShell test on another machine
Restrict "possible values" of a published variable in a test script
Beeing able to create Structure like C/C++ in TestShellStudio