Find the best tutors and institutes for Automation Testing

Find Best Automation Testing Training

Please select a Category.

Please select a Locality.

No matching category found.

No matching Locality found.

Outside India?

Search for topics

Automation Testing Updates

Ask a Question

Post a Lesson

All

All

Lessons

Discussion

Lesson Posted on 19/08/2017 IT Courses/QA/Automation Testing

Selenium Testing

Pradeep M

I have around 7 years of experience in manual and automation testing(selenium). - strong knowledge on...

Many, perhaps most, software applications today are written as web-based applications to be run in an Internet browser. The effectiveness of testing these applications varies widely among companies and organizations. In an era of highly interactive and responsive software processes where many organizations... read more

Many, perhaps most, software applications today are written as web-based applications to be run in an Internet browser. The effectiveness of testing these applications varies widely among companies and organizations. In an era of highly interactive and responsive software processes where many organizations are using some form of Agile methodology, test automation is frequently becoming a requirement for software projects. Test automation is often the answer. Test automation means using a software tool to run repeatable tests against the application to be tested. For regression testing this provides that responsiveness.

There are many advantages to test automation. Most are related to the repeatability of the tests and the speed at which the tests can be executed. There are a number of commercial and open source tools available for assisting with the development of test automation. Selenium is possibly the most widely-used open source solution. This user’s guide will assist both new and experienced Selenium users in learning effective techniques in building test automation for web applications.

read less
Comments
Dislike Bookmark

Lesson Posted on 17/07/2017 IT Courses/QA/Selenium IT Courses/QA/Automation Testing

What Is The Difference Between Driver.close() And Driver.quit()?

Kalpesh T.

Having over 5 years of working experience in Manual, Automation, Database, and Performance Testing by...

• Driver.close(): It is used to close the browser or page currently in focus. close() is a webdriver command which closes the browser window which is currently in focus. During the automation process, if there are more than one browser window opened, then the close() command will close only the... read more

• Driver.close(): It is used to close the browser or page currently in focus.

close() is a webdriver command which closes the browser window which is currently in focus.

During the automation process, if there are more than one browser window opened, then the close() command will close only the current browser window which is having focus at that time. The remaining browser windows will not be closed. The following code can be used to close the current browser window:

driver.close() //where, ‘driver’ is the Webdriver object.

• Driver.quit() : It is used to shut down the webdriver and close all instances associated to webdriver.

You should use driver.quit whenever you want to end the program. It will close all opened browser window and terminates the WebDriver session. If you do not use driver.quit at the end of program, WebDriver session will not close properly and files would not be cleared off memory. This may result in memory leak errors.

If the Automation process opens only a single browser window, the close() and quit() commands work in the same way. Both will differ in their functionality when there are more than one browser window opened during Automation.

read less
Comments
Dislike Bookmark

Lesson Posted on 01/06/2017 IT Courses/QA/Automation Testing IT Courses/QA/Selenium

Selenium Web Drive Wait Methods

Rajesh Bathula

I had been working as Software QA (Manual and Automation). I have very good knowledge in this domain...

Hi I am Rajesh, Here we have three types of wait methods in Selenium: 1.Implicitly Wait: Wait if required, otherwise, if the accuracy will good program will move to next level In General most of the time, we will use this method. 2.Explicitly Wait: Wait until expected condition will display, once... read more

Hi I am Rajesh,

Here we have three types of wait methods in Selenium:

1.Implicitly Wait: Wait if required, otherwise, if the accuracy will good program will move to next level In General most of the time, we will use this method. 

2.Explicitly Wait: Wait until expected condition will display, once condition will display program should move to next level.

Note: We should mention maximum time period for all these methods.

3.Fluent Wait: This method we are using when we need to mentioned time "fluently" frequently for that cases we are using this method.

Example: WAIT 5 SEC FOR EACH 35 SEC OF THE SCRIPT

