Nishant Verma

What is it?  vodQA is a platform for members of the software testing industry to strengthen the QA community by sharing and learning new practices and ideas. vodQA is a series of testing events hosted by ThoughtWorks across our India offices. This is the first time it will take place in Bangalore. The series is open to all testing professionals from the IT industry. Read more details here .

  Generally when we are writing our automation test in Selenium or any other driver , the first thing we tend to do is start looking for object Id. Thought we have multiple ways of getting the hold of the object on a webpage like: Id name Link text XPath DOM Id or name is the most simplest and easy to use locators. Advantages with them is it increases the readability of your test code. It’s also better than other locators in terms of test performance. If you are using lot of Id’s and your test code is becoming too clumsy then one suggested way of using Id’s would be to have a separate file and then probably you can rename them if they are not properly named in the page source (Google page “q” as their search box Id). Link Text is mostly used with links and limited to that. They are easy to use. However they are a little problematic to maintain because of often changing link texts. Next is the famous XPath, simple to use (if you are usi...

This blog is mostly like a  “How to” post on testing web application using Eclipse IDE, JUnit and AndroidDriver. What all you need ? Eclipse (version 3.7), JUnit, selenium-server-standalone-2.15.0.jar and of course Android SDK. Before you do anything, you need to install Android Emulator on Windows, and then install WebDriver on that emulator: http://www.nishantverma.com/2011/06/installing-android-emulator-on-windows.html     http://www.nishantverma.com/2011/06/installing-webdriver-on-android.html Post the set up, you can refer below to download the sample test framework from Github to get started https://github.com/nishantverma/Android This is a test framework skeleton and can be leveraged for specific testing requirements.

On Friday, I just finished "Group Feedback" session. Well I don't want to blog about what happened in that feedback. This post is more from the point of view of "Why we need feedback?". What is " feedback "? Wikipedia defines feedback as Feedback  describes the situation when output from (or  information  about the result of) an event or  phenomenon  in the past will influence an occurrence or occurrences of the same (i.e. same defined) event / phenomenon (or the continuation / development of the original phenomenon) in the present or future. When an event is part of a  chain  of  cause-and-effect  that forms a circuit or loop, then the event is said to  "feed back"  into itself.  We work in team and the team is made up of "Individuals". The behavior of individuals influence the outcome of team , may be in a positive manner or negative! A team is constituted to achieve a certain goal and so the team members beh...

Internet Explorer does less than 50 percent of world's web surfing, Chrome on the come-up -- Engadget : "Microsoft's finest still has a healthy 52.63 percent desktop market share, which gives it a sizable lead over the competition from Firefox (23 percent), Chrome (18 percent), and Safari (five percent)" 'via Blog this'

Conducting a workshop on Testing tool is not new for me. In past I have given the same for QTP and other tools in my previous organization. How was this different ? What’s new for me ? I noticed that these kind of sessions mostly revolves around tool. Those sessions were mostly like Feature drill down from Day-1 to last day nothing but just features. During my QTP days, I used to prepare a Power point presentation of features and snapshot of screen flows to illustrate it. What’s different in conducting Twist session. I actually thought of experimenting. I listed down all the critical features which I thought of discussing and then finalized on the application (which was Mingle , a Project Management Tool from ThoughtWorks Studios). I started session with a persona of a QA on a testing team of Mingle (AUT) who will be involved in writing test cases, testing Story acceptance criteria and finally automating it. So it was easy for me to map the requirements of a Tester with the feat...

Previous two posts Web Application Testing (QTP Vs. Twist) and Test Creation (QTP Vs. Twist) talks more about the features in the tool and ease of use.  Following my two blog posts where I have compared QTP with Twist, this blog post is next  in the series which will talk about  Test framework and maintenance in both the tools. When you launch QTP, you will notice that the Process Guidance pane shows you a path to achieve what QTP has popularized in the Testing community as “ Keyword-Driven Testing ”. [Keyword Driven Testing is a technique that separates much of the programming work from the actual test steps so that the test steps can be developed earlier and can often be maintained with only minor updates, even when the application or testing needs change significantly] -QTP Help File on “Keyword Driven Testing” This technique relies on 3 pillars: Test Steps Keywords Object Repository So a tester generally writes Test steps usi...