<commit_before>---
layout: post
author: tooky
title:  "Hands-on with the Cucumber Ruby Events API"
date:   2015-09-14 00:00:00
nav: blog
---

[Cucumber Ruby 2.1][cuke-2.1] introduces the new [Events API][events] &mdash; a simple way to find out what's happening while Cucumber runs your features. Events are read-only and simplify the process of writing formatters, and other output tools.

I'll illustate how to use the API with a worked example that streams Cucumber test results to a browser in real-time.

## Can you give me an example?<commit_msg>Fix typo<commit_after>---
layout: post
author: tooky
title:  "Hands-on with the Cucumber Ruby Events API"
date:   2015-11-20 09:00:00
nav:    blog
---

[Cucumber Ruby 2.1][cuke-2.1] introduces the new [Events API][events] &mdash; a simple way to find out what's happening while Cucumber runs your features. Events are read-only and simplify the process of writing formatters, and other output tools.

I'll illustrate how to use the API with a worked example that streams Cucumber test results to a browser in real-time.

## Can you give me an example?
{'fraction_non_alphanumeric': 0.0815956482320943, 'fraction_numerical': 0.032638259292837715, 'mean_word_length': 4.134883720930232, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5560349', 'n_tokens_mistral': 359, 'n_tokens_neox': 328, 'n_words': 162}