<commit_before>Fluent Unit Testing
===================

*Readable hybrid testing*

Why?
~~~~

This is an attempt to make Python testing more readable while maintaining a
Pythonic look and feel.  As powerful and useful as the `unittest`_ module is,
I've always disliked the Java-esque naming convention amongst other things.

While truly awesome, attempts to bring BDD to Python never feel *Pythonic*.
Most of the frameworks that I have seen rely on duplicated information between
the specification and the test cases.  My belief is that we need something
closer to what `RSpec`_ offers but one that feels like Python.

Where?
~~~~~~

- Source Code: https://github.com/dave-shawley/fluent-test
- CI: https://travis-ci.org/dave-shawley/fluent-test
- Documentation: https://fluent-test.readthedocs.org/

.. _unittest: http://docs.python.org/2/library/unittest.html
.. _RSpec: http://rspec.info/
<commit_msg>README: Add development environment section.<commit_after>Fluent Unit Testing
===================

*Readable hybrid testing*

Why?
~~~~

This is an attempt to make Python testing more readable while maintaining a
Pythonic look and feel.  As powerful and useful as the `unittest`_ module is,
I've always disliked the Java-esque naming convention amongst other things.

While truly awesome, attempts to bring BDD to Python never feel *Pythonic*.
Most of the frameworks that I have seen rely on duplicated information between
the specification and the test cases.  My belief is that we need something
closer to what `RSpec`_ offers but one that feels like Python.

Where?
~~~~~~

- Source Code: https://github.com/dave-shawley/fluent-test
- CI: https://travis-ci.org/dave-shawley/fluent-test
- Documentation: https://fluent-test.readthedocs.org/

Contributing
~~~~~~~~~~~~

Fluent-test uses Vincent Driessen's excellent `gitflow`_ extenion to manage
work flow through github.  Contributions are welcome as long as they follow
a few basic rules:

1. They start out life by forking the central repo and creating a new
   feature branch named *feature/my-feature* from the *develop* branch.
2. All tests pass and coverage is at 100% - **make test**
3. All quality checks pass - **make lint**
4. Issue a pull-request through github.

.. _unittest: http://docs.python.org/2/library/unittest.html
.. _RSpec: http://rspec.info/
.. _gitflow: https://github.com/nvie/gitflow
{'fraction_non_alphanumeric': 0.10777683854606931, 'fraction_numerical': 0.0038038884192730348, 'mean_word_length': 4.331081081081081, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 7, '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': '7092189', 'n_tokens_mistral': 704, 'n_tokens_neox': 671, 'n_words': 286}