Setting up TestNG & ADT plug-in for Eclipse


Recently I have switched from "simple" Windows to "Smart" Mac, so I had to do all those basic set up of my typical test automation env which I had on Win7. 
This post will detail about installing TestNG and Android plug-in into Eclipse and get started with your test.

Steps to install TestNG:
1. Click Help -> Install New Software.
2. Paste this URL http://beust.com/eclipse in the "Work with" edit box and click on "Add" button.
3. In the ‘Name’ column we can see "TestNG" -> Select this and click "Next" button.
4. Click on "Next" and click on the radio button "I accept the terms of the license agreement".
5. Click on "Finish".
6. Click on "Next" button.


Once the above steps are done, this will install the TestNG plug-in for Eclipse and it will start for restart of Eclipse. Just restart the Eclipse. You should be good.

To install ADT plug in Eclipse, follow these steps:
  • Start Eclipse, then select Help -> Install New Software....
  • Click Add, in the top-right corner.
  • In the Add Repository dialog that appears, enter "ADT Plugin" for the Name and the following URL for the Location: 
https://dl-ssl.google.com/android/eclipse
In case this throws up error you might want to try with just http instead of https.
  • Click OK
Once you install this, you need to navigate to Window -> Android SDK Manager then select "ARM EABI v7a System Image" and then click on "Install packages..." 

Once you do this, you should be able to launch AVD Manager and then create a virtual device.

Now you need to install WebDriver on that emulator and post that you can download a sample android test framework from Github to get started. 
This is a test framework skeleton and can be leveraged for specific testing requirements.

Comments

Post a Comment

Your comments will be reviewed and then published !

Popular posts from this blog

Defect Tracking System – Wastage of Money & Time ???

Image
As a QA I have been logging bugs since 5 years. But what do we do with that ? A typical flow: If this is the only thing we need to do then why taking so much of pain to have a defect tracking system . To log a standard bug (Standard Bug= Broken Functionality), we need to write steps to reproduce, pre-requisites (if any), expected result, actual result, priority, severity, snapshot (if any), Test environment details and finally save it. This takes around roughly 3-5 minutes to log a bug. To say truth, I have never seen any report coming out of defect tracking system which is of use in analyzing the pattern of bug or finding out any trend in them. All I have seen apart from tracking usage, is the summary of bugs with count based on Priority and Severity. Is that the only purpose of Defect Tracking System? If that is the case then why not use a Google spreadsheet rather then investing money of the company and time of QA in a bug logging system. I am sure if we mine the data which i
Read More »

The 3 qualities that will always help you become better at almost anything…

Image
Have we ever noticed how excited we are when we start anything? But it’s a sad fact that 70% of people abandon what they have started with so much energy and love. It could be as small as building a hobby or starting a pet project or even an activity or a side learning we started. “ Well begun is half done .” Aristotle did say this but we are judged for how we have finished something. You separate yourself fro m  the masses when you choose to give that task a finish.  The first quality is finishing off what you started and it helps develop mental stamina or willpower.   It builds confidence and inculcates as a habit in a long run. You don’t need to sign up for the mammoth activity to build this habit, even finishing mundane day-to-day routine tasks will help. Diligence — the quality of working carefully and with a lot of effort Diligence is a quality that almost never will get unnoticed. It’s one of the underlying traits of great works or success. The key to mediocrity on the o
Read More »

Test Case Paths : Happy, Sad & Bad

Image
I came back from the background of writing test cases which were categorized in either Positive or Negative test cases. Positive test cases were business flows which may or may not give any result but they will certainly not give any exception or error. Negative test cases are those test cases which were bound to result into some exception or better expressed as error causing scenarios.  Then those positive test cases were prioritized as High/Medium/Low . Finally it used to result in quite a comprehensive test case document. Then it will go through the process of review and few more updates or change of priority etc. Certainly it is a tedious process. Here in ThoughtWorks I got introduced to different way of categorizing test cases called “ Happy/Sad/Bad ”. A test case which results you in a positive result is a Happy path , for e.g. entering proper username and password on login page. A test case which yields no result like entering invalid username and invalid password on a logi
Read More »