In this talk, we'll discuss:

• How Erlang's concurrency makes it easier to write robust programs
• Elixir's approachable syntax
• How to test Erlang and Elixir programs using Cucumberl

Attendees will walk away with a solid introduction to the principles of Erlang, and an appreciation of the way Elixir brings the joy of Ruby to the solidity of the Erlang runtime.

Join Ian Dees in this session, as we cover the following topics.

• Connecting to an Arduino using a custom serial protocol
• Taking advantage of the TCP stack when it's available
• Building the Cucumber wire protocol into your device
• What to do when you can't modify the app under test
• Driving more fully-featured devices such as the BeagleBone or RaspberryPi

By the end of the presentation, you'll have a handle on what the various options are for testing embedded devices, and which tradeoffs will apply to your system

This is not a matter of dumbing things down. There is a synergy between the expressiveness of tests and the maintainability. Achieving clarity in natural language is essential for their long-term viability.

One of the most powerful things Cucumber can do for a software team is help them grow a ubiquitous language. But this depends on scenarios having the right level of detail at the right level of abstraction to be expressive to business people, testers, and developers alike.

Cucumber gives us Scenarios and Step Definitions and leaves the rest up to us. Over time we have discovered that placing all of our code in Step Definitions tends to lead to brittle tests - especially in very large projects.

In this session we find out how Oscar adopted Cucumber, WebDriver, as well as automating everything he possibly could, to successfully reduced our regression from 160+ automation with QTP and 80+ hour manual to 7 minutes full regression.

We’ve all been there. You work incredibly hard to develop a feature and design tests based on written requirements. You build a detailed test plan that aligns the tests with the software and the documented business needs. When you put the tests to the software, it all falls apart because the requirements were updated without informing everyone.

But help is at hand. Enter business-driven development and Cucumber, a tool for running automated acceptance tests.

By fostering collaboration for implementing active requirements via a common language and format, Cucumber bridges the communication gap between business stakeholders and implementation teams. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, be here!