read less
Comments
Dislike Bookmark

Looking for Automation Testing Training

Find best Automation Testing Training in your locality on UrbanPro.

FIND NOW

Lesson Posted on 27/04/2017 IT Courses/QA/Automation Testing

Unit Testing MVC Web Application using MSTest with MOQ Framework

Kunal Sehgal

I have more than 12 years of industry experience in web applications development using .Net platform...

Introduction - MSTest and MOQ framework We can use MSTest for end to end unit testing of any managed code(.net based languages) base testing. Mostly our applications are designed to have multiple physical tiers or logical layers like UI/BL/DL etc. We can create unit tests to test all the layers together... read more

Introduction - MSTest and MOQ framework

We can use MSTest for end to end unit testing of any managed code(.net based languages) base testing.

Mostly our applications are designed to have multiple physical tiers or logical layers like UI/BL/DL etc.

We can create unit tests to test all the layers together in which case each test case will call all the layers and methods as followed by true users and we can test all layers at once. This approach is ok but in most cases it leads to lot of dependencies for testing like having correct data  in databases, IO always to be available etc. Also it leads to in-effective testing as developers have to focus on many items at once rather than making a unit of code fully functional.

As name suggest unit testting is unit testing and shouldn't ideally be integration testing , its always better approach to use some kind of framework or tools which helps us in stubbing/faking/mocking the dependencies on other layers and focus only on the layer we want to test.

There are many tools available for this like MOQ,RhinoMOQ, MSFake and many others which helps us in mocking the dependencies and focus only on the unit of code we want to test.
All the above frameworks work on fundamental of dynamic Proxy creations.

For our purpose we are using MOQ which is the most widely used mock framework in whole industry primarily because of its effectiveness and easily understandable logic.
To use MOQ there are few considerations which includes :
a. We cant directly mock static or sealed classes and this includes both custom and .net based classes.
b. We can mock abstract or virtual classes and properties. Internally MOQ creates their overrides.
c. We can mock regular classes as well if we want to.

As a best practice all our layers/tiers should not be tightly coupled with each other and design should focus on segragating them.
Each layer should call other layer loosly which is easily possible by implementing the interfaces and not using concreate classes directly.
Using interface based implementation approach directly helps in mocking the dependencies very effectively.

Below test methods show case many different areas where mocking is important.
This solution doesn't include all possible scenerios but it's an effort to provide developers with enough knowledge on mocking and
helping them understand why its important.

Please refer other resources on code project for further knowledge on mstest fundamentals and moq.

 

Classes shown here are of a sample MVC web Project.

  • Few custom methods have been added like AddProduct, GetProduct etc for sample business rules  along with simple Action methods returning Views.
  • Action Filters have been added for testing purpose.
  • Custom Exceptions added for testing for expected Exceptions in test code.

Scenarios and items included in Test project are:

  1. Mocking standard dependencies of calling another layer from UI like Business layer/ 3rd  party/external calls.
  2. Handling static class in unit test. Static classes can’t be mocked directly using MOQ.
  3. Mocking .net framework based classes like HttpContext, ControllerContext, Principal/User and Identity. – For testing authentication scenarios.
  4. Handling Session variables by mocking SessionStateBase class. – Cache can/should also be handled same way but not tried.
  5. Handling Cookies from unit tests.
  6. Testing Action Filters (MVC).
  7. Using CSV file for data driven tests. – We can multiple data items to a unit test to check for all possible data scenarios.
  8. Detailed code commenting  of web and test projects to make code clear and  self-explanatory for developers.
  9. Comments detailing MOQ framework itself.
  10. MSTest Assert statements to test various scenarios.
  11. How to handle Exceptions in unit tests as well as exception messages.

A brief description of how to use the article or code. The class names, the methods and properties, any tricks or tips.

Blocks of code should be set as style "Formatted" like this:

