In Selenium Conference Bangalore 2016, Selenium WebDriver version 3 was the hot topic and the major takeaways from this topic were: WebDriver 3 will no longer support Selenium 1 i.e. Selenium RC. …
Source: FirefoxDriver or MarionettDriver
In Selenium Conference Bangalore 2016, Selenium WebDriver version 3 was the hot topic and the major takeaways from this topic were: WebDriver 3 will no longer support Selenium 1 i.e. Selenium RC. …
Source: FirefoxDriver or MarionettDriver
With superb day one we were all looking forward for day 2 and we were not disappointed. Lets jump straight to summarising the sessions
This was my favourite talk for #SeConf16 here is what I understood
This talk was related to abstracting UI changes in the application from the functional changes. This would be really helpful in cases where want tests to be isolated from UI changes.
My take on parallel execution on tests on mobile was that one would need write some engine to manage device’s availability and we take example of Justin’s code for doing it which shared on github here
In the session Priti talked about managing your Page Objects for multiple applications in single class. We had faced similar challenges in one of our projects however we implemented different Page Object class for different apps because we felt it would be better if each class is assigned single responsibility
This session was interesting and completely new where it said that instead of writing tests we should be generating tests. However after the session I was wondering that time/cost involved for generating tests versus the kind of bugs that these tests will find is it going to be worth it.
To summarise the each of 2 days we learnt a lot of new things. We have all picked up various areas of interests where we will try to apply the knowledge gained in these 2 days.
Kudos to the organiser’s and all who attended the #SeConf16. It was awesome!!!
After awesome experience @ VodQA; QAvengers (Ulhas Deshmukh, Hemant Ojha, Irfan Ahmad, Neha Tandon and My Self.) decided to visit Selenium Conference in Bangalore and we were super excited.
Here’s how the day 1 looked like
Announced release of Selenium 3 and what changes in selenium 3
for (i=0; i < 10; i++) { Read(“Selenium Core is no more”) }
Since we had parallel talks we divided in ourselves in groups Ulhas and Hemant attended above talk which they described in following bullet points
Appium code refactoring – This has made huge difference to Appium code and made it easy for contributor’s
Winium for automating windows app is part of appium – This is great news for people who have windows app to tests
Me and Neha attended this demonstration and here’s what we learnt
Here we shared our experience in writing automation tests following were the highlights
This talk gave a great idea of how selenium can be used for more than just doing web application testing. Idea was to use selenium along with BrowserMobProxy to test analytics. I am must say we were really impressed by the presentation by Vinay.
In the next session I tried few of our existing tests with Selenium 3 beta and guess what they worked just as fine. Luckily I was seated besides Simon Stewart when I did this and when told him tests are working well. This was his reaction.
Day ended with superb jam session. It was great day we enjoyed not only the awesome talks but also awesome good!!!
You can find the Day 2 experiences here
When I want to speak about the future of testers and testing, I first have to think about the situation we have now, and why I want to change anything about that. In the past decade or so there wer…
Source: Reinventing Testers and Testing to prepare for the Future
This blog is to share our experiences (Irfan Ahmad, Hemant Ojha and Ulhas Deshmukh) @vodQA event in Pune. The Journey began as early as 4.00 am in the morning (don’t remember last time I woke up this early and some didn’t sleep at all).
Welcome note
The talk started with usual welcome note however it was not very usual. From the welcome note itself it was clear that we were going to have a very open ended session and interactive.
Agile Game
This one was my favourite it has many learnings for us. So we were given task lets call it project, we had a PO and we had team. The project was to blow some balloons and draw face on it seemed really easy. However it was not so and here is why
Agile Testing
Here we were shown Agile testing manifesto. For me the learning here was
Effective Strategies for Distributed Testing
This session was focused on effective ways of communication when entire team is not at same place. Effectively using tools like JIRA help’s everyone in team be on same page at any point in time
Testing the Mysterious Sphere
I think this was most entertaining session from audiences point of you. Learnings
Test Automation – Principles, Practices
Patterns in Test Automation
Summary
I am have 8 years’ experience in software testing. Apart working for my daily job I strongly believe that one should always put significant amount of effort in your personal development. Like the great Steve Jobs quoted “Work takes up large part of our life so we should love what we do.”
As I thought more and more over it I started to believe to love what you do; I should be good in what I do; that means spending more time doing what we love. That’s where I started looking for more opportunities related to software testing and came to know about Crowd Testing.
From Stake holder perspective: Getting software tested from diverse software experts on diverse platforms using various cloud based platforms.
From Tester perspective: It’s an opportunity. Yes an opportunity to
I love writing automated scripts which help in reducing testing efforts and always looking for an opportunity to do so and one such opportunity came my way thanks to Praveen from 99tests and Yogi from GetSkills
The requirement was to write functional automated tests for a website
To get started we need to have an account with http://bitbucket.org/ which is like version control and once that is in place Yogi(Stakeholder for GetSkills) granted required access.
There was very good document provided to
We also used HipChat to resolve any queries we had amongst all the people working on the project
I would strongly recommend all my fellow testers to join the crowd testing eco system and leverage vast benefits of it.
I would like to thank again Praveen(http://99tests.com/) and Yogi(http://getskills.co.nz/) for the opportunity and all the fellow testers for helping me out when it was needed.
Crowd tester,
Jitendra
I have was able to successfully integrate Bugzilla and Selenium using j2bugzilla API. When I say integrate it means that when executing Selenium tests using TestNG framework and if a test method fails then a defect will be reported in Bugzilla with a screenshot attached for the failure.
Following are the libraries used.
Following are the steps I followed to achieve above mentioned scenario
2. Implement the connect Bugzilla : This class which will be used by the listener for communicating with Bugzilla and performing operations on the same. Using j2bugzilla the class looks as follows
3. Implement RaiseDefectWithScreenShotOnFailure class : This extends TestListenerAdapter and overrides the method onTestFailure(ITestResult tr)this uses connect Bugzilla class to Add a new bug every time tests fails. It will also capture screenshot and add it as an attachment to the defect.
Some of the details in bug
1. Title – is same as the Name of the test and timestamp of its execution TestMethodName_timeStamp
2. Description – String which is passed in Assert methods. This string is same which is used in TestNG results
3. Priority – Same as the Priority of the tests
All the details above are fetched with use of ITestNGMethod testMethod = tr.getMethod() and Map parameters = testMethod.getXmlTest().getAllParameters();
I have used the information provided from following links
ReportNG is a simple HTML reporting plug-in for the TestNGunit-testing framework. It is intended as a replacement for the default TestNG HTML report. The default report is comprehensive but is not so easy to understand at-a-glance. ReportNG provides a simple, colour-coded view of the test results.
Steps to use the plugin
1. Download the plugin from http://reportng.uncommons.org/
2. Add the downloaded jars in the class-path
3. Add following the ant target
<testng classpathref=”TestNgSelenium.classpath”
outputDir=”outputFromAnt”
haltOnfailure=”true”
useDefaultListeners=”false”
listeners=”org.uncommons.reportng.HTMLReporter,org.uncommons.reportng.JUnitXMLReporter”>
<xmlfileset dir=”.” includes=”testng.xml”/> <sysproperty key=”org.uncommons.reportng.title” value=”My Test Report”/>
</testng>
useDefaultListeners – This will disable the default the TestNG reports
reportslisteners – Will use the new plugin
Following is the example of sample report :- http://reportng.uncommons.org/sample/index.html
In this post I’m trying to suggest the steps which can help in performing automation from scratch.
All the above questions will help do the next step
What is Automated Software Testing?
Automation testing is creating another software another for