mirror of
https://github.com/Brandon-Rozek/website.git
synced 2025-10-10 06:51:13 +00:00
New blog posts
This commit is contained in:
parent
3b69b7e465
commit
9329d8a605
3 changed files with 101 additions and 0 deletions
32
content/blog/tox.md
Normal file
32
content/blog/tox.md
Normal file
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
title: "Tox"
|
||||
date: 2020-02-21T22:34:19-05:00
|
||||
draft: false
|
||||
tags: [ "python", "testing" ]
|
||||
---
|
||||
|
||||
[Tox](https://tox.readthedocs.io/en/latest/) is a great project where you can automate your testing using virtual environments.
|
||||
|
||||
First install tox
|
||||
```bash
|
||||
pip install tox
|
||||
```
|
||||
|
||||
I like to write my tests in Python's native [`unittest`](https://docs.python.org/3/library/unittest.html) format. Tests should be stored in a `tests` directory.
|
||||
|
||||
I then combine it with the `coverage` library to tell me how much of my code that my test cases cover. To quickly insert my personal opinion, I never aim for 100% test coverage since there's typically overhead in maintaining that.
|
||||
|
||||
This all gets described in a `tox.ini` file. This file should live in the same directory as your `setup.py`
|
||||
|
||||
```ini
|
||||
[tox]
|
||||
envlist =
|
||||
py38
|
||||
|
||||
[testenv]
|
||||
deps = coverage
|
||||
commands =
|
||||
coverage run --source=tests,library -m unittest discover tests
|
||||
coverage report -m
|
||||
```
|
||||
|
Loading…
Add table
Add a link
Reference in a new issue