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 >.
Summary: 6.0 is distributed with a custom execution server sample written in python and is available via the following path. The purpose of this article is to detail the steps needed to run scripts on a remote machine using the provided example.
\CloudShell 6.0 GA [6.0.0.10553]\CloudShell\Integration\Custom Execution Server Sample
Configure the Python execution server: (In this example we are configuring the server to run TCL scripts)
4. The "name" and "type" field values in the config.json file should match the "Name" and "Description" in the Execution Server.
Configure the Portal:
3. Click on “Add” button to define a "Name" and “Type”.
Start the execution server:
1. Open the command line to the “Custom Execution Server Sample” folder.
2. Register the server by executing “ces.py register”.
3. Run the execution server “ces.py” and leave the window open.
4. Upon executing the "ces.py" you should see the # of execution server to increase by the number that is set in the config.json file ("capacity" default is 5).
Scheduling a job:
2. Name the Test Suite and on the far right click on “+” to add a job, then click on “+” in the center of the screen to add a test.
3. The purpose of the "Name (or Executable)" field is to define the path to the script engine. Example: “C:\tcl\bin\tclsh.exe”.
4. The purpose of the "Arguments” is to define the location of the test script and any arguments. Example: “myTestSctipt.tcl Apple”.
5. Run the job immediately or as desired.
6. Note that the job should report passed but no report will be available as reporting is not available for this feature.
7. The dos execution server will display feedback about the script being run and will report an error in reference to reporting which can be ignored.
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.
GUI Automation - Identifying 'difficult' objects
Examples for Regular Expressions
Studio - assets appear with yellow x
Difference between Simple and Emulated Read Buffer
How to add link into test report
API File System doesn't work properly
How to generate random number and write its result to excel? (v. 4.8)
Creating a unified log when working with external devices / drivers