Join GitHub today
Plaso comes with multiple forms of automated tests:
- unit tests
- end-to-end tests
The unit tests are intended to detect issues after individual changes (change lists). Unit tests are typically small by nature and only test a specific part of the code.
The unit tests are stored in the
tests sub directory, in the same directory hierarchy as the plaso module directory, and can be run with:
The end-to-end tests are intended to test the plaso tools as a user would run them. To run the end-to-end tests you'll need:
- test runner, which is
- end-to-end tests configuration, e.g.
- test data
- reference data, to compare test output against
E.g. to run the predefined end-to-end tests:
PYTHONPATH=. python ./tests/end-to-end.py --debug -c config/end-to-end.ini
The predefined end-to-end tests are also run automatically on Travis-CI after every commit (code submit).