TesterHQ - The Evil Tester Blog Aggregator

Aug 5, 2016 - 1 minute read - Selenium Simplified Blog WebDriver

Selenium WebDriver 3.0.0-beta2 and JUnit and GeckoDriver v 0.10.0

I started to have a look at Selenium WebDriver 3.0.0-beta2 And my @Test methods were running from the IDE, but not running on CI. The effect in CI was, no tests executing at all: Running TestSuite Configuring TestNG with: org.apache.maven.surefire.testng.conf.TestNG652Configurator@77468bd Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.424 sec I don’t use TestNG, I use JUnit. Since this only happened when I switched to 3.

Aug 5, 2016 - 2 minute read - Selenium Simplified Blog WebDriver

WebDriver Windows 10 Anniversary Build and Edge 14393

TLDR; if your version of Edge is not listed on the WebDriver Edge page, try the insider build. I am experimenting with Selenium WebDriver 3.0.0 beta2 at the moment - more on that later. And this morning I could not get MS Edge to work. I could not understand how the beta was affecting Edge. And then I remembered that I upgraded to Windows 10 Anniversary last night so now Edge is on a new version:

Aug 4, 2016 - 4 minute read - Selenium Simplified Blog WebDriver

Question: What is the best Page Object framework for Java?

TLDR; Q: what is the best Page Object framework? A: I don’t know. I don’t use any Question: What is the best Page Object framework for Java? And are there any tools to build Page Objects e.g. scan the page and create a class with all the @FindBy annotations on WebElements etc. Answer: I don’t know. I have not researched any Page Object frameworks. I don’t use any, and don’t recommend any.

Aug 2, 2016 - 3 minute read - Java For Testers JUnit

Is JUnit only for unit testing? What about system testing or UAT?

TLDR; We can use JUnit to execute code to support any type of testing. Question: Hi, you use Junit in the book “Java For Testers” and I thought JUnit was used for “unit testing” and “unit testing” was performed by developers , not testers. Is the purpose to learn JUnit and “unit testing” or other types of testing as well? In other words, would you recommend learning “java for Testers” to software testers who would rather not be involved in “unit testing” but rather involved in “system and UAT”?

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.