// Classes defined here are MVC Controller class and ControllerTest class. It also includes code for
//defined ActionFilter as well.

//Controller name is HomeController.cs and will be part of Controller folder in MVC web app.

//ControllerTest class is HomeControllerTest.cs and will be part of Test project.

//ActionFilter is AuthorizeFilterAttribute.cs and can be placed anywhere in MVC Web project.

//We can see many other items in HomeController.cs like some interfaces defined in contructor but that is upto the dev. team to decide how they want to handle BAL or any other 3rd party dependencies and is not in scope of this tutorial.

//below code when talks about BL it means Business layer and DL means Data Acces layer.

////////////Code for Web Project's HomeController.cs class below////////////////////

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using BAL;
using MSFakes_TestApplication.Models;
using MSFakes_TestApplication.App_Start;
namespace MSFakes_TestApplication.Controllers
{
/// <summary>
/// THIS CONTROLLER CLASS HAS FEW ACTION METHODS RETURNING THE VIEWS BACK -- PART OF MVC TEMPLATE.
/// INDEX,ABOUT AND CONTACT ARE PART OF MVC TEMPLATE PROJECT.
///
/// ADDPRODUCT(GET), ADDPRODUCT(POST) AND GETPRODUCT ARE CUSTOM METHODS ADDED TO THIS CONTROLLER.
/// SOME SIMPLE BUSINESS RULES HAVE BEEN DEFINED IN THESE CUSTOM METHODS LIKE
/// CHECKING FOR SESSION VARIABLES,
/// CALLING BL TO ADD AND GET PRODUCT,
/// CHECKING IF PRODUCT AVAILABLE OR NOT,
/// CHCKING IF PRODUCT ID IS NULL,
/// ALSO CHECKING IF CORRECT VIEWS ARE RETURNED.
/// USING STATIC CLASSES IN A WAY THAT THEY ARE WRAPPED INSIDE A REGULAR INSTANCE CLASS. THIS HELPS IN HANDLING STATIC ITEMS DURING MOCKING
/// ALSO HAVE DEFINED SOME DUMMY CUSTOM EXCEPTIONS.
/// DEFINED ONE ACTION FILTER TO CHECK FOR AUTHENTICATION ETC
/// </summary>
public class HomeController : Controller
{
public HomeController()
{

}

//unit has been setup to initialize the classes for these interfaces.
private IProduct _productBL;
private IStaticFieldsHandler _staticHandler;

/// <summary>
/// defining controller constructor.
/// </summary>
/// <param name="productBL">ProductBL (BAL) implements IProduct interface</param>
/// <param name="staticHandler">in BAL there is a class wrapping the static class and implements IStaticFieldsHandler interface</param>
public HomeController(IProduct productBL, IStaticFieldsHandler staticHandler)
{
_productBL = productBL;
_staticHandler = staticHandler;
}

[AuthorizeFilter(role: "Admin")]
public ActionResult Index()
{
var vw = View("Index");
return vw;
}

public ActionResult About()
{
ViewBag.Message = "Your application description page.";

return View();
}

public ActionResult Contact()
{
ViewBag.Message = "Your contact page.";

return View();
}

[HttpGet]
public ActionResult AddProduct()
{
//some logic
if (this.ControllerContext.HttpContext.Request.Cookies["MyBasket"] != null)
throw new CookieFoundException("Product already available in basket. Please check out");
else
{
int returnValue = _staticHandler.GetKeyValueFromDatabase("testkey");
if (returnValue == -1)
{
return RedirectToAction("Index");

}
else
return View(new ProductViewModel());
}
}

[HttpPost]
public ActionResult AddProduct(ProductViewModel model)
{

if (model.ProductID == string.Empty || model.ProductName == string.Empty || model.ProductCost == int.MinValue)
throw new ArgumentNullException("Please enter product details correctly");

Product p = new Product { ProductID = model.ProductID, ProductAvailable = model.ProductAvailable, ProductName = model.ProductName, ProductCost = model.ProductCost };
p = _productBL.AddProduct(p);

//p.Added += Product_Added;
model.ProductID = p.ProductID;

ListModel.AddModel(model);

return View("ListProducts", ListModel.Collection);
}

//public void Product_Added(object sender, EventArgs e)
//{
// ViewBag.Message = "Product Pushed";
//}

[HttpGet]
public ActionResult GetProduct(string productid = "")
{
string sessionkey = string.Empty;
//get something from session variables
if (Session["SessionVariable"] != null)
sessionkey = Session["SessionVariable"].ToString();
else
sessionkey = "No session";

if (this.ControllerContext.HttpContext.Request.Cookies["LoginCookie"] != null)
{
if (productid == string.Empty)
{
throw new ArgumentNullException("ProductId is null");
}

var p = _productBL.GetProduct(productid);
if (p.ProductAvailable == true)
{
ProductViewModel model = new ProductViewModel { ProductID = p.ProductID, ProductCost = p.ProductCost, ProductName = p.ProductName, ProductAvailable = p.ProductAvailable };

return View("Products", model);
}
else
{
ViewBag.Message = "Product Not available";
ProductViewModel model = new ProductViewModel { ProductID = string.Empty, ProductCost = int.MinValue, ProductName = "NA", ProductAvailable = false };
return View("Products", model);
}
}
else
throw new LoginCookieNotFoundException();
}
}
}

 


