Go gaga over Machine Learning

Here is an excellent article on how we can have efficient test scripts in the selenium world Use few and fast locators Use only Explicit waits Write good atomic tests Use the Chrome Driver Use Headless browser drivers Re-use the browser instance Run scripts in parallel Use HTTP-parse libraries like JSoup Pre-populate cookies Do not load images Read the entire article here: Source:  http://www.beacon.by/test-automation-for-manual-testers/10-tips-for-faster-selenium-scripts#/4

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 steps GNU 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.

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 Source:  http://zeroturnaround.com/rebellabs/java-tools-and-technologies-landscape-for-2014/

A good one to watch: Source: http://www.stickyminds.com/interview/challenges-testing-internet-things-starwest-2015-interview-paul-gerrard

If we choose to make TestNG as the testing library in our automation framework , we can easily do that with the Eclipse/IntelliJ Plugins: http://testng.org/doc/migrating.html Excellent report on converting an entire project from jUnit to TestNG https://developers.opengamma.com/blog/2011/04/04/converting-opengamma-junit-testng Use case JUnit 4 TestNG Comment Method is a test @Test @Test Simply change the import Class is a test N/A @Test We decided to stick with per method annotations in the end Test 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 method An exception is expected @Test (expected =IOException.class) @Test (expectedExceptions =IOException.class) Simple spelling change Test timeout @Test(timeout =20000) @Test(timeOut=20000) Simple spelling change Run before/after each test method @Before/@After @BeforeMethod/ @AfterMethod C

Every automation tester should read this: https://www.linkedin.com/pulse/problem-automation-testers-steve-walton?trk=hp-feed-article-title-like Source: Steve Walton