Skip to content

Latest commit

 

History

History
53 lines (32 loc) · 1.44 KB

README.md

File metadata and controls

53 lines (32 loc) · 1.44 KB
Raw

Inspiration

I'm working on a small codebase. I've been asked to make a few updates, and the first couple changes worked OK, however I'm having trouble debugging the latest change. I need to be able to make small updates with confidence.

Conclusions

  • Small same file unit and async unit tests should be enough to keep troubleshooting and debugging simple, for now.
  • A few infrastructure tests may be useful to catch simple mistakes in my dockerfile.
  • I don't think Fuzz tests and API response mocking are needed while this project is so small.

Everything except fuzz tests are runnable from pytest.

How to activate virtual env

source venv/bin/activate

How to run fuzz tests:

py-afl-fuzz -m 600 -i fuzzing-inputs/ -o fuzzing-results/ -- python lib/example_fuzzing.py @@

lib/example_fuzzing.py

How to run infrastructure tests:

pytest ./

test_local_infra_example.py

test_dockerinfra.py

How to run unit tests:

pytest examples/*

examples/example_unit_test_same_file.py

examples/example_test_with_api_response_fixture.py

examples/example_async_test.py # pytest-aio does not require any extra setup

Future examples (TODO):

  • Auto mocking, spy, stubbing 3rd party libs
  • Snapshot testing