////////////ActionFilter - Web project's AuthorizeFilterAttribute.cs below///////////////

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
namespace MSFakes_TestApplication.App_Start
{
public class AuthorizeFilterAttribute : ActionFilterAttribute
{

string _role = string.Empty;
public AuthorizeFilterAttribute(string role)
{
_role = role;
}
public override void OnActionExecuting(ActionExecutingContext filterContext)
{
if (filterContext.HttpContext.User.Identity.IsAuthenticated)
{
if (_role != "Admin")
{
filterContext.Result = new RedirectResult("////Home//AddProduct", false);
}
}
else
{
throw new UnauthorizedAccessException("User not authenticated to access th site");
}

base.OnActionExecuting(filterContext);
}

}
}

 

We need to have MOQ assembly either using Nuget package installed in test project before using MOQ library.

 

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Web.Mvc;
using Microsoft.VisualStudio.TestTools.UnitTesting;
using MSFakes_TestApplication;
using MSFakes_TestApplication.Controllers;
using BAL;
using Moq;
using System.Web;
using System.Security.Principal;
using MSFakes_TestApplication.App_Start;
using MSFakes_TestApplication.Models;
using System.Diagnostics.CodeAnalysis;

//wrapper namespace for Test class

/*
* This Test class provided enough base understanding on how to create/manage unit tests using MSTest/Microsoft Unit testing tools.
* We can use MSTest for end to end unit testing of any managed code(.net based languages) base testing.
* Mostly our applications are designed to have multiple physical tiers or logical layers like UI/BL/DL etc.
* We can create unit tests to test all the layers together in which case each test case will call all the layers and methods as followed by true users and we can test all layers at once.
* Above approach is ok but in most cases it leads to lot of dependencies for testing like having correct data in databases, IO always to be available etc.
* Also it leads to in-effective testing as developers have to focus on many items at once rather than making a unit of code fully functional.
*
* As name suggest unit testting is unit testing and shouldn't ideally be integration testing , its always better approach to use some kind of
* framework or tools which helps us in stubbing/faking/mocking the dependencies on other layers and focus only on the layer we want to test.
* There are many tools available for this like MOQ,RhinoMOQ, MSFake and many others which helps us in mocking the dependencies and focus only on the unit of code we want to test.
* All the above frameworks work on fundamental of dynamic Proxy creations.
*
* For our purpose we are using MOQ which is the most widely used mock framework in whole industry primarily because of its effectiveness and easily understandable logic.
* To use MOQ there are few considerations which includes :
* a. We cant directly mock static or sealed classes and this includes both custom and .net based classes.
* b. We can mock abstract or virtual classes and properties. Internally MOQ creates their overrides.
* c. We can mock regular classes as well if we want to.
*
* As a best practice all our layers/tiers should not be tightly coupled with each other and design should focus on segragating them.
* Each layer should call other layer loosly which is easily possible by implementing the interfaces and not using concreate classes directly.
* Using interface based implementation approach directly helps in mocking the dependencies very effectively.
*
* BELOW TEST METHODS SHOW CASE MANY DIFFERENT AREAS WHERE MOCKING IS IMPORTANT.
* THIS SOLUTION DOESN'T INCLUDE ALL POSSIBLE SCENERIOS BUT IT'S AN EFFORT TO PROVIDE DEVELOPERS WITH ENOUGH KNOWLEDGE ON MOCKING AND
* HELPING THEM UNDERSTAND WHY ITS IMPORTANT.
*
* PLEASE REFER ONLINE RESOURCES FOR FURTHER KNOWLEDGE ON MSTEST FUNDAMENTALS AND MOQ.
*/
namespace MSFakes_TestApplication.Tests.Controllers
{
/// <summary>
/// Test class for HomeController.cs - using MSTest with MOQ as isolator for single layer unit testing
/// </summary>
///
//Class has to use the below attribute in order to be picked by MSTest
[TestClass]
//Just for reference this attribuet has been set here. If VS is run to calculate code coverage we are telling it to ignore the test class
[ExcludeFromCodeCoverage]
public class HomeControllerTest
{
private string _propX;

// [DeploymentItem("//TestData/BadProductData.csv")] - to Deploy test related files like data files/config files etc we can deplo them to
//either specific folder or to output folder in the configured testResult folder.

//This is called before each Test method. We can use this to some initializations like setting up default test Data or setting up some TestProperty e read less

Comments
Dislike Bookmark

Lesson Posted on 21/02/2017 IT Courses/QA/Selenium IT Courses/QA/Automation Testing

Selenium WebDriver 3.0, Test NG and JAVA.

Learn Park

LearnPark is an organisation which hosts Seminars like Wealth Management and Relaunch Career for Women,...

Hello, Selenium WebDriver 3.0 with GeckoDriver is the latest upgrade of Selenium. To execute automation test scripts in Mozilla browser we need to install GeckoDriver seperately and the scripts should include. package seleniumPrograms; import org.openqa.selenium.WebDriver; import org.openqa.selenium.firefox.FirefoxDriver; ... read more

Hello,

Selenium WebDriver 3.0 with GeckoDriver is the latest upgrade of Selenium. To execute automation test scripts in Mozilla browser we need to install GeckoDriver seperately and the scripts should include.

package seleniumPrograms;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
 
public class SeleniumThree_test {
 
public static void main(String[]args ) throwsInterruptedException {
System.setProperty("webdriver.gecko.driver","C:\\Selenium3\\work\\tools\\geckodriver.exe");
WebDriver driver=newFirefoxDriver();
driver.get("http://www.google.com");
 
Thread.sleep(4000);
driver.quit();
}

To Try new features of Selenium 3, we need to use Mozilla 47.0.1.

read less
Comments
Dislike Bookmark

Answered on 18/12/2016 IT Courses/QA/Automation Testing

ICreative Solution

The term BIOS is an acronym for Basic Input/Output System. BIOS is a low level software, the first software to run when you power up the system. It is as the software that intermediates data transfers between the hardware components of a system and the user or the software installed on that system. The... read more
The term BIOS is an acronym for Basic Input/Output System. BIOS is a low level software, the first software to run when you power up the system. It is as the software that intermediates data transfers between the hardware components of a system and the user or the software installed on that system. The BIOS provides a number of services that allow users and higher level software to configure the settings for a computer's hardware components and to get direct information from those components. BIOS are generally very small programs, with a size of up to 16 MB. Modern BIOSes have a user interface, usually called Setup Utility, where the user can configure many hardware settings. On laptops or tablets you will often encounter simplified BIOS versions, in which the user can only set the time and a couple of other things like the boot order. read less
Answers 12 Comments
Dislike Bookmark

Looking for Automation Testing Training

Find best Automation Testing Training in your locality on UrbanPro.

FIND NOW

Lesson Posted on 17/12/2016 IT Courses/QA/Automation Testing IT Courses/Software Testing IT Courses/Manual Testing

Practices & Strategies For Test Automation

ICreative Solution

We would like to introduce ourselves as a team of fully qualified professionals in the field of IT education...

Q)What are the Best Practices and Strategies for Test Automation? A)Below are some best practices & strategies for Test Automation: 1.Hire a Dedicated Automation Engineer or Team:This is a basic thing to do. Don’t ask your manual testers to indulge in test automation. If you do want them... read more

Q)What are the Best Practices and Strategies for Test Automation?

