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 (#4866) · Nov 21, 2019 at 11:22 AM · testshellstudiotooloutput
In REST Client tool of TestShell Studio, when sending a request and the response is for example 200, the output is retrieved and then we can assert on it, but when the response is let’s say 4xx or 5xx, there is nothing displayed in the output so we cannot assert on it. In some cases, we are already expecting 4xx or 5xx response.
Hence, our suggestion is that results get piped through to the “Output” even in case of an Error.
Muli Wienrib commented · Nov 25, 2019 at 09:14 AM
Hi Mohamed,
This is a good suggestion that will improve testing and monitor capabilities when using APIs
We will consider adding it
Thanks!
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
Automatically refactor tests if a library has been renamed or moved
Add “Failure Handling” feature
Run part of a TestShell test on another machine
Restrict "possible values" of a published variable in a test script
GetReservationDetails does not return sandbox conflicts
Full Report Search added to Job Scheduling section of the portal
Addition of "Invoke" & "WaitFor" Action in TestShell GUI Automator