Go gaga over Machine Learning

Gwen Stefani! Not really :) Gwen: The tool that claims to reduce the development effort when testing using selenium in a BDD(Gherkin) fashion. Attending a meetup by the developer(Branko Juric) himself here Quoting the details: " Automating tests with Selenium WebDriver is a very developer centric activity. But what if you could express the expected behavior of a feature in a standard business language instead and have an interpreter translate and evaluate it for you? This session will introduce and demonstrate an open source automation tool called Gwen that allows you to compose executable tests in a way that frees you from the development concerns typically associated with automation. It will also show you how Gwen can help BDD practices and Agile teams rapidly accelerate their UI testing. As a user of this tool, you no longer need to write any code that interacts with Selenium, develop any page objects, or build any test frameworks at all. " I thought let me...

Some of us here are working on the BDD guidelines that should be followed: Would be interested to hear if anyone has thoughts to share: Guidelines Explain in the feature file what the feature is about, just after the “Feature: ” before proceeding to the scenarios (preferably in “In order/As a/I want” format). Write high-level scenario steps by raising the level of abstraction and focus on the “what” rather than the “how” don’t mention UI elements don’t mention ‘click’ or other actions linked to specific UI elements the scenario should remain valid if the UI is replaced with a new UI tomorrow avoid very detailed steps where possible (helps to focus and avoid clutter) Write scenarios using business language rather than using technical language so that it can be understood by everyone. Write scenarios from the perspective of the person who will use or needs the feature (not always a member or user). Use 'I' and explain who the 'I' is in 'Given' s...

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