<commit_before>RestKit Spec Environment
========================

RestKit ships with a testing infrastructure built around UISpec and
an associated Ruby Gem called UISpecRunner. To be able to run the
tests, you need to do a little bit of setup:

1. Install the Ruby Bundler Gem (if necessary): `sudo gem install bundler`
1. Install the other required Gems via Bundler: `bundle`
1. Start the spec server: `rake uispec:server`
1. Verify the configuration by running the specs: `uispec -v`

If the project builds the Specs target correctly and executes the suite, then
you are all set. If there are any issues, you may need to reach out to the mailing
list for help debugging.

Once your spec environment has been configured and set up, you can run the entire suite
by executing `rake` or `uispec`.

Running Specs
-------------

UISpecRunner is both a library and a general purpose CLI runner. The library works
by plugging into the application and executing specs as configured by some environment
variables.

You can use the `uispec` executable to target and run specific specs or grouping of specs
(i.e. unit, functional, integration):

* Run all specs: `uispec`
* Run a specific spec class: `uispec -s RKClientSpec`
* Run a specific spec example: `uispec -s RKClientSpec -e itShouldDetectNetworkStatusWithAHostname`
* Run all specs conforming to a protocol: `uispec -p UISpecUnit`

Common spec groupings (i.e. Units and Integration) are configured for execution via the Rakefile. Execute
`rake -T` for a full listing of the pre-configured spec groups available.

Writing Specs
-------------<commit_msg>Updated testing Doc to use bundle exec<commit_after>RestKit Spec Environment
========================

RestKit ships with a testing infrastructure built around UISpec and
an associated Ruby Gem called UISpecRunner. To be able to run the
tests, you need to do a little bit of setup:

1. Install the Ruby Bundler Gem (if necessary): `gem install bundler`
1. Install the other required Gems via Bundler: `bundle`
1. Start the spec server: `rake uispec:server`
1. Verify the configuration by running the specs: `uispec -v`

If the project builds the Specs target correctly and executes the suite, then
you are all set. If there are any issues, you may need to reach out to the mailing
list for help debugging.

Once your spec environment has been configured and set up, you can run the entire suite
by executing `rake` or `uispec`.

Running Specs
-------------

UISpecRunner is both a library and a general purpose CLI runner. The library works
by plugging into the application and executing specs as configured by some environment
variables.

You can use the `uispec` executable to target and run specific specs or grouping of specs
(i.e. unit, functional, integration):

* Run all specs: `bundle exec uispec`
* Run a specific spec class: `bundle exec uispec -s RKClientSpec`
* Run a specific spec example: `bundle exec uispec -s RKClientSpec -e itShouldDetectNetworkStatusWithAHostname`
* Run all specs conforming to a protocol: `bundle exec uispec -p UISpecUnit`

Common spec groupings (i.e. Units and Integration) are configured for execution via the Rakefile. Execute
`rake -T` for a full listing of the pre-configured spec groups available.

Writing Specs
-------------
{'fraction_non_alphanumeric': 0.07758094074526573, 'fraction_numerical': 0.002443494196701283, 'mean_word_length': 4.248397435897436, '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': '2705007', 'n_tokens_mistral': 885, 'n_tokens_neox': 847, 'n_words': 493}