A)Below are some best practices & strategies for Test Automation:

1.Hire a Dedicated Automation Engineer or Team:
This is a basic thing to do. Don’t ask your manual testers to indulge in test automation. If you do want them to do test automation, then free them from manual testing work. Test automation is a full time job. For this you need dedicated resources.

2.An automation tool is important, but it is not the solution of everything:
Selecting the right tool is just the beginning. Tool make the process easier. But you need skilled resources to complete the process.

3.Select the automation tool which is familiar to your resources:
If your resources are familiar with C# and your application to be tested is also developed in C#, then there is no point selecting the tool which does not offer C# to write scripts.

4.Know the application being tested:
The tool selection depends heavily on the technologies used in your product. Know your product inside out before starting the automation.
If it is a web application, know the browsers it will support. Know the technologies being used in it. If it is a desktop application, know which language is built upon. What third-party controls are being used in the application. This will help you make the tool selection and future automation easier.

5.Good Automation means good manual test case:
Nicely written strong manual test cases saves us from automating those test cases which are easy to automate but weak in finding defects.

6.Identify opportunities with automation:
If you are handed over with a manual test case to automate, don’t just automate that test case as it is. Instead, find further opportunities in your automation, to expand the scope of this test case.

7.You cannot automate everything:
Automation means running fewer tests more often. You have to start small by attacking your smoke tests first. Then cover your build acceptance tests. Then move onto your frequently performed tests, then move onto your time taking tests. But make sure every test you automate, it saves time for a manual tester to focus on more important things.

