<commit_before># TeamCity Formatter

Render cucumber output in the format expected by TeamCity. This formatter is compatible with cucumber 2.0

## Installation

Add this to your test suite's Gemfile:

    gem 'teamcity_formatter'

Then execute:

    $ bundle install

Or, install it directly:

    $ gem install teamcity_formatter

## Usage

Direct cucumber to use the formatter:

    $ cucumber -f TeamCityFormatter::Formatter

## Notes

Our overall goals in writing a cucumber formatter are:

1. Generate TeamCity output from a cucumber 2 test suite
1. Passing and failing test counts should match the same counts as the standard cucumber formatter

Cucumber elements are mapped simply to TeamCity test artifacts:

Cucumber                 | TeamCity
----                     | ---
Feature                  | TestSuite
Scenario                 | Test
Sceanrio Outline Example | Test

Test failures include the stack trace of the exception which triggered the failure.

## Acknowledgements

This gem drew some code from [`cucumber_teamcity`](https://github.com/ankurcha/cucumber_teamcity/). The `cucumber_teamcity` formatter is not compatible with Cucumber 2.

Also, though we did not use code from their project, JetBrains makes available some TeamCity-related code [here](https://github.com/JetBrains/intellij-plugins/tree/master/ruby-testing/src/rb/testing/patch/bdd/teamcity), which may be of interest to others researching TeamCity Cucumber formatters.<commit_msg>Add "License" section to readme<commit_after># TeamCity Formatter

Render cucumber output in the format expected by TeamCity. This formatter is compatible with cucumber 2.0

## Installation

Add this to your test suite's Gemfile:

    gem 'teamcity_formatter'

Then execute:

    $ bundle install

Or, install it directly:

    $ gem install teamcity_formatter

## Usage

Direct cucumber to use the formatter:

    $ cucumber -f TeamCityFormatter::Formatter

## Notes

Our overall goals in writing a cucumber formatter are:

1. Generate TeamCity output from a cucumber 2 test suite
1. Passing and failing test counts should match the same counts as the standard cucumber formatter

Cucumber elements are mapped simply to TeamCity test artifacts:

Cucumber                 | TeamCity
----                     | ---
Feature                  | TestSuite
Scenario                 | Test
Sceanrio Outline Example | Test

Test failures include the stack trace of the exception which triggered the failure.

## Acknowledgements

This gem drew some code from [`cucumber_teamcity`](https://github.com/ankurcha/cucumber_teamcity/). The `cucumber_teamcity` formatter is not compatible with Cucumber 2.

Also, though we did not use code from their project, JetBrains makes available some TeamCity-related code [here](https://github.com/JetBrains/intellij-plugins/tree/master/ruby-testing/src/rb/testing/patch/bdd/teamcity), which may be of interest to others researching TeamCity Cucumber formatters.

## License

Apache License, Version 2.0
{'fraction_non_alphanumeric': 0.06068689563187729, 'fraction_numerical': 0.004668222740913638, 'mean_word_length': 3.5871559633027523, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, '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': '2577269', 'n_tokens_mistral': 838, 'n_tokens_neox': 782, 'n_words': 334}