Posts

Showing posts with the label Java

Cheatsheet from Java to C# to Swift to VS2017

Image

Tools and technologies - Test Automation awesomeness - Java

Image
Here is a quick overview of the top 6 programming languages used and the various flavors of testing: Let's start with Java: 1.  Java Happy Java Testing!

slf4j failed to load class

Image
Problem:  If you are getting this error message every time you run your slf4j failed to load class framework org.slf4j.impl.staticloggerbinder Solution: If you use maven just add the following Happy Testing!

Open Source Test Automation Frameworks

Image
Every-time I read Joe Colantonio's posts I learn something new and this time it was a newbie called Gauge. If you don't know what it is here are the 6 opensource frameworks Joe talks about: Serenity (Formally Thucydides) Robot Framework RedwoodHQ Sahi Galen  Framework Gauge Update:  Two more to the list: An old one  Open2Test New:  Extensive Testing Further Reading:  http://www.joecolantonio.com/2016/05/10/6-open-source-test-automation-frameworks-need-know/

Java Build Tools + Dependency Management for Test Automation

Image
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 acce...

Java tools and technologies - Automation

Image
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/

LeanFT - Proof of Concept

Image
Findings and POC for using LeanFT as part of the Contentious Integration build: LeanFT uses the UFT SDK  Allows coding your tests in C# and Java in your favorite IDE (documentation is focused around Visual Studio and Eclipse) Any add-in can be automated Standard Windows, WPF, .NET, Mobile etc.. Prerequisite: You should now see:  C:\Program Files (x86)\HP\LeanFT\bin Browser Prerequisite: In the Firefox browser menu, select Add-ons and then click Extensions. Drag the Agent.xpi file from the%LeanFT%\Installations\Firefox folder to the Firefox Extension page and click ‘Install now’. If you are testing against Chrome ensure the LeanFT plugin is enabled from Chrome Settings -> Extensions. With IE, go to Settings -> Manage Addons where HP Functional Testing Agent must be enabled. Download the sdk jars/dll: https://github.com/upgundecha/lftexamples SDK reference: http://leanft-help.saas.hp.com/en/latest/JavaSDKReference/index.html

Complete list of Serenity properties

Image
The Serenity Reference Manual: http://thucydides.info/docs/serenity-staging/ Serenity properties Absolute path of the property file where Serenity system property defaults are defined. Defaults to ~/serenity.properties webdriver.driver What browser do you want your tests to run in, for example firefox, chrome, phantomjs or iexplorer. You can also use the  driver  property as a shortcut. webdriver.provided_type If using a provided driver, what type is it. The implementation class needs to be defined in the webdriver.provided.{type} system property. webdriver.base.url The default starting URL for the application, and base URL for relative paths. webdriver.remote.url The URL to be used for remote drivers (including a selenium grid hub or SauceLabs URL) phantomjs.webdriver.port What port to run PhantomJS on (used in conjunction with webdriver.remote.url to register with a Selenium hub, e.g. -Dphantomjs.webdriver=5555 -Dwebdriver.remote.url=http://loca...