8.Automation is software development :
If you develop a quality software, it needs best practices. It needs code reviews to write quality code. It needs a framework or design pattern to be followed. It needs constant maintenance.
Automation is basically software development. So all best practices you follow when you develop a software should be followed in doing automation. Automation Framework should be there. Code Reviews should be done. Bugs of automation should be reported in bug repository. Source Code of automation should be placed under a source control, etc.

 

read less
Comments
Dislike Bookmark

Lesson Posted on 17/12/2016 IT Courses/Software Testing IT Courses/Manual Testing IT Courses/QA/Automation Testing

What Points Determines A Candidate Is Fit For A QA Job Or Not?

ICreative Solution

We would like to introduce ourselves as a team of fully qualified professionals in the field of IT education...

Following are some(base) Points Which Determine a Candidate is Fit for the QA Job or Not: 1.On Curiosity and passion: Being a software tester means being curious for everything. You need to mirror a child who is curious for the whole world and wants to know how it works. This is the critical criteria... read more

Following are some(base) Points Which Determine a Candidate is Fit for the QA Job or Not:

1.On Curiosity and passion: Being a software tester means being curious for everything. You need to mirror a child who is curious for the whole world and wants to know how it works. This is the critical criteria to be considered.

2.On Understanding priorities: A tester is always loaded with multiple tasks and if not able to define priorities, (s)he will create a mess only. Rather than jumping into everything and not able to complete anything, it’s better to leave work area with a satisfaction that you have successfully completed one of the important work.

