Running the `MyClassTests` using the default unittest runner


``` {.sourceCode .console}
$ python -m unittest -v sample
test_add_one(0, 1) (sample.MyClassTests) ... ok
test_add_one(100000, 100001) (sample.MyClassTests) ... ok

----------------------------------------------------------------------
Ran 2 tests in 0.000s

OK

would be run 3 times, producing output like


``` {.sourceCode .console}
$ python -m unittest -v sample
test_adding_one() iteration_1 (sample.MyClassTests) ... ok
test_adding_one() iteration_2 (sample.MyClassTests) ... ok
test_adding_one() iteration_3 (sample.MyClassTests) ... ok

----------------------------------------------------------------------
Ran 3 tests in 0.001s

OK

There are more options to explore including naming your datasets and
`genty_args`.


``` {.sourceCode .python}
@genty_dataset(
    default_case=(0, 1),
    limit_case=(999, 1000),
    error_case=genty_args(-1, -1, is_something=False),
)
def test_complex(self, value1, value2, optional_value=None, is_something=True):
    ...

The `@genty_datasets` can be chained together. This is useful, for
example, if there are semantically different datasets so keeping them
separate would help expressiveness.


``` {.sourceCode .python}
@genty_dataset(10, 100)
@genty_dataset('first', 'second')
def test_composing(self, parameter_value):
    ...

Sometimes the parameters to a test can\'t be determined at module load
time. For example, some test might be based on results from some http
request. And first the test needs to authenticate, etc. This is
supported using the `@genty_dataprovider` decorator like so:


``` {.sourceCode .python}
def setUp(self):
    super(MyClassTests, self).setUp()

    # http authentication happens
    # And imagine that _some_function is actually some http request
    self._some_function = lambda x, y: ((x + y), (x - y), (x * y))

@genty_dataset((1000, 100), (100, 1))
def calculate(self, x_val, y_val):
    # when this is called... we've been authenticated
    return self._some_function(x_val, y_val)

@genty_dataprovider(calculate)
def test_heavy(self, data1, data2, data3):
    ...

Notice here how the name of the helper (`calculate`) is added to the
names of the 2 executed test cases.

Like `@genty_dataset`, `@genty_dataprovider` can be chained together.

Enjoy!

Deferred Parameterization
-------------------------

Parametrized tests where the final parameters are not determined until
test execution time. It looks like so:


``` {.sourceCode .python}
@genty_dataset((1000, 100), (100, 1))
def calculate(self, x_val, y_val):
    # when this is called... we've been authenticated, perhaps in
    # some Test.setUp() method.

    # Let's imagine that _some_function requires that authentication.
    # And it returns a 3-tuple, matching that signature of
    # of the test(s) decorated with this 'calculate' method.
    return self._some_function(x_val, y_val)

@genty_dataprovider(calculate)
def test_heavy(self, data1, data2, data3):
    ...

Contributing
------------

See
[CONTRIBUTING.rst](https://github.com/box/genty/blob/master/CONTRIBUTING.rst).

### Setup

Create a virtual environment and install packages -


``` {.sourceCode .console}
mkvirtualenv genty
pip install -r requirements-dev.txt

Copyright 2015 Box, Inc. All rights reserved.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.