Showing posts from March, 2016

Tips for faster test automation - Selenium

Here is an excellent article on how we can have efficient test scripts in the selenium world

Use few and fast locatorsUse only Explicit waitsWrite good atomic testsUse the Chrome DriverUse Headless browser driversRe-use the browser instanceRun scripts in parallelUse HTTP-parse libraries like JSoupPre-populate cookiesDo not load images Read the entire article here:

Java Build Tools + Dependency Management for Test Automation

Build Tools - History: 
Save developers some time typing commands that would have many source code modules compiled and linked in a particular order. First build tool was Make a scripting language that allowed a build script to be written as a series of compile-and-link stepsGNU version of Make offered additional features, such as dependency management and incremental building

Java now has Maven, Gradle, Ant and some others (like Scala’s Simple Build Tool–SBT)
Ant Ant was the first of the so-called “modern build tools”, and is used for automating build process. In theory, it is kind of like Make, without Make’s wrinkles. It is implemented in Java and used mostly for Java projects. The first public release of Ant was in 2000, and it quickly became most popular build tool for Java projects thanks to being platform independent (like Java), having low barriers for getting set up, and providing repeatable builds. Later, it also gained the ability to accept plugins. However, Ant was criticiz…

Java tools and technologies - Automation

Zeroturnaround does a survey on Java development and research. Here are some top technologies and how they influence the automation space as well:

Here is a complete slide deck of their research:

Java Tools and Technologies Landscape for 2014 (image gallery) from ZeroTurnaround


Repost: The Challenges of Testing the Internet of Things: STARWEST 2015 Interview with Paul Gerrard [interview]

A good one to watch:


Migration from jUnit to TestNG

If we choose to make TestNG as the testing library in our automation framework , we can easily do that with the Eclipse/IntelliJ Plugins:

Excellent report on converting an entire project from jUnit to TestNG

Use caseJUnit 4TestNGCommentMethod is a test@Test@TestSimply change the importClass is a testN/A@TestWe decided to stick with
per method annotations
in the endTest is disabled@Ignore@Test(enabled=false)@Ignore on the class
disables all tests
 in the class, whereas @Test
(enabled = false) on the class
doesn't override @Test
on a methodAn exception is expected@Test
=IOException.class)Simple spelling changeTest timeout@Test(timeout
=20000)@Test(timeOut=20000)Simple spelling changeRun before/after each test method@Before/@After@BeforeMethod/
@AfterMethodClearer annotation nameRun before/after each test method@BeforeCla…

The problem with Automation Testers is...