by admin | Nov 12, 2021 | Automation Testing, Blog, Latest Post |
Robot Framework is an open-source Python-based automation framework used for Robotic Process Automation (RPA) and also for Acceptance Testing & Acceptances Test-Driven Development (ATDD). It is used with the keyword-driven testing approach for which testers can write automation test scripts easily. The Test cases are written using the keyword style in a tabular format making them easy to understand. Robot Framework does provide good support for external libraries. But Selenium library is the most popular library used with Robot Framework for web development and UI testing. As a leading mobile app testing service provider, we have been using Robot Framework in our various Android and iOS app testing projects. So we have written this end-to-end Robot Framework Tutorial that covers everything one has to know.
The Basic requirements for robot framework
Since the Robot framework is built based on Python, we have to install the latest version of Python by downloading it from their official site. After successful installation, set up the Path environment variable in your local system.
Steps to Install Robot Framework:-
1. You can check if the Python setup has been installed properly by opening Command Prompt and typing the below command.
2. Use the below command to check the pip version. (Pip is a Python package manager)
3. Now we’re all set to install the Robot framework
a. For a straightforward installation of the robot framework, you can use the command
pip install robotframework
b. If there is a need to install the robot framework without any cache, you can use this code instead.
pip install --no-cache-dir robotframework
c. If for any reason, you want to uninstall the Robot framework, then you can do so by using the below code.
pip uninstall robotframework
4. Just like how we verified Java, we can use the below commands to check it using Command Prompt.
(i)
This command will show the details of the robot framework and the framework location.
(ii.)
Once we enter this command, the desired result that should be displayed is “No broken requirements found.” If any other message apart from this (i.e.) a warning is displayed, we need to check the warning related to the setup and install it properly.
We can also verify if the Robot Framework has also been installed properly in our Local system.
Go to the Python folder > Lib > site-packages > verify if Robot Framework is installed.
5. To verify the version of the installed Robot Framework, use this code
6. You might face a scenario where you would need to use a specific version of the Robot Framework, you can accomplish this by mentioning the specific version you need as shown below.
pip install robotframework==4.0.0 //mention the specific version
7. In time, you might want to upgrade the old version of the Robot Framework. You can use the below code to do it.
pip install --upgrade robotframework
8. In addition to verifying if the Robot Framework has been installed correctly, you might also have to check if the python libraries.
(i.)
This command will show all the python libraries installed with the robot framework version.
(ii.)
This command will show all the python libraries installed with their version numbers.
For writing automation test case:
In the Robot Framework Tutorial, we would be exploring how to perform web browser testing using Selenium Library. But for that to happen, we have to import the Selenium library file to this Robot project
Step 1: Enter the Command-Line to install Selenium
Step 2: To upgrade the pip installation with the Selenium library, enter the below-mentioned command
pip install --upgrade robotframework-seleniumlibrary
Step 3: Finally, you can check if the pip Robot framework Selenium library has been installed properly by using this command.
pip check robotframework-seleniumlibrary
IDE for the Robot framework:
We can conveniently use the following IDE’s to write the Robot Framework automation testing codes.
1. PyCharm
2. Eclipse with RED plugin
3. Visual Studio with one of the plugin
4. RIDE
In this Robot Framework Tutorial, we have used PyCharm with Selenium to write a website automation testing code.
PyCharm IDE Installation and a New Project Creation:-
Step 1: Go to https://www.jetbrains.com/pycharm/download/#section=windows
Step 2: Download the free Open-Source Community Version of the PyCharm .exe file.
Step 3: Once you run the .exe file of the PyCharm setup, you’ll see the ‘Install Location’ window. If you want to change the location from the default option, you can click on the “BROWSE” button, and select your own file setup location and click on the ‘Next’ button.
Step 4: In the 4th Window, select the 64-bit launcher and click the ‘NEXT’ button to move to the next window where you can directly click on the ‘INSTALL’ button to install all the files.
Step 5: Once the setup and jar files are properly installed and updated, tick the checkbox and finish by clicking on the “OK” button in the “Import Pycharm Settings” pop-up.
Step 6: Now, you will see the ‘Welcome to PyCharm’ window. Click on the “Create New Project” option and it will automatically generate a project fill location to set up the project. If you would like to change the location, then you may click on the file option to customize it as you please. Enter the “Project Name”, and click on the “CREATE” button.
Step 7: Finally the PyCharm Window will display with New Project.
In this Pycharm IDE, we are going to create a Robot framework for a website’s automation testing. So let’s explore how to generate a report and all the other essential actions in the upcoming topics of this Robot Framework Tutorial.
How to Create a New Robot Project and the required Setups:
In the Robot framework, we have to set up interpreters and add some plugins as well. Let see how to do those things now.
Step 1: You’ve already created the Initial Project for which you need to add the interpreters to work with the Selenium and Robot framework. So follow the below steps, and use the image as a reference if needed.
Go to File > Settings > Click on Project: “current project name” > Python Interpreter > + icon
Step 2: You need to install the following packages for this project
i. Selenium
ii. robotframework
iii. robotframework-seleniumlibrary
You have to enter these three keywords one by one in the search input field and search for the packages. Once you find them, you have to click on the “Install Package” button and wait for a while for the packages to install in the back end. Once it is successfully installed, the highlighted message will appear and you can close the window by clicking on the “OK” button in the settings window.
Note: Make sure to close the window only after installing the three packages one by one.
Step 3: Now, you have to add the “IntelliBot @SeleniumLibrary Patched” Plugin as it’ll help us find the Robot framework files and give auto suggestions for the keywords. So without this plugin, PyCharm will not be able to find the “.robot” files. The steps are as follows,
Settings > Plugin > Marketplace >Search “IntelliBot @SeleniumLibrary Patched” > Install
Once the Plugin has been installed, you have to restart the IDE for the initial configuration.
Step 4: Normally, the Project Structure contains multiple directories and each directory contains a similar kind of file. So in this Test project, we are going to create a test case inside the directory first.
Right-click Test Project > New > Directory > Enter the Directory Name
That directory will be created under the Test Project and so our Robot test cases can be created inside it.
Step 5: Create the “.robot” file under the created directory.
Right Click on Created Directory > New > File > Enter a File name that ends with “.robot”
Once the robot project has been created, the structure of the project will be how it’s shown in the following image.
Prerequisites to run Automation Test Cases in the Robot Framework:
Whenever you write automation test cases in the Robot framework, 4 sections should be there. They are
- Settings
- Variables
- Test Cases
- Keywords
Note:
- These 4 sections are must-know aspects from a beginner’s point of view.
- Each and every section starts with ‘***’ and is followed by the Name of the Section. It also ends with ‘***’.
- One (or) Two Tab spaces are needed in between the Keyword and the Test data (or) Data (or) input data because indentation is very important in Python.
- When you’re about to write a test case, you should first write the test case name and then go to the next line to write the keyword after leaving a tab space.
Step 1: Settings
You are going to import the Selenium Library in this Test case.
The first line indicates the code block and the second line uses the “Library” keyword to import the “SeleniumLibrary”.
Syntax:
***Settings***
Keyword LibraryName
Step 2: Write the Test Cases
Now, you have to write exact test cases as per your requirements. First, you have to assign a test case name, and then enter the test case information in the next line. You can write these test cases using free defined Selenium Keywords. Being a leading QA Company, we wanted our Robot Framework Tutorial to be a comprehensive guide even for beginners. That is why we’re going through everything from scratch.
Syntax:
***Test Cases***
TestCase_Name
Keyword Locators(or)data Testdata
In this Robot Framework Tutorial, we are going to perform the following test cases:-
1. Visit the Codoid Website.
2. Navigate to another page and verify it.
3. Pass the Input data.
The first step towards automation is launching your browser. Based on the browser you are using (Chrome, Firefox, etc.), you have to download the various drivers. Once you have downloaded the drivers, you have to extract the downloaded file and copy the driver.exe file path. We will be using Chrome for our demonstration.
Syntax for the Chrome launch:
***Test Cases***
TestCase_Name
Keyword driver_name executable_path= “driver_path”
There is also another method that can help us save some valuable time by reducing the time to launch the browser. You can,
1. Copy or Cut “various_driver.exe” file from your local.
2. Paste them under the Python/Scripts page under your local system as shown below.
After this step, we can directly launch the browser without pointing to the driver location in the framework. We have to write the following syntax instead of using the “Create webdriver” keyword to set up the path.
Direct browser launching syntax:
***Test Cases***
TestCase_Name
Keyword input_data (or) URL driver_name
Based on the requirements, we have to write the test steps under the test case name with the Selenium Library Keywords and respected Locators along with the test data.
In this example, will be performing the test case with limited Selenium Keywords in the robot framework. For more Selenium Library keywords please visit their website.
Step 3: Define the Variable
The variables are elements used to store values which can be referred to by other elements.
Syntax:
***Variables ***
${URL} url
@{UserCredentials} inputs
Defined variables can be replaced in test cases and we can even reuse them anywhere in the test case when needed.
Apart from this, we have a lot of variables available in Robot Framework. We have mentioned only the required ones here
Step 4: Define the KEYWORDS
Since the keywords are reusable in the Robot framework, it helps manage the changes in a faster and efficient manner. You can even create our own keywords here.
Syntax:
***Keywords***
Keyword_Name
Selenium_keyword locators input_data
Once you write your own keyword, you can replace the test case steps with the keywords.
Even once all of this is done, we won’t be able to run our project directly in the PyCharm Robot framework. We would have to go to the Terminal and use the below command
robot directory_name\file_name.robot
Once the project has been successfully executed, the output.html, the log.html, and the report.html files along with the screenshots for each test case will be automatically created in our project structure. So we can copy and paste it into any browser to check the report of the execution of our project.
Here we have executed all the test cases. But if you are looking to run a separate test case, you can do so by using Tags. You should include the tags with the name of your choice inside the test cases section under the test case name as shown in the below image.
You can either run one or a particular set of test cases by using this command in the Terminal.
For one particular Tag:
robot --include=Tag_name directory_name\file_name.robot
For Two Tags at a Time:
robot –i Tag_name -i Tag_name directory_name\file_name.robot
So using tags you will be able to get more concise reports as you can execute the test cases based on priorities. Refer to the following images to get a better understanding of what we mean.
Conclusion:
We hope you have found our end-to-end Robot framework tutorial to be useful as the Robot framework is an easy-to-understand open-source tool that provides a modular interface to build custom automation test cases based on your varying requirements. So it has been widely adopted by various large organizations for this very purpose, and for good reason.
by admin | Nov 8, 2021 | Software Testing, Blog, Latest Post |
Knowing each entity in depth is very important when it comes to testing banking applications that deal with corporate customers. Corporate Customers are the ones who are neither individuals nor micro-enterprises. With years of experience in providing the best software testing services to our clients, we are well-worse with everything a team will need to know about entities. So in this blog, we will be seeing an overview of entities on the whole as we will be learning what is an entity, exploring the Different Business Entities, and will also be covering how to test its intricacies.
What is an Entity?
An entity is a registered organization that processes and provides certain services to end consumers. It has its own goals & missions and a separate existence like humans. There are key representatives called the key principles of the organization who govern the entity. Now let’s take a look at the list of the different types of entities and explore them one by one.
The Different Business Entities:
- Public Limited Company
- Private Limited Company
- Partnership
- Sole proprietorship
- HUF
- Religious Establishment
- LLC
- Statutory Corporation
- Holding Company
- Trust
- Funds
- Non Profit Organizations
- Investment Vehicles
- State-Owned Entity
- Charitable Organizations
- Central Bank
- Sovereign Wealth Funds
- Clubs and Societies
Public Limited Company:
A public limited company offers shares of their stock to the general public by listing it on the stock exchange. The stakeholders are the owners of a PLC. It is referred to as PLC in the United Kingdom, as Inc in the United States, and as Ltd. In India. PLC requires a minimum number of 7 members, and there is no upper limit. It should also have at least 3 directors.
Private Limited Company:
A Private Limited Company can be listed in the stock exchange or need not be. Even if they hold shares, they cannot be sold to the general public. It requires a minimum of 2 members to start the company and it should have 2 or more directors. It is called LLC in the United States, PVT in the United Kingdom, and Pvt. Ltd in India.
Partnership:
A Partnership is a formal agreement between 2 or more parties to manage the business and share its profit or loss. Unlike Private Limited companies, partnership firms are not separate entities. A change in the partners leads to the formation of a new partnership firm while the old partnership firm would get dissolved. There should be a minimum of 2 partners, but the number should also not exceed 50.
Sole proprietorship:
When a company is owned and managed by a single owner, it is called a sole proprietorship. It is unincorporated by nature, meaning this company has no separate existence by itself. It is easy and inexpensive to establish when compared to the other entities as it has fewer regulations. The biggest challenge would be raising the required capital for the business from external sources. Small business owners mostly prefer sole proprietorships.
HUF
HUF is a family business that lends a way of saving taxes by clubbing the assets owned by the members of a family. Though it is an option available only in India, we wanted to be thorough in our proceedings. The senior-most member in the family will most probably be the head of their HUF. It is governed by Hindu Law. So the death of the senior member does not affect the existence of the business, the next senior-most male member becomes head.
Religious Establishment:
Temples, Churches, and Mosques are places of worship that can be termed as religious establishments. There are a lot of regulatory laws that help prevent the misuse of religious institutions as an unauthorized way of gaining money.
LLC (Limited Liability Company:
An LLC is a Legal Entity that helps its owners avoid personal responsibility for its debt and liabilities. LLCs do not pay tax as the profit or loss is passed to the owners who show it as their personal gain or loss. It is mostly incorporated, meaning the entity has a separate existence, unlike Sole Proprietary.
Statutory Corporation:
Statutory Corporations are companies owned by a government with the presence of other stakeholders. It is a cumbersome task to start such an entity as a lot of approvals are required. Once the policies governing this entity have been created, it is nearly impossible to change. So they are prone to wastage of capital & assets and inefficiency in operations compared to private establishments. It also suffers from political interference.
Holding Companies:
When multiple businesses are owned by a single person or by a group of people, they create a holding company which is called the ‘Parent Company’ to keep track of its subsidiaries. This holding company doesn’t usually perform any business activities, its primary purpose is to monitor the subsidiary businesses. So when the subsidiaries grow, their parent companies also grow in tandem. It receives dividends from its subsidiaries. The holding company either owns 100% of its subsidiary or at least 51% of its subsidiary to maintain control over it. This helps them to protect the interest of its subsidiary and helps to protect it from the creditors of the subsidiary to control the assets by investing less money.
Trust:
Trusts are owned by Banks or Financial Institutions and act as custodian for asset management, beneficial ownership registration, and so on. It acts on behalf of its client or beneficiary to make investment-related decisions.
Funds:
Funds are investment companies that focus on investing in securities. They employ portfolio managers to help manage the investment options offered by the firm.
Non Profit Organizations:
A non-profit organization can be a trust, a corporation, an association, a Limited Liability Company, or unincorporated. Since they are mainly created to serve a social cause, they will have tax exemption benefits.
To create a Non-Profit Organization, first, we have to decide if creating it as a non-profit is the right choice, create a mission statement, develop a business plan, build a board, and then file for the tax-exempt status.
Investment Vehicle:
An investment vehicle is a type of company that helps the investor grow their money by issuing bonds or investing in stocks or investing in real estate. Any mutual fund company that helps its investors diversify their portfolios is an example of an Investment Vehicle.
There is a special type of Investment Vehicle called the Special Purpose Vehicle (SPV). It is created by the parent company for the main purpose of undertaking some risky projects.
State-Owned Entity:
It is a company owned by the Government with the sole purpose of generating profits or helping the Government with certain activities that are vital to them.
Charitable Organizations:
It is a type of organization created with the sole purpose of aiding a social cause. It can be set up with the objective of safeguarding animals, protecting the environment, aiding in disaster recovery, and so on. The major difference between a charitable organization and an NGO is that it can run for profit. They accept funds from the general public for their survival.
Central Bank:
Central Bank is an entity that can be seen in every country and is called the Bank of Banks. They are responsible for the formulation of monetary policies and supervising or governing the other banks. It holds the privilege to issue currency notes for the nation. It eases or tightens the supply of money based on the demand to keep a nation’s economy on the positive side. It can be a lender when any financial institutions are in trouble.
Sovereign Wealth Funds:
It is an enterprise created by the Government to invest its surplus funds from any trade or budgeting. The sovereign wealth funds then invest that money in local industries to generate the return.
Clubs and Societies:
Based on the nature of Clubs and societies, it could be a non-profit or a profit-based entity whose profits go to the owner or can be saved by the club for a rainy day. Clubs can be established for fun & recreational activities, for people with similar interests, or even for social causes. They can grow to the extent of sponsoring an event or conducting a competition.
Testing Intricacies for the Different Business Entities:
Each entity type has its own intricacies based on its purpose and objective. We have mentioned the various testing considerations below.
Setting up an entity or type of Business
- Business rules pertaining to each of the entity types
- Nature of the business
- The process to add or modify the key owners or stakeholders of the entity.
- The type of registration that is required.
- Documentation requirements for setting up the entity.
- The workflow process for the approval or verification of an entity.
- Consider the variations in the country in which the setup is made based on and the country’s risk exposure as well.
- The economic condition of the country and its impact on the setup of the entity.
- Risk definition and approval mechanisms.
- The political influence and exposure of the business. (Could be added as a part of the Business Rules)
Below are the scenarios in which Testing should be mandated:
- When we need to create or set up an entity in a system, we are required to be aware of all the above areas and it has got its own influence on the setup. The primary focus area is on the Business Rules for each type of Entity.
- When we modify an entity type, we should again be careful to test all the above areas as business rules, country exposure, etc. might have different levels of impact.
- When there is new criteria or business rule imposed by a country, we need to do a round of post regression testing as the entity level rules change.
- When Risk exposure on a firm / Country / Region changes, we have to do another round of testing.
Since these entity setups mostly require multiple levels of approval and review, most of the applications will be standard workflow products like PEGA, IBM-BPM, TIBCO Business Studio, Appian, etc.
Conclusion
We hope you have found this blog to be informative and now have a clear picture of what an entity is, what the different types of entities are, and the intricacies you’ll have to know. As a leading QA company, we will be exploring such niche topics. So make sure to follow us on our social media handles to be updated with our blogs.
by admin | Nov 5, 2021 | Mobile App Testing, Blog, Latest Post |
An application crash is a developer’s worst nightmare. Even though it happens to everyone, it could be unbearable for your users and may cost you financial damages. Recurring crashes lead to more uninstalls; therefore, it’s great that there are numerous techniques to avoid them during mobile app testing. To accomplish this, your program must consistently provide a good user experience.
To ensure the stability of your application, first, identify the primary sources of crashes and devise methods to avoid them. Here’s how you can prevent app crashes by testing your app’s stability:
Memory and Processing Management
Memory difficulties are a leading cause of software crashes because not all users own high-end tablets and smartphones. As a result, your software must perform its intended functions while maintaining memory management.
To proceed, take caution not to utilize too much RAM. When possible, make use of your cache. Determine which parts of your software consume the most data or have the most complex data structures, and make sure they are all required.
Additionally, you can also profile your program to find memory leaks. As you structure network inquiries to avoid overburdening the device, craft methods and strategies to save memory and prepare a list of what to keep and what to delete.
Error Surveillance
Once you’ve identified errors and problems, you can rectify them. And when it comes to fixing app breakdowns and issues, you must go above and beyond. One method is to monitor the performance of the Internet Information Server and look for flaws.
For example, if a user’s WiFi connection goes down during a file transfer, you can notify them via a communication channel. When failures occur as a result of unexpected app behavior, you’ll need crash detection tools in your mobile app testing kit.
App Compatibility Testing
To test your program or app, use as many platforms, devices, manufacturers, and generations as possible. You can use this method to determine your compatibility. The majority, if not all, of devices and platforms are supported.
You must, however, be mindful of your limitations. Comprehensive mobile app testing will ensure that your app is compatible with a wide range of devices and will aid you in finding and addressing flaws before its release.
Activate Offline Use
Continuous network connectivity issues can harm your application system and may lead to a bad reputation. Users may be dissatisfied if they need your program but cannot access it due to a lack of internet access.
By employing a local data store such as Google Room, you can create an app that functions flawlessly offline. The application’s offline mode can help you prevent crashes and freezes caused by a sluggish internet connection.
However, early testing of mobile apps on slow networks may reveal weaknesses, preventing software from becoming inoperable on all networks. So, make it a point to check if the program works on unreliable networks.
Conclusion
While not all accidents are avoidable, those that are can be corrected quickly. This notion applies to developing applications as well. To put it simply, one of the most effective ways to learn about and fix your crashes is to use crash reporting tools. As you gather data and further broaden your knowledge, you’ll be able to create an app that is efficient and useful to your users.
Are you looking for mobile app testing services? Codoid is a forerunner in quality assurance comprising a team that guides and leads the community. For your assurance, our brilliant engineers attend meetup groups, forums, software quality assurance events, and automated testing conferences on a regular basis. Get in touch with us today!
by admin | Nov 4, 2021 | Mobile App Testing, Blog, Latest Post |
Appium is a great choice if you are on the lookout for open source tools to automate mobile applications. Be it native, web, or hybrid applications, Appium will be able to automate it. In addition to that, it has cross-platform support across Android, iOS, and Windows as well. Last but not the least, its support for multiple programming languages like C#, Python, Java, Ruby, PHP, JavaScript with node.js, and so on. As a leading QA company, Appium has been always been our go-to tool in many of our projects. So in this Appium guide, we will be giving you a thorough walkthrough of how you can run tests on real devices using Appium. Let’s take a look at a few other advantages that Appium has to offer before we proceed further.
Advantages of Appium
- Appium is an open-source tool that is very easy to install. Reinstallation of the application is also not needed when there are any small changes that have to be made.
- Appium doesn’t require any application source code or library.
- It has an active and helpful community.
- Unlike other testing tools, you wouldn’t have to include any additional agents in your app for making it compatible with Appium for automation. It will test the same app that will be uploaded to the App or Play Store.
- Beyond testing the mobile apps from Android and iOS, it can also be used to test windows desktop applications.
- Parallel execution of test scripts can be achieved by using Appium.
Prerequisites for using Appium
Now in this Appium Guide, let’s take a look at few of the prerequisite you’ll be needing in order to get Appium up and running. You would have to install the following,
- Java (JDK)
- Android Studio
- Additional Android SDK tools
- Appium jar file
- Appium Desktop Client
- Eclipse IDE for Java
Note: Node.js and NPM will be there by default whenever the Appium server is installed. It is not required to install node.js and NPM separately as would be already included in the current version of Appium.
Appium Guide to install Appium with Node.js
Step 1: Check if node.js is installed on your system by entering the below-mentioned code in Command prompt. Step 1 isn’t the only step where we have mentioned the codes. So make sure to use the appropriate codes we have highlighted in the command prompt.
node --version
npm –version
Step 2: Download the node.js installer
Step 3: Run the installer & install node.js & npm
Step 4: Check if node.js & npm are installed.
node --version
npm --version
where node
where npm
Step 5: Install Appium with node.js
Step 6: Check if Appium has been installed
Step 7: Start Appium
Installing Appium with APPIUM DESKTOP CLIENT in Windows
Step 1: Download the Appium desktop client
http://appium.io/
https://github.com/appium/appium-desk
Step 2: Install the Appium desktop client
Step 3: Start Appium through the desktop client
Appium Guide to install Appium on MacOS
Step 1: Check if node is installed on your system
Step 2: Install node.js
https://nodejs.org/en/download/
https://brew.sh/
Step 3: Check if node is installed using these codes
Step 4: Install Appium
Step 5: Check if Appium is installed
Step 6: Use the below code to start appium
Installing Appium with Appium desktop client
Step 1: Download the Appium desktop client
http://appium.io/
https://github.com/appium/appium-desktop
Step 2: Double click on the .dmg file to install the Appium desktop client
Step 3: Start the Appium desktop client
To verify Appium’s installation and its dependencies
Install Appium-doctor as it is a tool used to verify Appium installation. We can install it by using npm as we’ve already installed node
npm install appium doctor -g
If you want to check the version of Appium doctor, use the following code
How to uninstall Appium
If you had installed through node.js, then use the below code,
If you had installed the Appium Desktop Client, then just delete the app
Appium Guide to connect a Real Android Mobile Device on Windows
Step 1: Download SDK tools
https://developer.android.com/studio
Step 2: Unzip the folder and then extract the platform-tools using the below code
sdkmanager “platform-tools” “platforms;android-28”
This command will extract the platform-tools
Step 3: Set the environment variables
ANDROID_HOME=location of SDK folder
Path: Append the path of the plaform_tools folder
Step 4: Check the command ‘adb devices’ in the command line
Step 5: Make the device ready
Enable developer mode to turn on ‘USB Debugging’
Step 6: Connect the real device to the computer using a USB cable.
Step 7: Run the below command
adb devices
adb = android debug bridge
Check if your device ID is displayed.
Appium Guide to Connect Real Android Device on macOS
To achieve this, you must have Java installed on your system, and the JAVA_HOME should be set in the environment variables command to check the Java –version. You should have also installed homebrew.
Step 1: Download the Android SDK
You can download it using this link directly and install it using the below-mentioned codes.
brew install android-sdk
brew cask install android-sdk
Step 2: Extract the platform-tools folder using the following command
sdkmanager “platform-tools” “platforms;android-28”
Step 3: Add environment variables
ANDROID_HOME = path of android-sdk folder
Path: Append the path of the platform-tools folder
export ANDROID_HOME=/usr/local/share/android-sdk
echo $ANDROID_HOME
export PATH="/usr/local/Caskroom/android-sdk/4333796/platform-tools:${PATH}"
Use the below code to set the environment variables permanently on the Mac system
If bash_profile does not exist
bash_profile
Press i and add the following
For setting the PATH for ANDROID_HOME
export ANDROID_HOME=/usr/local/share/android-sdk
For adding the platform tools to the PATH
PATH="/usr/local/Caskroom/android-sdk/4333796/platform-tools:${PATH}”
Press the ‘Esc’ key
Hit ‘Enter’
Now Android Home and Path have been set permanently.
echo $ANDROID_HOME
echo $PATH
You should be able to run the command ‘adb devices’ now.
Step 4: Same as Windows, make your mobile device ready for automation by enabling developer options and turning on the ‘USB Debugging’ option.
Step 5: Connect the real device with your computer system using a USB cable.
Step 6: Run the following command
Check if the Device ID is displayed
Running Your First Test on a Real Mobile Device
Step 1: Download Eclipse or any other IDE for Java
Step 2: Create a Java project
Step 3: Add the following libraries
1. Selenium Java
2. Appium Java client
https://mvnrepository.com/
Step 4: Connect your device and run the below command
Step 5: Start the Appium server either from the command line or using the Appium Desktop Client
Step 6: Add the code to start automation on your mobile device.
Set the desired capabilities and start the calculator application.
deviceName
udid
platformName
platformVersion
appPackage
appActivity
Step 7: Run and validate
Appium Test Case for Native Android App (Calculator)
Step 1: Download the ADT Eclipse plugin or download the ADT bundle separately
Step 2: Open Eclipse and Create a new Project >> Package >> Class
Step 3: Import the Selenium library and TestNG inside that new project.
Step 4: Now create a small test Program for ‘Calculator.app’ to add two numbers.
package src_Appium;
import java.net.MalformedURLException;
import java.net.URL;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
//import org.openqa.selenium.remote.CapabilityType;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.testng.annotations.*;
public class Calculator {
WebDriver driver;
@BeforeClass
public void setUp() throws MalformedURLException{
//Set up desired capabilities and pass the Android app-activity and app-package to Appium
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability("BROWSER_NAME", "Android");
capabilities.setCapability("VERSION", "4.4.2");
capabilities.setCapability("deviceName","Emulator");
capabilities.setCapability("platformName","Android");
capabilities.setCapability("appPackage", "com.android.calculator2");
// This package name of your app (you can get it from apk info app)
capabilities.setCapability("appActivity","com.android.calculator2.Calculator"); // This is Launcher activity of your app (you can get it from apk info app)
//Create RemoteWebDriver instance and connect to the Appium server
//It will launch the Calculator App in Android Device using the configurations specified in Desired Capabilities
driver = new RemoteWebDriver(new URL("https://127.0.0.1:4723/wd/hub"), capabilities);
}
@Test
public void testCal() throws Exception {
//locate the Text on the calculator by using By.name()
WebElement two=driver.findElement(By.name("2"));
two.click();
WebElement plus=driver.findElement(By.name("+"));
plus.click();
WebElement four=driver.findElement(By.name("4"));
four.click();
WebElement equalTo=driver.findElement(By.name("="));
equalTo.click();
//locate the edit box of the calculator by using By.tagName()
WebElement results=driver.findElement(By.tagName("EditText"));
//Check the calculated value on the edit box
assert results.getText().equals("6"):"Actual value is : "+results.getText()+" did not match with expected value: 6";
}
@AfterClass
public void teardown(){
//close the app
driver.quit();
}
}
Conclusion
So we have done a comprehensive coverage of everything that you would need to know in this Appium Guide like the advantages of Appium, the methods to install Appium on both Windows and macOS, and also saw how to connect a real device on both platforms and run a test. We hope you’ve found this blog to be informative. As one of the best mobile app testing services providers, we highly recommend Appium for your testing projects to get the best results.
by admin | Nov 2, 2021 | Automation Testing, Blog, Latest Post |
Jenkins has risen to become an expert in Continuous Integration, Continuous Testing, & Continuous Delivery, and assumes a critical role in conveying great applications or items. It utilizes a component called the Jenkins pipeline for achieving Continuous Delivery (i.e.) the capacity to deliver applications routinely for a long stretch. This Jenkins pipeline guarantees that the product is consistently prepared for creation. As a leading QA Company, we have been using the Jenkins Pipeline and found it to be very effective. So if you are looking for a Jenkins Pipeline Tutorial that covers everything from the basics of the pipeline to learning how to perform parallel execution, you’ve found it.
What is a Jenkins Pipeline?
A pipeline in the Jenkins CI/CD can be defined as a series of events or even tasks that are interconnected to each other in a specific order. To put it in simpler terms, the Jenkins pipeline can also be characterized as a set of modules or plugins that enable the implementation & integration of the Continuous Delivery pipelines within Jenkins. It has an expandable automation system that can be used to build basic or complicated ‘template’ distribution pipelines via the Domain-specific language (DSL) used in the pipeline. Continuous Delivery in the Jenkins pipeline comprises 4 major states,
- Build
- Deploy
- Test
- Release
We will be taking a closer look at these states later on in the Jenkins Pipeline Tutorial, but first, let’s take a peek at the many advantages that the Jenkins pipeline CI/CD has to offer.
Advantages of the Pipeline:
- It can divide the jobs into parts (build /test /deploy) and each part can run in each agent.
- Parallel execution of stages is easy to configure and so it can be instrumental in saving time.
- Each stage can execute the different versions of JDK/MVN versions.
- It can be retriggered even from a failed stage.
- Visualizing the build flow becomes possible.
- The build can hold until the user gives the input.
- Version control and code reviews are made easier.
- We can pause and restart the build as and when we wish.
- It will automatically be created as sub-branches in a multi-branch pipeline script.
Pipeline’s Basic Keywords:
Knowing the basic keywords that will be used in the pipeline is the first step that we will be taking in our Jenkins Pipeline Tutorial. So let’s see what these keywords are and how you can use them in the pipeline. We’ll start with ‘Steps’.
Steps
- Steps have to be written inside the stage directive.
- Steps contains the command or scripts that we’ve used in the build.
-
- One step’s directive should be there in the stage directive.
Stage
- Stage defines a particular stage (build/test/deploy/..) of our job.
- There has to be a minimum of at least one stage.
- The name of the stage will be displayed on the Jenkins dashboard.
Stages
Stage and Stages are two different keywords that you shouldn’t confuse yourself with.
- It contains a sequence of the stages we saw earlier.
- There has to be at least one stage.
Agent
- It defines where we need to run our pipeline script. (Master/Slave/Container)
Stage color
So using color, we will be able to find out the current status of the stage.
- White – The stage hasn’t yet been executed.
- Green – The stage is a success.
- Blue Lines – The stage is being executed.
- Red Line or Red Lines – The stage has failed.
- Red (If in case few stages were a success and one failed, it will show red even if the few have been successful)
Types of Pipeline
1. Declarative pipeline
2. Scripted pipeline
So as seen above, there are two types of the pipeline, and the declarative pipeline is the recent addition that has the more simplified and opinionated syntax when compared to the scripted pipeline. Now let’s take a look at the syntax for these types.
Declarative Pipeline syntax:
Pipeline {
agent any
stages {
stage(‘Build’) {
Steps {
}
}
stage(‘Test’){
steps {
}
}
stage(‘Deploy’){
steps {
}
}
}
}
Scripted Pipeline Syntax:
node {
stage(‘Build’) {
}
stage(Test’) {
}
stage(‘Deploy’) {
}
}
Variables in the pipeline:
What is a variable?
A variable is used to store values. There are two types of variables, and they are predefined and user-defined variables.
<variable name> = <variable value>
Predefined Variable:
pipeline{
agent any
stages{
stage('pre'){
steps{
echo " predefined variable $BUILD_NUMBER $WORKSPACE "
}
}
}
}
Output:
User-defined Variable:
User-defined Variable we can define in root level or stage level
pipeline {
agent any
environment{
MYHOME="Chennai"
}
stages{
stage('User'){
steps{
echo " userdefined variable $MYHOME "
}
}
}
}
Output:
Parameters in Pipeline:
Parameters are used to pass the following types of data dynamically.
- String
- Text
- Boolean
- Choice
- Password
- File
Implementation of Parameters in Pipeline:
pipeline{
agent any
parameters {
string(name: 'DEPLOY_ENV', defaultValue: 'staging', description: '')
text(name: 'DEPLOY_TEXT', defaultValue: 'RnD\nJenkins\nPipeline\n', description: '')
booleanParam(name: 'Are You Have Permission to Deploy', defaultValue: true, description: 'Toggle this value')
choice(name: 'CHOICE', choices: ['One', 'Two', 'Three'], description: 'Pick something')
file(name: 'FILE', description: 'Some file to upload')
password(name: 'PASSWORD', defaultValue: 'SECRET', description: 'A secret password')
}
stages{
stage('string'){
steps{
echo " string $DEPLOY_ENV"
}
}
stage('text'){
steps{
echo " text $DEPLOY_TEXT"
}
}
stage('booleanParam'){
steps{
script{
if(TOGGLE){
echo " now execute, booleann is true"
}else{
echo " Dont execute, boolean is true"
}
}
}
}
stage('choice'){
steps{
script{
if(DEPLOY_ENV=='staging'){
echo " choice $CHOICE"
}
}
}
}
stage('file'){
steps{
echo " file $FILE"
}
}
stage('password'){
steps{
echo " password $PASSWORD"
}
}
}
}
Output:
Parallel Execution in Jenkins pipeline:
We will be focusing on the parallel build using the Jenkins declarative pipeline in our Jenkins Pipeline Tutorial now. So you can trigger your build system by Jenkins if there are some steps that could possibly run at the same time since they have no dependencies. By following this method, you will speed up your build process and save time for other sequential steps. As one of the best automation testing service providers, we don’t just stop with using the best tools, we also focus on using them in the best way possible.
Parallel Execution:
pipeline {
agent any
stages {
stage ('My Java Project Test Scenarios'){
parallel {
stage('Unite Test'){
steps {
echo 'Unit test Completed'
sleep 5
}
}
stage('Integration Test'){
steps {
echo 'Integration Completed'
sleep 5
}
}
stage('Security Test'){
steps {
echo 'Security Completed'
sleep 5
}
}
stage('Selenium UI Test'){
steps {
echo 'Selenium UI Test Completed'
sleep 5
}
}
}
}
}
}
Output:
Conclusion
We hope you enjoyed reading our Jenkins Pipeline Tutorial and found it to be informative at the same time. As promised we have covered everything including the basics of the Jenkins pipeline, seen its advantages, explored all the perquisites like variables and parameters that you will need to know to use it effectively. So make sure you don’t just try the Jenkins pipeline, make sure you use it effectively.
by admin | Nov 1, 2021 | Mobile App Testing, Blog, Latest Post |
Automation tests are a crucial part of the process that makes sure your iOS app is up-to-par with the required standards. We can say without any doubt that the bar has been raised to new heights because of the standards set by Apple. Automation testing on their end is highly standardized. The apps must go through rigorous checks before they can be approved for the App Store. The parameters include numerous guidelines set by Apple that are followed up with strict implementation rules. The XCUITest framework not only allows you to execute automated functional and performance checks but also shares information across devices in order to identify any inconsistencies between them before it’s too late! So in this blog, we will discuss how the XCUITest framework will be instrumental in helping you meet the high standards set by Apple.
Though the XCUITest framework is a popular tool from Apple, it’s still an independent module with many features that can be harnessed by any developer in the industry – even beginners! We know that XCUITest provides a framework that can be used for testing your iOS app. Since it supports Swift and Objective-C languages, it allows you to write tests in either of these programming languages instead of coding directly with Xcode or using another tool like StoryTest. These interactions are more realistic since they reflect how users will interact with your mobile application on their own devices rather than just simulating this behavior through code while being tethered by wires during development – it makes integration easy!
As one of the best mobile app testing companies, we have been able to use XCUITest in our projects to reap the wonderful benefits it has to offer. So let’s explore the tool’s potential by understanding the need.
UI Automation Testing
UI Automation Testing is a relatively new practice and has only recently started becoming popular among software engineers who want more control over how their work gets tested before it goes live. Frameworks like XCUITest allows testers to develop clean automation test suites for an app’s UI. These tests can run on different devices to check if the apps work properly regardless of the type or size of the screen you use them on. This makes it very convenient when testing apps that have international versions available but aren’t yet localized. Now let’s take a look at a few benefits UI automation testing has to offer.
Preserving Time and Money
Automation will pay off your investment with far greater returns as time goes on. The primary reason is that UI has such an important role to play in helping the customer feel satisfied with any application. A poorly designed UI has the potential to single-handedly derail your app’s success.
Automating Code isn’t Sufficient
UI testing shouldn’t be seen as something that has to be ticked off in your checklist. It is one of the best methods to ensure that your application works perfectly. Many developers use third-party frameworks like Appium to automate repetitive tasks to save time and to be more thorough. Developers must also perform code test cases to check the behavior and interactivity with the other modules. But the issue here is that they do not have any metrics that show how development sprint cycles or new builds affect UI functionality.
For example, if it takes more than the expected time to load or if some change has rendered any component from the previous release to become non-functional now. There are so many more similar scenarios that could happen. So the developers will be at risk when automating manual tasks using Test Automation Frameworks like Appium. These tools are only useful to automate parts of an automated assessment, whereas, the entire context needs attention. That is why tools like XCUITest and XCTest are very crucial.
Basics of the XCUITest Framework
With XCUITest, testers can write test cases to check how an application behaves when user actions are performed and compare the results they get with the expected outcomes. Using the two fundamental concepts behind XCUITest, they will be able to precisely monitor what a person would experience while using your app by utilizing their input device or system. They would also be able to validate the current state at any given time based on the documented interactions from the earlier tests to simulate real-life use conditions before the release.
XCTest
XCTest is the base testing framework for both iOS and OSX apps. It provides testers with various tools to write test cases in either Objective-C or Swift, to create UI tests classes (e.g., methods), and to assert the behavior validation when running them through Xcode. So all of this would be seamlessly integrated at your fingertips with XCTest!
Accessibility Features
QAs can also add accessibility features to the apps for people with disabilities. Accessibility technology has given QAs a new way of testing the app’s functionality when it is being used by someone who may not be able to use conventional input methods or have full access to all the components on the screen. So the UI test cases are created using functions provided within the Accessibility Core library that executes and validates tests against various parameters including size changes in width/height values. Changing these values will paint us a clear picture of how our program behaves differently depending on the user’s perspective.
XCUIApplication
Every time testers need to automate a test for an app, they have to ensure that it’s launched by specifying the XCUIApplication instance and calling the launch method on this object before the testing even begins. It should also terminate once all of its tasks have been completed so that no lingering processes are left behind after the tests have finished running. It will help to avoid any problems with sensitive data being leaked or tampered with during the analysis stage.
XCUIElement
The XCUITest framework provides a suite of components to help UI testers with their tests. These elements can be used in different ways, such as navigating & interacting within the view or performing actions like tapping & swiping on the screen. The class is responsible for handling these interactions between the user input devices (such as touchscreens) and the app logic. It also grants you access to look into how an element hierarchy unfolds — this way; we know which parts will respond when interacted with by our users!
XCUIElementQuery
The XCUIElementQuery is one of the most important classes in the UI framework. This class will allow testers to search for a particular element on that user interface, perform some action, and then move on to another task!
Conclusion
Xcode has many built-in features which allow developers of all levels to quickly explore potential bugs in their software before releasing them on the App Store. Plus, getting started is fairly easy for any iOS developer as it can be done without having to learn a new framework or language. As one of the best software testing companies in India, we always make sure to use the best tools and wrote this blog to help others understand the importance of XCUITest.
XCUITest is a powerful tool to help you find issues in your app’s code and pinpoint the root cause. With XCUITest, we can fiddle with our apps’ UI elements and ensure that end-users do not encounter unexpected results or have poor experiences. It provides an excellent way to test mobile apps, but it will only work if the tests are running on real devices or in emulated environments with XCUI Automation Platform integration enabled – which gives us total control over the computing resources during our automated testing sessions.
