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 >.
Praveen Kakarla suggested an idea (#528) · Aug 08, 2016 at 01:55 AM · scriptstestshell
Sometimes there are syntax errors in our TS scripts due to the function interface changing, or function moving, or some other reasons. But unless we open the scripts, we are NOT able to see the existance of such errors.
If we run from TS Studio there would be a window poping up -- The script contains error, are you going to continue? But if we run from RQM & Runner, the case would just fail without any more details. So in order to avoid such failure when running from RQM, it would be helpful that we can see which cases contain the syntax error on the Test cases view.
I know right know we need to run "Check" before we execute it from the RQM.
Actually this is not what we expect. We would like to have the option to choose whether to ignore, or fail immediately when there are errors in scripts
Maya Ber commented · Feb 08, 2017 at 08:59 AM
Hi, Thank you for the idea. Right now we don't have concrete plans to add such functionality to our RQM integration. If anyone would still like to see this happen, please vote.
Regards, Maya
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.
The CloudShell orchestration package needs to be in the script Python env by default
Run API requests through SSH using TestShell Studio
Ability to save and import the Reporting templates
User must be able to save 'Find usages' output in Studio
Changing default report template of Test Shell
Add Input Variables to Blueprint Scripts
Support “application/x-www-form-urlencoded” content type on REST Client
Ability to get a list of all function calls used in a test including the full path
Manage blueprint script visibility in domains
Additional fields required for Testshell method 'GetTopologyDetails '