TesterHQ - The Evil Tester Blog Aggregator

Jul 29, 2016 - 2 minute read - Selenium Simplified Blog WebDriver

First impressions of Selenium WebDriver 3.0.0 beta 1

TLDR; Selenium 3 WebDriver is pretty much a drop in replacement for Selenium 2 WebDriver The 3.0.0 Beta v1 version of WebDriver has been released and my first Impressions of Selenium 3 beta are very good. And first impressions means, can I run the stuff I have already. I amended the pom.xml to bring the release down from maven central. <!-- <webdriver.version>2.53.1</webdriver.version> --> <webdriver.version>3.0.0-beta1</webdriver.version> So I effectively included it as

Jul 29, 2016 - 2 minute read - Selenium Simplified Blog WebDriver

Comparing WebDriver 2.53.1 execution for Firefox, Chrome, IE, HTMLUnit, Edge and Marionette

The Selenium 2 WebDriver with Java course has a new Continuous Integration section. Instead of using SVN we now use Git and have the source for the CI experimentation in Git (more info on this update). As part of this process I ran all the tests on all current versions of browsers to see the status. I last performed this type of retrospective back on (WebDriver 2.42.2](http://seleniumsimplified.com/2014/06/a-quick-webdriver-2-42-2-retrospective/) And boy have things changed with WebDriver 2.

Jul 29, 2016 - 2 minute read - CompendiumDev training

July 28th 2016 updates to online Selenium WebDriver with Java course

July 28th 2016 updates to the Selenium WebDriver API with Java Course Continuous Integration section now uses Git and all new videos Continuous Integration section uses a dedicated github project to make it easy https://github.com/eviltester/wdci New videos showing Microsoft Edge WebDriver Updated Suites Continuous Integration section now uses Git and all new videos I completely changed the Continuous Integration section. The old section was based on SVN, and used the main source code base.

Jul 24, 2016 - 3 minute read - Java Selenium Simplified Blog WebDriver

Using Intellij to debug @Test with the 'Watch' function

I was sent a query about why a cookies test was failing on Chrome but not on Firefox. The debug process involved me using techniques that I don’t think I have blogged about or demonstrated before so I repeated the debug session for a video and have written it up here. Essence: Run test on Firefox to make sure it does work Change Run configuration in IntelliJ to configure Chrome as the browser Breakpoints on relevant lines Add a watch that uses ‘code’ not just a variable name Step through the code comparing my expectations with the actual values shown in the variables and watch view I have a Driver class, which allows me to configure which driver I use by a method call, or environment variables or properties.

Jul 22, 2016 - 2 minute read - Selenium Simplified Blog WebDriver

Appium - a very short getting started guide

I recently amended the Selenium WebDriver API with Java online training to include a section on Appium with Android. In essence, Appium for mobile web testing is pretty simple, you simply use RemoteWebDriver to connect to the Appium server. Use the capabilities to setup the remote webdriver. DesiredCapabilities capabilities = new DesiredCapabilities(); capabilities.setCapability("deviceName", "emulator-5554"); capabilities.setCapability("platformName", Platform.ANDROID); // if you are using an up to date version of android to you can use "Chrome" as the app, // otherwise "browser" is the default 'browser' on Android capabilities.

Jul 22, 2016 - 2 minute read - Evil Tester Technical Testing

We test REST even if it isn't REST

The Microsoft REST guidelines are being critiqued for not being particularly RESTful. Pretty much every team I’ve worked on has had arguments about their implementation of REST APIs. Versioning? URI formats? Query strings or paths? Which return code? Support OPTION? Custom headers? Those discussions are important for the design, but sometimes people get hung up on disagreements about theory. The theory is important. We should read it, but at some point we have to make a decision about the implementation that works for us.

Jul 22, 2016 - 4 minute read - Evil Tester Productivity

On Workarounds and Fixes

TLDR: fixes are important. when we have work to do, sometimes a workaround is more important One of the skills I think we develop when working with software is a search for workarounds. I was reminded of that this morning when the start button on Windows 10 refused to work. The start menu would not appear in response to the windows key, nor could I click on it. The search for a fix

Jul 22, 2016 - 2 minute read - CompendiumDev training

Recent updates to our online training courses

July has been a busy month for updates to our online training courses. Updates to: Selenium WebDriver API with Java Technical Web Testing 101 Selenium WebDriver API with Java has been updated: to reflect the changes made to Firefox Driver and Marionette And also has a new section on Appium on Android The Appium section shows how to setup Virtual Machines, use Appium on real devices and configuring Remote Web Driver to use an Appium Server.

Jul 20, 2016 - 5 minute read - Java Selenium Simplified Blog WebDriver

How to investigate and debug a Selenium WebDriver `@Test` error

Here’s the situation. You’ve written some code to automatically execute your application. You’re using Selenium WebDriver. Bam. Something goes wrong. You don’t know what to do. Do you: A) investigate? B) ask someone else to fix your problem? If you answered B to the question above, then in this post I’ll show you some strategies to help with (A). You do have to develop the skills to investigate your own issues.

Jul 19, 2016 - 4 minute read - IntelliJ Java For Testers JUnit

How to debug Java with IntelliJ: breakpoints, evaluate expression, watches and variable view

I have deliberately created a failing test. Obviously deliberately since I would never ever create such simple issues in code. I’m far too experienced for that. :) Even though these issues were created deliberately I still need to know how to debug code. In this blog post I’ll describe how I debug Java using IntelliJ. You can also ‘watch’ this post on YouTube I have some code which fills a dynamic array with “*” to simulate a set of ‘pixels’ - whatever.