3.On Bug reporting: It’s an art to describe the problem you are facing and that art is the key factor for any software tester to be successful in this field.

4.On Ideas generation: Being in most creative field, software testing, if a tester is unable to generate test ideas, s(he) will start feeling stagnant in short duration.

5.On Concepts: Being a software tester, it’s expected that the person should know what testing is and how to perform it better. Conceptual knowledge is also necessary and can be evaluated with below questions:

A.While SDLC model is better as per you? Waterfall or Agile? Why?
B.What is the need of re-testing when you are already doing regression testing?

6.On Analytical skills:
Finding the root cause or pattern of an issue is as important as finding an issue. A tester is expected to show that skill too.

If your all the above points are clear then definitely you will get your QA job next time.

read less
Comments
Dislike Bookmark

Lesson Posted on 13/12/2016 IT Courses/QA/Automation Testing

Short introduction about Appium

Mahesh Patil

Have 6 years of experience in Mobile Application testing & Software testing/Manual testing Have a great...

“Appium is an open source, cross-platform test automation tool for native, hybrid and mobile web apps, tested on simulators (iOS, FirefoxOS), emulators (Android), and real devices (iOS, Android, FirefoxOS).” APPIUM is a freely distributed open source mobile application UI testing framework. Appium... read more

“Appium is an open source, cross-platform test automation tool for native, hybrid and mobile web apps, tested on simulators (iOS, FirefoxOS), emulators (Android), and real devices (iOS, Android, FirefoxOS).”

  1. APPIUM is a freely distributed open source mobile application UI testing framework.
  2. Appium allows native, hybrid and web application testing and supports
  3. Automation test on physical devices as well as on emulator or simulator both.
  4. It offers cross-platform application testing i.e. single API works for both Android
  5. And iOS platform test scripts.
  6. It has NO dependency on Mobile device OS. Because, APPIUM has framework or
  7. Wrapper that translate Selenium Webdriver commands into UIAutomation (iOS)
  8. Or UIAutomator (Android) commands depending on the device type not any OS type.
  9. Appium supports all languages that have Selenium client libraries like- Java,
  10. Objective-C, JavaScript with node.js, PHP, Ruby, Python, C# etc.
read less
Comments
Dislike Bookmark

Looking for Automation Testing Training

Find best Automation Testing Training in your locality on UrbanPro.

FIND NOW

Answered on 02/03/2017 IT Courses/QA/Automation Testing

Vinodkumar K V

Full Stack Developer

1. Learn any OOP based language. this is most important. 2. Learn Selenium. 3. Learn CI tools like GIT, Maven and jenkins.
Answers 25 Comments
Dislike Bookmark

About UrbanPro

UrbanPro.com helps you to connect with the best Automation Testing Training in India. Post Your Requirement today and get connected.

Overview

Questions 15

Lessons 29

Total Shares  

+ Follow 6,336 Followers

Top Contributors

Connect with Expert Tutors & Institutes for Automation Testing

x

Ask a Question

Please enter your Question

Please select a Tag

UrbanPro.com is India's largest network of most trusted tutors and institutes. Over 25 lakh students rely on UrbanPro.com, to fulfill their learning requirements across 1,000+ categories. Using UrbanPro.com, parents, and students can compare multiple Tutors and Institutes and choose the one that best suits their requirements. More than 6.5 lakh verified Tutors and Institutes are helping millions of students every day and growing their tutoring business on UrbanPro.com. Whether you are looking for a tutor to learn mathematics, a German language trainer to brush up your German language skills or an institute to upgrade your IT skills, we have got the best selection of Tutors and Training Institutes for you. Read more