We have segregated the entire Tosca tutorial in to below articles. We have wrote this article(TOSCA Tutorial) in simple language and keep the article short with the required concepts only so that any entry level software tester can understand this article in a shorter span of time.
In this article Tricentis Tosca Setup, we will discuss about step by step procedure to Install Tosca, uninstall and license configuration. If you want to prepare for TOSCA Interview Questions, please click here.
Click on the “Request a Demo” button available in right top corener of the website available in section Tricenties Tosca.
Tosca Setup Download 1
Enter the details in the form and click on “Request Demo” button to submit.
Tosca Setup Download 2
Once the form has been submitted, Tricenties support team will contact you for the demo and understand the expectations. After that you will be able to request for trial version of tosca through email/ telephone.
Download for registered user:
Open the tricentis support portal and download the latest tosca version in your local drive. In this article, we will work with TOSCA 13.2 Patch Level 3.
Step#1: Click on Installation Setup file from local directory.
Step#2: Accept License agreement and Continue.
Install Tosca Setup 1
Step#3: After auto verification of prerequisites, click on Next to proceed.
Install Tosca Setup 2
Step#4: Select Tosca Commander option for standard installation. But you can customize or installation based on the requirements. After the selection click on Next to proceed.
Install Tosca Setup 3
Step#5: Change Installation paths if required and Next.
Install Tosca Setup 4
Step#6: Please select the checkbox if you want to send the usage statistics to Tricentis. Click on Next.
Install Tosca Setup 5
Step#7: Review and click on Install.
Install Tosca Setup 6
Step#8: Accept if any popups and wait for installation to be completed.
Install Tosca Setup 7
Step#9: Once done, please click on Finish to complete installation.
Install Tosca Setup 8
Step#10: Open TOSCA Commander from start menu to verify installation.
Install Tosca Setup 9
Uninstall TOSCA
During up-gradation of Tricentis Tosca it is strongly recommended to completely uninstall Tricentis Tosca and install latest version to avoid any unexpected errors.
Uninstall Process Steps:
Step#1: Navigate to Control Panel and Click on “Programmes and Features”:
Step#2: Select Tricenties Tosca and Click on Uninstall:
Tosca Setup Uninstallation
Step#3: Wait for process completion and restart the system.
Tricentis Tosca License Configuration
Step#1: Open the “Tosca License Configuration” wizard from the start menu.
Tricentis Tosca Setup License Configuration 1
Step#2: Based on the available licenses, please select the desire option. And click Ok. Here we are selecting second option i.e. “Connect to Self-Hosted License Server”.
Tricentis Tosca Setup License Configuration 2
Step#3: Enter the license server details and click on OK to complete the configuration. Default post should be 7070.
Tricentis Tosca Setup License Configuration 3
Step#4: License Configured successfully.
Tricentis Tosca Setup License Configuration 4
Step#5: For trial license, at step2, please select the first option and enter the user details which are created after registering in Tricentis portal.
Tricentis Tosca Setup License Configuration 5
Conclusion
In this article of Tricentis Tosca Tutorial, we have covered the setup of Tricentis TOSCA testing tool so that we can start with working with Tosca. Click here to understand more from Tricentis Support portal.
Please click to read the next article of TOSCA Tutorial – Complete Study of TOSCA Commander.
The list of articles on Tosca Tutorial are mentioned in the table of content which will be explain through out the entire Tutorial. All the the articles are written in simple languages with proper example which will help the entry level software tester to understand in short time.
In this article, we will start with TOSCA Overview. To get the flavors of Tosca interviews, you can check the most frequently asked interview questions with answers from here.
Tosca Overview
The purpose of this tutorial is to describe a complete and detailed overview of TOSCA as a test automation tool for beginners.
Concepts of Software Testing:
Software testing is an important step to assure the quality of software products. It ensures that the requirements are fullfilled as per the expectations. Testing can be done in the different phases of Software development life cycles. Those are –
Unit Testing – Done by software developer at the time of development.
Integration Testing – After developing the different components, each of the components need to be integrated to make an unique product. After the integration, the integration testing is required to verify that the entire setup (includes all the software components) is working fine as a single product.
System Testing – After the integration testing, the system testing is required to ensure the quality of the software.
User Acceptance Testing –
It is one type of black box testing. The business team (end user of the software product) is responsible to perform this testing to verify that all the requirements are fulfilled.
The Software or application testing can be performed manually or through some automated approach. There is multiple test automation tool is available in the marked to automate the testing process. In this article, we are going to explain the overview of TOSCA as a test automation tool.
What is Automation testing?
Today, the IT industry demands the quality and the efficacy with minimum human efforts to deliver any kind of IT services. Here, automation testing is playing a big role for testing services. Automation testing is a service to automate the testing process and scenarios to reduce the human efforts. In the automation vertical, the leading tools like QTP (UFT), RFT, and Selenium were consuming the major spaces. Now Tosca is giving tough competition to these tools.
Why Tosca?
Tosca is one of the market leading tool in the present days. It has the ability to perform functional and regression testing as well. The API testing which has n important role in AGILE process, can be done through TOSCA. Now a days, marked demands lesser testing efforts and lesser training span on the tool. In this aspect, Tosca is best suited tool as it supports the script less testing which will consume minimum time to learn. Tosca user can write efficient test cases with minimum skill set. Also, it generates a standard test reports for the management with out much customization.
Tosca Key Features:
Model-Based Testing Approach: This is the main features of Tosca as a test automation tool. Due to this Tosca is more suitable than other test automation tools which are available in the market. As a part of test case development, we have to create modules for each of the unit level functionalities. All the technical properties of test objects are stored in the modules which will be merged during the test creation along with test data.
Risk-Based Testing Approach: The another important aspect of Tosca as it supports the risk-based testing approach. Tosca is capable of assess the risk with the test cases. Basically, it can identify the subset of entire test suite which will minimize the chances of risks. Once the execution is completed, risks are measured by considering the test execution result and the risk coverage.
Script less test cases: Tosca supports script less automation which means that test cases can be developed by drag and drop method of modules in the TestCase section of Tosca. The test data parametrization and implementations of checkpoints, can be done through the configuration. So, anyone will be able to develop tests with minimum skillset and training.
Dynamic test data: The dynamic test data can be kept separately from the technical testcases. To achieve this, Tosca provides advance features such as, TDM, TCD, TDS etc.
Easy to maintain: If there is an application or data enhancement, same can be incorporated in the entire test suite by updating the modules or data in the central repository. The efforts spent here, is lesser with compare to any of the other test automation tools.
Distribute Execution: It signifies about the distribution of test execution in multiple system to reduce the human efforts and execution cycle. Based on the configuration of distributed execution, we can schedule the test execution in multiple systems.
API Testing: API testing is very useful when the entire application is not ready but some of the application components are developed. Using the API, Tosca is able to test the corresponding application components.
Test Recording: Tosca is able to record test scenario to generates linear test cases along with checkpoints to save time. This feature is very useful for one time testing only.
Detailed Reporting: Tosca generates step by step execution reports and logs with captured screens. The execution logs are very useful while investigating any errors.
Mobile Testing: Tosca supports the testing of mobile apps in both android and iOS devices. For iOS testing, additional MAC infrastructure is required.
Supported applications: Tosca is compatible with different types of applications such as Salesforce, SAP, Web, Powerbuilder, DotNet, Mainframe, Mobile devices, etc.
Integration with third-party tools: Tosca helps to integrate with third party tools with minimum customization such as Perfecto, Selenium, Azure, Jenkins etc.
TOSCA Architecture:
TOSCA is designed and developed by TRICENTIS Technology & Consulting GmbH (An Austrian Software Company based in Vienna). The test tool TOSCA have the below interfaces –
GUI – The Graphical User Interface
API – Application Programming Interface
CLI – Command Line Interface
Integrated Test Management
Architecture Diagram (Tosca Overview)
The latest version of TOSCA Commander which is available in the market is 13.3. The main components of Tosca are mentioned below –
Tosca Wizard
Tosca Commander
Tosca Executor
Test Repository
TOSCA Commander:
TOSCA commander is the core backbone of the tool to develop, manage, execute, and analysis of test scripts creation. Tosca Commander has the five sections which are used in most of the projects –
Module – All the Modules(keep the technical information of the test object) are stored in this section.
Testcase – The technical components of any test cases are kept in this section.
TestCaseDesign – This section is used to isolate the test data from the testcase in a well organized manner. The main intention of this section is not to touch the technical test cases to modify the test data.
Execution – This sections keeps the logs of test execution results in execution list. Basically, it is used to manage the test execution.
Requirements – All the requirements related information are stored in this section.
TOSCA Overview – Tosca Commander
A detailed study of different sections is available in the next article.
TOSCA Executor:
Tosca Executor is used to performing executing test cases that are developed in TOSCA. This is an alternative to test execution without opening the Tosca commander. We can navigate the Tosca executor through the windows start menu: Start-> All Programs-> Tricentis-> Tosca Executor.
To get more details on TestSet files, please click here.
Tosca Overview – Tosca Executor
Tosca wizard:
We need to scan the application to create modules (object map) for test automation. Tosca wizard is the old model of application scans. It can be open as a standalone component also from the Commander as well.
TOSCA Overview – Tosca Wizard
Test Repository:
Testcase can be stored in external shared repository/databases such as Oracle, SQLServer, SQL Lite, etc. Also, test data can be stored in an external repository in Tosca through different processes such as TDM – Test Data Management, TDS – Test Data Service. The test repository is required so that multiple testers can work at a time.
TOSCA Overview – Tosca Repository
Tosca Supported platform:
Frameworks and programming languages: dotNet including WPF, Java, VB, Delphi.
Web browsers: Firefox, Internet Explorer, Chrome.
Application Development Environment: PowerBuilder.
Host Applications: 3270, 5250.
MS programs: MS Outlook, MS excel
Enterprise Application: Seibel, SAP.
Protocols and hardware: Flash, Webservices (SOAP),ODBC.
Conclusion
In this introductory article of Tosca overview, we have covered the overview of Tricentis TOSCA testing tool, Tosca Commander and Workspace. Please click here, to navigate to the Tosca support portal for more information.
We going to start with Selenium tutorialBlackbook in exhaustive and different approach , In this first segment of the Selenium tutorial, we will discuss aboutSelenium Webdriver Architecture, what is Selenium Webdriver , Selenium Webdriver overview, Brief History of Selenium,Advantages of Selenium,limitations of Selenium, Selenium components and some frequently asked questions .
What is Selenium Webdriver
Selenium is an open source technology or framework through which we can automate Web based Applications. Selenium Supports Multi browser Testing, Multiple languages like Java, Ruby, Perl, Python is also supported. It supports different multiple platforms like Windows, Linux, macOS etc. as part of the platform.
Brief History About Selenium :
Selenium was initially evolved from an internal tool by Jason Huggins in 2004 at ThoughtWorks.
Later in the year of 2007, Huggins joined the organization Google, and with others like Jennifer Bevan, he continued with the design and development of one of the initial variations of Selenium called Selenium RC. During a similar time period, another person named as Simon Stewart from ThoughtWorks developed an advance web browser automation tools as WebDriver.
In 2008, a person named as Philippe Hanrigou from ThoughtWorks came up with remote Automation concepts known as “Selenium Grid”.
In 2009, at Google Test Automation Conference, it was decided to merge the two projects, and given the name as Selenium WebDriver, or Selenium 2.0.
Advantages of Selenium Webdriver :
A. Open Source :
Selenium is an open source technology/framework, hence huge community support is available where the development and improvement scope is rapid and vast, also as its open source you can implement any specific feature that you require as part of your work and contribute to the Open source community.
B. Multi Programming Language supported :
Selenium is supported by widely used languages; it comes up with different programming language bindings, so you can choose your favourable language to work with selenium as per your need and expertise.
Selenium provides support for the below programming languages :
Java
C#
Perl
python
Ruby
Javascript
C. Platform independent :
Selenium is platform-independent, so you can automate your web applications over any platform and any of the Operating System i.e. Windows, Linux, macOS etc.
D. Cross Browser Testing capability
Selenium supports cross browser Testing capability for your web applications; you can run your test suite written with Selenium in multiple browsers such as Firefox, Chrome, IE, Safari etc.
E. Cross Device Testing capability
Selenium Test Automation is used for mobile web application testing automation on various devices such as Android, IOS.
F. Remote or cloud execution :
Selenium GRID provides you with the feature to run and control your web application’s automation test script in the cloud by making one system as the master node and other system as the slave node, slave nodes connect to one master node, and master node monitors the slave nodes, so your tests are in different slave nodes with the different operating system and different browsers such as Chrome, Firefox, Internet Explorer etc.
G. Parallel Testing capability:
With Selenium, you can achieve Automated Parallel testing capabilities, i.e. you can run your test script or automation Test cases into the different or same browser and different or same operating system in parallel. This feature helps you achieve lesser execution time for the whole Automation Test suite that you have, and also you can test your web application’s feasibility and compatibility with multiple operating system and multiple browsers in parallel.
H. Compatibility with multiple Framework and third-party tools and technology
Selenium framework can be easily integrated with multiple various third party technologies and frameworks such as different Unit Test framework, i.e. TestNg, JUnit, MbUnit, Nunit etc. etc., different build Tools such as Ant, Maven, Gradle etc., continuous integration tools, i.e. Jenkins, different Test management tools such Jira, testlink etc., various reporting tools such as Allure, Extent Report etc.
I. Headless Browser execution :
Selenium Webdriver supports headless browser driver for automated test case execution, where all your automation test cases run in headless browser mode, i.e. no browser gets opened and the execution becomes lightning fast so you can complete you Test scripts and the functionality quickly in case of urgent release and validations.
You can basically use htmlUnitdriver or ghost driver for the headless execution with Selenium.
Disadvantages of Selenium :
Native/Window based App Support, not present :
Selenium is used for Automating Web Bade application, but it does not provide support for native applications or windows based applications.
Exhaustive Image-based Automation:
Selenium does not provide exhaustive support for automating image-based problems or applications, though we can use some third-party tools such as Sikuli, tesseract ocr based solutions which can be integrated with Selenium to do the job related to the Image validations/operations or image data extractions and validations, they are also having some limitations like you may face issues with Parallel testing, identifying handwritten document and validating those in the process of automating your application if there are such use cases.
Integration with third-party tools :
One downside of the integration with multiple third-party tools with selenium is that your automation script might become slower at times.
Designing and developing an advance Test Automation framework with Selenium requires a lot of expertise on selenium and its not too straight forward to build an Automation framework with multiple tools along with Selenium.
Browser Specific issues:
You may face some browser-specific issues while working with Selenium, especially with IE, sometimes you may not be able to handle Web actions like click, sendkeys etc., and the browser may become dead. Hence you need to have advance knowledge to handle those areas while automating Application built on Bootstrap JS and executing it on IE browser.
Also, you might face browser compatibility issues with the Selenium Webdriver versions; you need to make sure you are using the compatible Firefox, Chrome or any other browser you are working with Selenium Webdriver’s version.
No official support :
Like any other Open Source tools selenium is also an open-source tool, which means you will not have official support for your problems like any Paid Tools, even though there is very large community support available, you can work with them with you problem statement, but that can be heavily time-consuming.
Selenium Components :
Selenium as a tool has the below-mentioned components, which are :
Selenium IDE :
Selenium IDE or Selenium Integrated Development environment is the most initial version of Selenium for Web Application Automation.
Selenium IDE is a kind of record and playback tool, which you can use as a plugin of the browser and record you web action your you applications and that can be saved as a script and later you can run the same recorded script to execute and do validations.
But it has few limitations such as :
You need to run the recorded script, modifying the script is not that flexible or neither you can deign you use case and scripts in you own independent approach.
Execution is very slow in nature.
Majorly supports Firefox, though there are some tweaks you can do to run the recorded script in other browsers such as Google Chrome.
parallel execution is not supported.
Mobile testing is not supported.
Report generation is quite not good.
Its actually very preliminary version of Selenium, by using this you can do very limited Test Automation for your Web Applications.
Selenium RC
Selenium Remote Control is the next version of Selenium and very often its referred to as Selenium 1.0.
How Selenium RC works internally :
Selenium RC consists of two major components, such as Selenium Server, Selenium Client.
The Selenium Server launches the browsers and runs the selenium commands that you have written as a test automation script by using Selenium client libraries available in different languages.
Selenium Server converts the commands/test scripts into something called Selenese commands, and it acts as an HTTP proxy.
Selenium Server interacts with Web Browser engine and performs the Web operation that you are trying to Automate as part of Test cases for the Application Under the Test.
Steps to use Selenium RC :
Install the Selenium-RC Server.
Create a project using your choice of programming language and language specific to the browser driver.
Install selenium server
You can set up Selenium Server by simply just download the selenium-server.jar file and run it in your system by using the below command :
java -jar selenium-server.jar
Write the Script by using Selenium client libraries and the same using the Selenium Server.
Limitations of Selenium RC :
In Selenium Remote control, automation driver and browser becomes a bit slower reason being browser engine is not directly interacted, rather Selenium RC injects javascript to the browser engine, it also referred to as Selenium Core.
The Server which has to be up and running before and during the test script execution.
Advance Web actions can not be automated and handled using Selenium RC such as mouse Movement, double click, taking input from Keyboard etc. etc. unlike Selenium Webdriver.
Selenium RC does not support Mobile app testing.
Selenium RC is dependent on the real browser to run the Automation testing script, and it does not support the headless browser such as HTMLUnitDriver or GHostDriver etc. unlike Selenium Webdriver.
Selenium WebDriver:
Selenium Webdriver is the advance version among the Selenium components which is very robust and also supports the advance version of Web interactions and also it does not interact with Browser via Javascript unlike Selenium RC and has the Mobile Application testing support as well. It’s very often referred to as part of Selenium 2.0.
WebDriver can handle dynamic elements and also supports parallel execution with multiple different browsers.
We will have a detailed discussion in the upcoming segments.
Selenium GRID :
Selenium GRID is another component of Selenium through which you can have the remote execution of your automation testing script by creating master-slave nodes. Selenium GRID supports parallel Testing on the same browser as well as multiple browsers.
We will have further discussion on Selenium GRID in the upcoming sections.
WebDriver 3.0
Selenium 3.0 is the latest version of Selenium components which is basically the combination of WebDriver 2.0 and evolution of GRID 3.
In this next segment, we are about to discuss the Selenium WebDriver Architecture in detail, and eventually, it depicts how Selenium works internally,.
Selenium Webdriver Architecture :
There five major attributes or components as part of Selenium Webdriver architecture :
Selenium Client Library or Selenium-Programming language bindings
WebDriver protocol or JSON Wire Protocol over HTTP
Browser’s Drivers
Browsers Engine
Browser’s rendering Engine
Selenium Tutorial-Selenium Webdriver architecture
Selenium Client Libraries or Programming Language Bindings:
Selenium provides different language binding, i.e. the client libraries to support multiple different languages as part of your Automation Development and Automation test script. For example, Selenium with C#, Selenium with Java, Selenium with Python etc.
WebDriver Protocol or JSON WIRE PROTOCOL :
JSON which basically stands for JavaScript Object Notation. This protocol is also referred to as WebDriver protocol, used for server-client data transfer over the web. Each Browser Driver (e.g. FirefoxDriver, ChromeDriver etc.) has its own HTTP server and uses this protocol to transfer data via Rest Webservices in the form of the HTTP request and HTTP response.
Browser Drivers:
Each browser has its own browser driver. The Browser drivers establish communication with the respective browser via browser engine.
When the Automation script gets executed, it directly communicates to browser drivers and eventually with the respective browser. The request and response are transferred via HTTP request and HTTP response.
Browsers Engine :
Every Browser has its own browser engine; The browser engine basically works as an intermediary layer between UI and the rendering engine.
Browser Rendering engine :
The Browser rendering engine is responsible for displaying the requested document by rendering the specific elements required for the request-response and data.
Selenium Webdriver Architecture and working functionality in a nutshell :
Selenium-WebDriver invokes the browser directly using each browser’s native support for automation and its JavaScript engine. How these calls are being made and the features that they support depend on the browser you are using.
It does not inject JavaScript like Selenium-RC when the browser loads.
The following incidence occurs while running the Webdriver script:
We do the automation scripting using any language binding (Java / C # etc.), and it triggers the WebDriver API while the script is in execution.
The script and eventually commands (eg driver.findElement (By.id (“idName”))) are being converted to JavaScript internally.
Using Browser Engine, it is again converted back to JSON, which is kind of a key-value pair.
After getting the respective value of the respective key, it identifies the respective WebElements and performs the respective user actions (like click, send keys, etc.).
All communication is done using a JSON-Wire or Webdriver Protocol call, and the communications happen over HTTP in the form of Rest API as an HTTP request and HTTP response.
Selenium frequently asked Questions :
What are the types of WebDriver APIs available in Selenium?
Selenium Webdriver is an interface and has different language bindings for different programming languages such as Java, C#, python etc.,
Selenium Webdriver is majorly having two different variants such as :
Selenium Web driver local.
Selenium Web driver Remote.
The Selenium Web driver Local uses the API to work with the specific language binding, and you can work with these with you local execution, while on the other hand if you want to execute you automation testing scripts in Remote, then you need to use the remote Selenium Web driver APIs.
Explain What are the scenarios we cannot automate using Selenium?
Selenium does not provide a way to Automate the below areas of aspects of the application, which are :
For Selenium 2.0 minimum requirement is Java 1.7, on the other hand for Selenium 3.0, the minimum required Java version is 1.8
Selenium 3.0 requires GeckOdriver for Firefox version above 47, but this is not the case for Selenium 2.0
Selenium 3.0 supports modern browser such as Edge, Safari etc. but on the other hand for Selenium 2.0, browser driver for Mozilla, Chromedriver, IE which is developed by Selenium developers.
In Selenium 3, the support for mobile automation testing got removed, i.e. AndroidDriver and iPhoneDriver, and you have to use tools like Appium for mobile automation testing, which is not the case for Selenium 2.0.
Selenium 3.0 doesn’t support the Headless driver, i.e. HTMLUnitWebDriver, but Selenium 2.0 has the support for Headless execution, i.e. with HTMLUnitDriver or ghostdriver.
Within Selenium 3, the Selenium WebDriver has become W3C standard; on the other hand, Selenium Webdriver in Selenium 2.0 does not belong to W3C standard.
Conclusion : With this we complete the first segment of Selenium tutorial blackbook covering What is Selenium , Selenium Webdriver Architecture,Selenium overview, Pros and cons of Selenium, In the upcoming segment of Selenium tutorial module 2 we will be discussing about Selenium Installation ie setup , Selenium commands and other basic,intermediate and advance topics of Selenium
Using Appium Inspector, we will learn how to inspect element android and how to inspect element on the iPhone in this Appium tutorial. Appium provides the capability to inspect elements both in android and iOS.
How to inspect element on iPhone using Appium inspector
Step 1 →Opening iOS simulator
In this tutorial, for all the examples we have covered with the iOS simulator. To open the iOS simulator, follow the below process:
Step 2 →Getting “udid.”
To connect the Appium inspector with the Simulator, we need udid. To get the
booted udid, please run below command
xcrun simctl list | egrep ‘(Booted)’
it will list down the device id and name of the Simulator booted up recently
Step 3→ Getting OS version
Now we need the OS version of the Simulator. To get the OS version, please run the below command
instruments -s devices |grep “iPhone SE” [please replace the device name with the device name you got from above command]
Step 4→ Opening Appium Inspector
Now we have the device id and os version with us. Please click on the button highlighted in the below image. It will open the New Inspector.
Click on search
Step 5→ Connecting Appium inspector with Simulator
Now add all the desired capabilities required to start the session. Please follow the below image for the required desired capabilities and start the session.
If you want to verify with a specific app, you can add an app path. In this tutorial, W have worked with the existing “Contact” app in the Simulator.
Add desiredCapabilities
Start the session
Step 6→ Getting the default screen.
Once the session is started, you can see the Simulator’s home screen image and the XML hierarchy. Please look at the below image for more details.
Appium inspector
Step 7→Inspect and clicking on the contact.
Now click on the Simulator’s contact button to reflect the inspector’s screen and click on refresh. Alternatively, you can find the Xpath of the contact and click on Tap. Please see the image below.
How to inspect element on iPhone
Step 8→ How to start recording?
After clicking on Contacts, we will see the image below. Now click on “Start recording” to capture all the actions. It will help to generate the Appium scripts in the desired language.
Start recording
Step 9→Inspect the element and clicking on tap.
Please follow the highlighted portion in the below image. First, find the XPath of the “Add” button, and after that, click on the Tap button.
Perform actions from inspector
Step 10→Sending keys.
After tapping on the Add button below screen will appear. Please follow the highlighted part to send the value from the Appium Inspector itself.
Use sendKeys
Step 11→Typing hello.
Please write any value to update the “First Name” value and click on “Send keys.”
Type hello
Step 12→Value reflected in both the app.
The value will be reflected in both places, like in the image below. Appium inspector
as well as Simulator
value reflected in both app
Step 13→generating code.
Now click on the link shown below in the image. It will generate Automation scripts in the preferred language. Here language has been selected as Python. You can view this in the below image.
click to generate the code
Step 14→Sample code.
Below are the sample scripts generated by the Appium inspector. Here language has been selected as Java-Junit.
import io.appium.java_client.MobileElement;
import io.appium.java_client.ios.IOSDriver;
import junit.framework.TestCase;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import java.net.MalformedURLException;
import java.net.URL;
import org.openqa.selenium.
remote.DesiredCapabilities;
public class SampleTest {
private IOSDriver driver;
@Before
public void setUp() throws MalformedURLException {
DesiredCapabilities desiredCapabilities = new DesiredCapabilities();
desiredCapabilities
.setCapability("platformName", "iOS");
desiredCapabilities
.setCapability("platformVersion", "13.6");
desiredCapabilities
.setCapability("deviceName", "iPhone SE");
desiredCapabilities
.setCapability("automationName", "XCUITest");
desiredCapabilities
.setCapability("udid", "B5FDD9EB-05C6-4F3B-9DFE-1A4EC3E06A7F");
URL remoteUrl = new URL("http://localhost:4723/wd/hub");
driver = new IOSDriver(remoteUrl, desiredCapabilities);
}
@Test
public void sampleTest() {
MobileElement el1 = (MobileElement) driver
.findElementByAccessibilityId
("Contacts");
el1.click();
MobileElement el2 = (MobileElement) driver
.findElementByAccessibilityId("Add");
el2.click();
MobileElement el3 = (MobileElement) driver
.findElementByAccessibilityId("First name");
el3.sendKeys("Hello");
}
@After
public void tearDown() {
driver.quit();
}
}
Issues faced opening the Appium Inspector in Mac.
How will you solve issues like “Encountered internal error running the command: Error: Unknown device or simulator UDID?”
You need to install "libimobiledevice."
Please use command → brew install libimobiledevice --HEAD.
How will you solve it if you get “WebDriverAgent because of xcodebuild failure: not found: carthage” issue?
You need to install the carthage
Please use command→ brew install carthage.
How to inspect element on android using Appium inspector
Step 1 → Opening emulator
In this tutorial, for all the examples we have covered with the Android emulator. To open the Android emulator, follow the below mentioned process:
Step 2→ Opening the Appium inspector.
Now we have the device id and os version with us. Please click on the button highlighted in the below image. It will open the New Inspector.
Opening Appium inspector
Step 3→ Connecting Appium inspector with Simulator
Now add all the desired capabilities required to start the session. Please follow the below image for the required desired capabilities and start the session. If you want to verify with a specific app, you can add an app path. In this tutorial, we have worked with the existing “Contact” app in the emulator.
Adding desiredCapabilities
Step 4→ Opening home screen
Once the session is started, you can see the emulator’s home screen image and the XML hierarchy. Please refer to the below image for details.
Opening Home screen
Step 5→Inspect element and start recording.
Now click on the contact button from the emulator. Please see the below image for more details.
how to inspect element on android
Step 6→Clicking add button
After clicking on Contacts, we will see the image below(Here we have chosen the favorite tab and refresh the page from the inspector). Now click on “Start recording” to capture all the actions. It will help to generate the Appium scripts in the desired language. Please click on the tap button highlighted below.
Perform actions
Step 7→ Clicking on send keys.
After tapping on the Add button below screen will appear. Please follow the highlighted part to send the value from the Appium inspector itself.
click on sendKeys
Step 8→Typing Hello
Please write any value to update the “First Name” value and click on “Send keys.”
typing hello
Step 9→Generating code
The value will be reflected in the edit box, like in the image below. Appium inspector, as well as an emulator. To generate the code, click on the highlighted arrow.
Till now, we have discussed how to inspect element android and how to inspect element on iPhone. In the next topic, we will write about how to write the first script in Appium. To start the subject from the beginning, pleaseclick here. For more details for this section, please refer to this link.
We will discuss how to use Appium methods in this Appium tutorial. Appium is a wrapper on top of Selenium webDriver. All the Selenium methods are already present in Appium. Apart from that, Appium provides a good number of ways to interact with native applications.
How to use the pressKey code using Appium methods?
public void pressKeyCode(AndroidKey code) {
\tandroidDriver.pressKey(new KeyEvent(code));
\t }
Here you can pass keyEvent like AndroidKey.ENTER to enter or AndroidKey.BACK to tap
on
back button Similarly, users can use this for long key presses like:
public void longPressKeyCode(AndroidKey code) {
\tandroidDriver.longPressKey(new KeyEvent(code));
\t}
How to get the current activity using Appium commands?
To get the current activity, we can use the current Activity method.
For Example:
public String currentActivity() {
\treturn androidDriver.currentActivity();
\t }
How to check if the app is installed or not?
To check if the app is installed or not we can use:
public boolean isAppInstalled(String bundleId) {
return androidDriver
.isAppInstalled(bundleId);
}
How to start activity in Android using Appium methods?
Please follow the below method to start the activity:
public void startActivity(String packageName, String activity) {
try {
androidDriver.startActivity(new Activity(packageName, activity));
} catch (Exception e) {
\t e.printStackTrace();
}
How to scroll to a particular text using Appium methods?
public MobileElement scrollTo(String text) {
MobileElement textFinder = androidDriver
.findElementByAndroidUIAutomator
("new UiScrollable(new UiSelector()"
+ ".resourceId(\\"android:id/list\\"))
.scrollIntoView("
+ "new UiSelector().text(\\"" + text + "\\"));");
\t return textFinder;
}
How to hide the keyboard using Appium methods?
public void hideKeyboard() {
try {
androidDriver.hideKeyboard();
} catch (Exception e) {
LoggerUtils.error("Exception in hiding keyboard" + e.getMessage());
}
How to get progress dialog using Appium methods?
public MobileElement getProgressDialog() {
return androidDriver
.findElementById
("android:id/progress");
}
Till now, We have discussed about the top 20 most used Appium methods. In the next topic, We will write about the Appium Inspector for Android and iOS. For more details for this section, please refer to this link.
We have written this Appium tutorial to give a complete picture of Appium mobile automation. We will discuss all the major topics here.
Introduction
It is an open-source tool. It supports Android, iOS, windows OS. We can execute same code in different os versions like Android, iOS.It reduces redundant code and helps to increase code reusability. It has implemented the Selenium webDriver, which connects through Apple’s XCUITest(iOS 9.3 and above) or UIAutomation(iOS 9.3 and lower) or UiAutomator/UiAutomator2 (Android) or WinAppDriver(Windows) dependent on the type of devices.
We will cover the below topics in this Appiumtutorial:
Advantages of Appium
Disadvantages of Appium
Types of Mobile applications
There are three types of applications supported :
Native Application
Native applications are written using Windows, Android, iOS SDKs.
Hybrid Application
Hybrid applications are a mix of web and native applications. Here native applications have control, and it interacts with mobile web applications.
Mobile Application
Mobile web applications are web-based applications. These are accessible using chrome(Android), Safari(iOS) browser. We can develop this type of application by HTML, CSS, JavaScript, AngularJS.
Appium Architecture :
How It works on the iOS platform
How It works on the Android platform
Prerequisite for setup
Appium tutorial for installing Appium Desktop on Windows
Please go to http://appium.io/, and you will see the below screen. Please click on the below-highlighted button.
Please click on the download button
Once you have clicked the above button, you will see the below page. Please click on the highlighted .exe file or .zip file to get it downloaded in your system.
Please Download the .zip or exe file
Here We have taken the .zip file to install it. Please unzip the file. After that, you will see the image below. Please click on Appium.exe.
Unzip the file
Now you can see the image below, and you are ready to start your server.
Please start the server
Now you can see the image below, and your server is ready.
Server has started
Appium tutorial for installing Appium Desktop on Mac
Please go to http://appium.io/, and you will see the below screen. Please click on the highlighted button shown below.
Please click on download button
Once you have clicked the above button, you will see the below page. Please click on the highlighted dmg file to get it downloaded in your system.
Please download the dmg file
Please click on the dmg file, which got downloaded recently, and you will see the below screen. Please the instruction mentioned in the below image.
Please drag to Application folder
It will start copying in the Application folder.
Copying started
Suppose you have already installed another version in your system. You will get below pop up. It is your choice to keep both or replace the older one.
You cab keep both or replace one
Once it is installed in your system, you can go to the launchpad and search with Appium, and you will get below icon and click on the icon. Alternatively, you can go to the Application folder and click on the icon.
Please search for the icon
Many times after launching it, you can get below error messages. No need to worry; we can solve this issue.
Security error
To solve the above issue, you have to go to system preference from the apple icon shown on the top left corner and then click on Security and privacy. You will see the screen below. Please click on “Open Anyway.”
Please go to privacy settings, and click on Open Anyway
Now click on the icon once again and this time, choose to open it. Please follow the below image.
Please Click on Open
Now you can see the image below, and you are ready to start your server.
Please start the server
Please click on the start server to start the server. Your screen will look like below.
Server Started
conclusion
Till now We have covered the basics of Appium mobile testing in this Appium Tutorial. In the next topic, We will write about top 20 most used methods to automate native application. For more details on this topic, please refer to this link.
Integer quis nisl at orci feugiat lobortis quis a odio. Etiam efficitur metus ultricies nisl lacinia malesuada. Mauris ante eros, convallis vitae eros ut, congue placerat ante. Etiam metus massa, volutpat sit amet sapien ut, condimentum ultricies dui. In mauris metus, semper eu consequat eget, porttitor sed dui. Nam eu hendrerit nibh. Mauris vulputate lectus … Read more
UiPath is the agent for the main computerized method for automation technology. It helps in building the product is ready to deliver , which will assist in a union like computerize job.
2. Discuss a few reliable RPA tools?
There are primarily three admired RPA tools which are mentioned below:
Blue Prism:
Blue Prism tool recommended business performance to be agile and low cost by automating rule-based, monotonous back-office process.
Automation Anywhere:
Automation Anywhere provides robust and user-friendly RPA tools to automate jobs of any difficulty.
UiPath:
UiPath is a Windows desktop tool applicable for automation for many types of web and desktop-based applications.
3. Tell me the activities which you have used in Pdf Automation?
Primarily used activities are Read pdf text, Read pdf with OCR & Get text.
4.Tell me the process of filtering the mail using Uipath?
There are two process for filtering the E-mails.
It can be strained using “if condition” in “for each” loop.
Users can provide filter conditions in the get Outlook filter choice.
5. Provide the steps to install Google Chrome Extension for UiPath Studio?
Below are the steps to install Google Chrome Extension for UiPath Studio:
Go to Setup ribbon tab, from the “Setup Extensions” menu, Choose Chrome. The Chrome Web Store is initiated in Google Chrome.
Setup Extension1
Click the “Add to Chrome” A verification dialogue box will have appeared.
Select the “Add extension” The extension will be installed.
Setup Extension2
Remark: Usually by default extension is kept off.
6. What do you understand by PDF Automation?
Pdf Automation is a special type of automation where the user can retrieve all the information from a pdf file.
7. What are the different type of navigation of Orchestrator?
There are more than eight types of navigation in Orchestrator alike Robot, Schedule, asset, Queue, Machine and process.
8. Tell me the method to schedule a process through Orchestrator?
There is a scheduler choice in Orchestrator options using that user can schedule the process.
9. What is Reframe work?
Reframe work is solely based on state machine and Entirely flow is State Machine. There are three states & one final states.
There are subprocess, sub modules& mini processes.
User can divide the process into different smaller projects.
10. What is the process for deploying UiPath tool?
1. Finish the installation of UiPath Studio on the desired system on which user want to automate processes.
2. Publish the scheme, except if user needs to use the existing procedure.
3. Build an Environment.
4. Create a release of the rule on the same environment.
5. Start the job
11. Tell me the process to activate UiPath Studio license?
To activate the UiPath Studio license, the user must keep the system Online. Steps are mentioned below.
Click the “Activate License”, the license window will appear.
Please provide an email id and continue to next step.
Provide the license key.
Select “Automatic activation.”
Select the “Activate”, UiPath license is now activated in the user’s system, and the user can begin building automation workflows.
License Activation
12. What is the invoking process of a UiPath workflow?
Workflows are short pieces of standard automation that are recyclable and applicable in many synopses. They are used to automate similar methods. Users can also merge two workflows to make combined automation.
13. How would you deploy UiPath?
Install UiPath Studio on the computer on which the user wants to automate processes.
Publish the process, omitting if user simply wants to make use of their existing process.
Develop an Environment.
On that Environment, make a release process.
Start job.
14. Discuss all the different status of a Robot.
Available: The Robot is not running a process and is available to be used.
Busy: The Robot is executing a process.
Disconnected: Communication has been lost or disconnected for more than 2 minutes between the Robot and Orchestrator.
4. Unresponsive: The UiPath Robot service is not working.
15. Tell me the process to allocate the load between different bots?
If you are engaging with reframe job queue functionality & if you desire to share the pressure among different workflow, then you can build two frameworks, first one is dispatcher which object is to upload data on Queue and the second one is a performer for receive the data from Queue.
16. Give a brief of UiPath tool components?
Components of UiPath tool mentioned below
UiPath studio: It is a tool; the user can create and develop their own Project using the diagrams and visually.
UiPath Robot: Usually named as a bot, using the bot user can run Project in various computers.
UiPath Orchestrator: Its an application, using this application user can deploy their Projects and use it in any place.
It’s used for Project optimization; the user can deploy, schedule, monitor the execution and extract report and update respective Team.
17. What do you mean by an argument in UiPath tool?
An argument is required to pass the data into one project to another.
18. Tell me project creation steps and the execution process.
Steps for creating the Project creation steps mentioned below:
Launch the UiPath Studio and start.
Create a new Project using below steps:
New
Simple process.
Agent Process Implementation.
Follow the ordered sequence for Transaction.
Use a new tab, Provide the name and required path and also mentioned details after creating the project.
Depends on the project design window will open.
Drag and drop the schemas into the design window
Now you can execute the project clicking the RUN button else you can press F5 button from your keyboard.
19. Clarify these two terms “Delay Before” and “Delay after”
Delay Before:
Before the operation executes it wait for the designated time and then it will perform.
Delay After:
Once the operation is executed, it waits for the designated time and performs the next process.
The delay Time should be only on milliseconds like 5000.
20. Discuss the different types of Workflows in the UiPath tool?
Sequences: The sequence is really the small type of projects which are acceptable primarily for linear methods & will permit the user to swap from one activity to another without any trouble. It works as a single activity block. Users can reuse them several times.
Flowchart: It helps in enormous jobs as well as in short projects, and the user can also use them in various projects. Flowcharts assists in several dispencing dividing of logical operators assist in developing composite business and for attaching the ventures in multiple ways.
State Machine: while a machine is using a specific number of states for automation throughout the execution process, it is also familiar as the state machine. It will only shift from one state to another if any activity is triggered.
21. Why do we need “branching” in the UiPath tool?
When we want to connect the activities, we need the branching in the Flowchart.
22. Cloud you, please explain the “Partial Selectors”?
The selector information described in attach window or in the connected browser is the partial selectors.
23. Tell me some Wildcards in the UiPath tool?
There are two wildcards.
Asterisk (*): Replaces zero or more characters.
Question mark (?): Replaces a single character.
24. What are the dissimilarities between the Attended and Unattended bot in UiPath tool?
1. Attended Robot: Attended Robot is triggered by user events, and serves beside a human, on the same workstation. AttendedRobots are practiced with Orchestrator for a centralized method deployment and logging medium.
2. UnattendedRobot: UnattendedRobot Runs abandoned in virtual environments and can automate an uncountable number of processes. Apart from that, unattended Robot is capable of job scheduling remote execution, monitoring and providing support for work queues.
25. Describe Automatic Recording in UiPath tool?
Automatic recording is very helpful and efficient as it can supply the users with a framework for business processes and can be efficiently customized and parameterized.
26. What is the use of the output panel in the UiPath Tool?
The output panel helps the programmer to view the execution results.
27. What is the different process to create variables in UiPath?
User can create a variable in two ways:
From a variable window, using ctrl+k in the property window.
Click on the Variable Pane in the toolbar.
28. Tell me the use of an outline panel in UiPath?
The Outline panel displays variables, all nodes, and the project hierarchy.
29. What are the sections available in the UiPath tool?
There are six sections are available in UiPath
1) Projects Panel.
2) Activity Panel.
3) Workflow Designer/ Main Panel.
4) Property Panel.
5) Output Panel
6) Outline Panel
UiPath Panel
30. What is the responsibility of an Orchestration job?
The primary authority is to organize the implementation of different jobs.
31. what are the processed to filter mail using the UiPath tool?
Two methods are used to filter the emails:
Emails can be filtered using if condition in for each loop.
Users can also filter email by implementing a filter condition in the “Get outlook” filter selection.
32. What do you understand by “credential manager” in the UiPath tool?
The credential manager assists developers in automating the methods. It is used for designing, making, as well as deleting the
credential using committed tasks.
33. Discuss “sequence activities” in the UiPath tool?
The sequence is a kind of project which are acceptable mainly for linear methods and will permit users to traverse from one activity to another without any hassle. It basically works as a single activity block. Users can reuse them many times.
34. How to automate excel macro using the UiPath tool?
Automating the excel macro using UiPath is achieved by executing macro activity installed from the manage package window.
35. What are the properties in UiPath?
There are different activities applied to automate applications or web-applications, and the user can discover them in the Activities Panel, inside the UI Automation section.
All of these activities have various properties in common:
Delay after: Adds a pause after the action, in milliseconds.
Delay before: Adds a pause before the action in milliseconds.
TimeoutMS: Defines the measure of time (in milliseconds) to wait for a particular element to be found before any error is thrown. The default value is 30000 milliseconds.
WaitForReady: Before executing the actions, wait for the target to become ready.
36. Describe the process of publishing a project in the UiPath tool?
When a developer or Tester wishes to publish an automation project, that implies document the workflow and all the other packages to be transferred to Robots. After configuring the Robot with the required infrastructure, the project can be executed.
Publishing projects locally needs the user to provide a path on the local machine, different from where the scripting packages are published. There, the user can later manually send the packages to the Robots to be executed.
37. Tell me the process of storing credentials in the window and utilize by UiPath tool?
Users will take secure credential activity and fetch that user-id and Password in two variables and pass into a web application or automate whatever process.
38. Discuss the “Automatic Recording” feature in the UiPath tool?
Users should use row below command: (“ColumnName”).ToString.Equals(String.Empty). This command returns a Boolean value, which authenticates empty columns in Excel.
39. Difference between sequence and flow chart in UiPath?
Sequence:
The sequence is a kind of project which are acceptable mainly for linear methods and will permit users to traverse from one activity to another without any hassle. It basically works as a single activity block. Users can reuse them many times.
Flowchart:
The flowchart is normally used for general configuration purpose in UiPath. User can use these flow charts for different types of projects for all complexity and length. Flowcharts assists the functions in creating and isolating the logical operations, in creating the complex business models, and merge various sequences.
40. Brief us the dis-similarities between RPA and the chatbot?
There are many dis-similarities between RPA and the chatbot few are mentioned below .
RPA (Robotic process automation): RPA is a broader supposition and chatbot is a very small or sub-group of RPA topic. RPA is used to automate the cumbersome processes but chatbot cannot automate the same complex process.
Chatbot: A bot is a pre-organized tool which works like a human. These chatbots assist the guests to operate some planned actions. The good thing about chatbots is that bots educate themselves from previous experiences and act as per the situation.
41. Discuss the assets configure process in Orchestrator?
Step1: Login to Orchestrator.
Step2: Select the assets option from left menu panel.
Step3: Add asset.
Step4: Provide asset name and Select type of asset.
Step5: Please keep in mind, you must have to disable the Global Value.
Step6: Add Robot name (Select the robot name if it is already existing in your dropdown list). Step7: Provide the password and click on create.
UiPath interview questions and answers: asset creation
42. Describe thick client and thin client in UiPath?
A Thin client is an application where the user cannot get all assets that he/she required while using the RPA tool. Basically, a thin client is an automation involvement done on the browser. Example: Citrix.
Thick client: Thick client is an application where the user will obtain all the attributes that are needed for the RPA tool. Basically, Thick client involved in Desktop application automation. Example: SAP GUI.
43. What are the changes required while publishing a new package for Bot?
Step1: After publishing a new package, user need to update with latest package in Orchestrator package section.
Step2: Next user need to download the package in “UiPath Robot agent”
Step3: Finally, user need to download the latest package in version management.
Integer quis nisl at orci feugiat lobortis quis a odio. Etiam efficitur metus ultricies nisl lacinia malesuada. Mauris ante eros, convallis vitae eros ut, congue placerat ante. Etiam metus massa, volutpat sit amet sapien ut, condimentum ultricies dui. In mauris metus, semper eu consequat eget, porttitor sed dui. Nam eu hendrerit nibh. Mauris vulputate lectus … Read more
Integer quis nisl at orci feugiat lobortis quis a odio. Etiam efficitur metus ultricies nisl lacinia malesuada. Mauris ante eros, convallis vitae eros ut, congue placerat ante. Etiam metus massa, volutpat sit amet sapien ut, condimentum ultricies dui. In mauris metus, semper eu consequat eget, porttitor sed dui. Nam eu hendrerit nibh. Mauris vulputate lectus … Read more
