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 >.
I'm automating a Web GUI portal (accessible from the Internet Browser) and XPATHs tracked by Ranorex Spy for each and every element contain the same hardcoded value of the IP address and the port number.
Examples of some XPATHs:
/dom[@domain='10.65.111.102:8080']//textarea[#'arid600000012']
/dom[@domain='10.65.111.102:8080']//div[#'FormContainer']//div[@innertext='View Work Order']
/dom[@domain='10.65.111.159:8080']//input[#'_ResidentialEndUserConnectionPortletWindow:_viewRoot:j_id1:applicationReference']
What would be your advice to avoid this hardcoded value in all XPATHs? I could introduce a variable, but it is not a desired solution because I'd need to include this variable in every GUI function I develop. So the best way would be to avoid the hardcoded bit.
I will appreciate your advice.
Hi Marcin,
Please see the attached image.
When you open the automation step you can edit the XPtah value:
In the Ptah text-box you can use custom variable - in this case {CustomTab} variable is a local variable.
Hi Aharon,
This is not what I asked about. I knew how to introduce a variable. My question was whether there is a way to avoid a variable.
Thanks,
Marcin
Marcin,
You can use the Ranorex repository - the repository will have the 'Base URL' & each step will have the page suffix.
Thefull pathwould be combination of theRepositoryand theRelative Path.
In order to create repository use 'Raorex Recorder' (not the spy) and import your record (include the repository).
Can you please confirm if my understanding is correct: Following your suggestion from your last post, way we end up hard-coding the repository with the 'Base URL' and the same test won't run in another instance of the environment. I wanted to avoid hard-coding and using a variable in the first place, please see the last paragraph in my original question.
Marcin
Working with local GUI repository should solve your problem.
Aharon
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.