☄️
kallisto docs
  • Featurizer and Modelling Helper
  • Setup and Installation
  • Testing suite
  • Check the Examples
  • Features
    • Coordination Numbers
    • Proximity Shells
    • Partial Charges
    • Polarizabilities
    • van-der-Waals Radii
    • Sterimol
  • Modelling
    • Breadth First Sorting
    • Root Mean Square Deviation
    • Substructure Finder
    • Substructure Exchanger
  • Misc
    • Need Help
    • License
Powered by GitBook
On this page
  • Default nox session
  • Tests
  • Lint
  • Black
  • Safety
  • Mypy
  • Pytype
  • Coverage

Was this helpful?

Testing suite

PreviousSetup and InstallationNextCheck the Examples

Last updated 4 years ago

Was this helpful?

The kallisto project uses as an automated unit test suite, which is therefore an additional dependency.

Default nox session

The default session includes: linting (lint), type checks (mypy, pytype), and unit tests (tests).

> nox

When everything runs smoothly through, you are ready to go! After one successful nox run, we can reuse the created virtual environment via the -r flag.

> nox -r

Sometimes conda and nox are getting in their ways, which could lead to a failure while running unit tests. When facing such a case, deactivate the virtual environment and try again.

Different unit test sessions are implemented (check the ). They can be called separately via the run session -rs flag.

Tests

Run all unit tests that are defined in the directory.

> nox -rs tests

Lint

kallisto uses the linter (check the config file).

> nox -rs lint

Black

> nox -rs black

Safety

> nox -rs safety

Mypy

> nox -rs mypy

Pytype

> nox -rs pytype

Coverage

> nox -rs coverage

kallisto uses the code formatter.

kallisto checks the security of dependencies via .

kallisto checks for static types via (check the config file).

kallisto furthermore uses for type checks.

Unit test can be checked as well.

nox
noxfile.py
/tests
flake8
.flake8
black
safety
mypy
mypy.ini
pytype
coverage