Metadata-Version: 2.1
Name: microtest-framework
Version: 1.0.1
Summary: Simple but powerful testing framework for Python
Home-page: https://github.com/varajala/microtest
Author: Valtteri Rajalainen
Author-email: rajalainen.valtteri@gmail.com
License: UNKNOWN
Project-URL: Documentation, https://varajala.github.io/microtest/docs/
Platform: UNKNOWN
Classifier: Programming Language :: Python :: 3
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Classifier: Topic :: Software Development :: Testing
Classifier: Topic :: Software Development :: Testing :: Unit
Classifier: Topic :: Utilities
Requires-Python: >=3.7
Description-Content-Type: text/markdown
License-File: LICENSE.txt

# microtest
Simple but powerful testing framework for Python.

<br>

## Installation

    python -m pip install microtest-framework

On Mac and Linux microtest doesn't require any external dependencies.
On Windows [colorama](https://github.com/tartley/colorama) is used to translate ANSI escape sequences to win32 calls.

Microtest currently requires Python version 3.7 or higher.

<br>

## Usage

Here's the simplest testing program you can create with microtest:
```python
import microtest


@microtest.test
def function():
    x = 10
    assert x < 0
    

if __name__ == '__main__':
    microtest.run()
```
You can run this script normally via the command line:

    python test.py

The script will produce the following output:

```
======================================================================
Started testing...
======================================================================
function ..................................................... FAILED

AssertionError on line 7:
assert 10 < 0 


----------------------------------------------------------------------
Ran 1 tests in 0.001s.

ERRORS: 0
FAILED: 1
```

<br>

## Documentation

Full source code refrence and user guide can be found [here](https://varajala.github.io/microtest/docs/).

<br>

## Contributing

To contribute new features to this project do the following steps:

  - Open a new issue explaining the new feature
  - Wait for approval
  - Fork and clone the repository to your local machine and code up the feature in a **new branch**
  - Pull request

The *wait for approval* step is there so that you don't end up coding up some feature that might
not be included into microtest. This could happen if the proposed feature is redundant, changes the
existing api too radically, or simply just is not the *right thing* to be added into microtest.

The goal is to keep this project simple and small.

**Bug fixes, documentation improvements and other minor tweaks are always welcome, no need for approval.** Just leave a pull request with the fixes done in a separate branch.


