Metadata-Version: 1.1
Name: green
Version: 0.9.9.9.4
Summary: Green is a clean, colorful test runner for Python unit tests.  Compare it to nose or trial.
Home-page: https://github.com/CleanCut/green
Author: Nathan Stocks
Author-email: nathan.stocks@gmail.com
License: MIT
Download-URL: https://github.com/CleanCut/green/tarball/0.9.9.9.4
Description: Green
        =====
        
        Clean, colorful test runner for Python
        --------------------------------------
        
        Green is a clean, colorful test runner for Python unit tests.  Compare it to
        nose or trial.
        
        Green grew out of a desire to see pretty colors.  Really!  A big part of the
        whole the **Red/Green/Refactor** process in test-driven-development is
        _actually getting to see red and green output_.  Most python unit testing
        actually goes **Gray/Gray/Refactor** (at least on my terminal, which is gray
        text on black background).  That's a shame.  Even TV is in color these days.
        Why not terminal output?  Even worse, the default output for most test runners
        is cluttered, hard-to-read, redundant, and the dang statuses are not aligned
        vertically!  Green fixes all that.
        
        ### Features ###
        
        - Colored terminal output with vertically-aligned status indicators
        - FAST -- experimental support for running tests independent subprocesses
        - Test auto-discovery
        - No new objects to learn -- just use normal `unittest` classes.
        - Optional HTML output
        - Four verbosity levels
        - Built-in, optional, integration with
          [coverage](http://nedbatchelder.com/code/coverage/)
        - Supports Python 2.7, 3.3, 3.4, and [PyPy](http://pypy.org)
        - Completely supports OS X and Linux, most likely BSDs (and maybe Windows,
          someone want to try it and let me know?)
        
        
        Basic Usage
        -----------
        
        The simplest way is to just run `green your_project_dir` in the parent
        directory of your project.  (For convenience, you can also use `greenX` or
        `greenX.Y`, where `X` and `Y` are the major and minor version number of your
        Python installation.)
        
        If your tests are extremely simple (don't attempt absolute imports), or if you
        carefully set up your `PYTHONPATH` environment variable to include the parent
        path of your project, you may be able to just run `green` from _inside_ your
        project directory.
        
        By default, Green mimics the verbosity levels of vanilla unittest or nose,
        meaning that output is mostly just dots.  For Green we recommend adding more
        verbosity by using the `-v` or `-vv` options.
        
        To run Green's own internal unit tests (which are hopefully all passing):
        
            green -v green
        
        To see all examples of all the failures, errors, etc. that could occur:
        
            green -v green.examples
        
        
        Advanced Usage
        --------------
        
        Please see `green --help`
        
        
        Install
        -------
        
        Replace `pip3` with your version of pip if necessary.  You may need to prepend
        this command with `sudo` or run it as root if your normal user cannot write to
        the local Python package directory.
        
            pip3 install green
        
        
        Upgrade
        -------
        
            pip3 install --upgrade green
        
        Wait...what do I have installed?
        
            green --version
        
        
        Uninstall
        ---------
        
            pip3 uninstall green
        
        Unit Test Structure Tutorial
        ----------------------------
        
        This tutorial *does* cover:
        
        - External structure of your project (directory and file layout)
        - Skeleton of a real test module
        - How to import stuff from from your project into your test module
        - Gotchas about naming...everything.
        - Where to run green from and what the output could look like.
        
        This tutorial *does not* cover:
        
        - Stupid, useless examples like _all-your-code-and-tests-in-one-file_.
        - [Why you should write unit tests at
          all](http://stackoverflow.com/questions/67299/is-unit-testing-worth-the-effort)
        - The benefits of [Test-Driven
          Development](http://en.wikipedia.org/wiki/Test-driven_development)
        - How to use the [unittest](https://docs.python.org/library/unittest.html) module.
        - How to write
          [good](http://stackoverflow.com/questions/61400/what-makes-a-good-unit-test)
          unit tests.
        
        ### External Structure ###
        
        This is what your project layout should look like with just one module in your
        package:
        
        
            proj                  # 'proj' is the package
            ├── __init__.py
            ├── foo.py            # 'foo' (or proj.foo) is the only "real" module
            └── test              # 'test' is a sub-package
                ├── __init__.py
                └── test_foo.py   # 'test_foo' is the only "test" module
        
        Notes:
        
        1. There is an `__init__.py` in every directory.  Don't forget it.  It can be
           an empty file, but it needs to exist.
        
        2. `proj` itself is a directory that you will be storing somewhere.  We'll
           pretend it's in `/home/user`
        
        3. The `test` directory needs to start with `test`.
        
        4. The test modules need to start with `test`.
        
        
        When your project starts adding code in sub-packages, you will need to make a
        choice on where you put their tests.  I prefer to create a `test` subdirectory
        in each sub-package.
        
            proj
            ├── __init__.py
            ├── foo.py
            ├── subpkg
            │   ├── __init__.py
            │   ├── bar.py
            │   └── test              # test subdirectory in every sub-package
            │       ├── __init__.py
            │       └── test_bar.py
            └── test
                ├── __init__.py
                └── test_foo.py
        
        
        The other option is to start mirroring your subpackage layout from within a single test directory.
        
            proj
            ├── __init__.py
            ├── foo.py
            ├── subpkg
            │   ├── __init__.py
            │   ├── bar.py
            └── test
                ├── __init__.py
                ├── subpkg            # mirror sub-package layout inside test dir
                │   ├── __init__.py
                │   └── test_bar.py
                └── test_foo.py
        
        
        ### Skeleton of Test Module ###
        
        Assume `foo.py` contains the following contents:
        
        ```python
        def answer():
            return 42
        
        class School():
        
            def food(self):
                return 'awful'
        
            def age(self):
                return 300
        ```
        
        Here's a possible version of `test_foo.py` you could have.
        
        ```python
        # Import stuff you need for the unit tests themselves to work
        import unittest
        
        # Import stuff that you want to test.  Don't import extra stuff if you don't
        # have to.
        from proj.foo import answer, School
        
        # If you need the whole module, you can do this:
        #     from proj import foo
        #
        # Here's another reasonable way to import the whole module:
        #     import proj.foo as foo
        #
        # In either case, you would obviously need to access objects like this:
        #     foo.answer()
        #     foo.School()
        
        # Then write your tests
        
        class TestAnswer(unittest.TestCase):
        
            def test_type(self):
                "answer() returns an integer"
                self.assertEqual(type(answer()), int)
        
            def test_expected(self):
                "answer() returns 42"
                self.assertEqual(answer(), 42)
        
        class TestSchool(unittest.TestCase):
        
            def test_food(self):
                school = School()
                self.assertEqual(school.food(), 'awful')
        
            def test_age(self):
                school = School()
                self.assertEqual(school.age(), 300)
        ```
        
        Notes:
        
        1. Start all your test class names with `Test`, and always subclass `unittest.TestCase`
        
        2. Start all your test method names with `test`.
        
        3. What a test class and/or its methods _actually test_ is entirely up to you.
           In some sense it is an artform.  Just use the test classes to group a bunch
           of methods that seem logical to go together.
        
        4. The methods of `TestAnswer` have docstrings, while the methods on
           `TestSchool` do not.  For most output modes, green will use the method
        docstring to describe the test if it is present, and the name of the method if
        it is not.  Notice the difference in the output below.
        
        ### Running Green ###
        
        To run the unittests, we would change to the parent directory of the project
        (`/home/user` in this example) and then run `green proj`.
        
        **In a real terminal, this output is syntax highlighted**
        
            $ green proj
            ....
            Ran 4 tests in 0.000s
        
            OK (passes=4)
        
        Okay, so that's the classic short-form output for unit tests.  Green really
        shines when you start getting more verbose:
        
        **In a real terminal, this output is syntax highlighted**
        
            $ green -v proj
            test.test_foo
              TestAnswer
            .   answer() returns 42
            .   answer() returns an integer
              TestSchool
            .   test_age
            .   test_food
        
            Ran 4 tests in 0.001s
        
            OK (passes=4)
        
        Notes:
        
        1. Green outputs clean, heirarchical output.
        
        2. Test status is aligned on the _left_
        
        3. Method names are replaced with docstrings when present.
        
        4. Green always outputs a summary of statuses that will add up to the total
           number of tests that were run.  For some reason, many test runners forget
           about statuses other than Error and Fail, and even the built-in unittest runner
           forgets about passing ones.
        
        5. Possible values for test status (these match the `unittest` short status characters exactly)
         - `.` Pass
         - `F` Failure
         - `E` Error
         - `s` Skipped
         - `x` Expected Failure
         - `u` Unexpected pass
        
Keywords: nose,nose2,trial,tox,green,test,tests,functional test,system test,unit test,unittest,color,tabular,clean,red,rednose
Platform: UNKNOWN
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Operating System :: MacOS :: MacOS X
Classifier: Operating System :: Microsoft :: Windows
Classifier: Operating System :: POSIX
Classifier: Operating System :: POSIX :: Linux
Classifier: Operating System :: Unix
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Software Development :: Libraries
Classifier: Topic :: Software Development :: Quality Assurance
Classifier: Topic :: Software Development :: Testing
Classifier: Topic :: Utilities
