How to Test

Test Locally

You can test mkdocs-tacc locally with PIP or Poetry.

You can test mkdocs-tacc clients the same way; some also support Docker and Make. *

PIP

Ensure PIP is updated; 21.3+ recommended:
```
pip install --upgrade pip
```

To install dependencies and serve docs in isolation:

python -m venv venv
source venv/bin/activate
pip install -e .
mkdocs serve

To deactivate environment: deactivate

To remove environment: rm -rf venv

Poetry

Ensure Poetry is updated; 1.5.0+ recommended:
```
poetry self update
```
To install dependencies and serve docs in isolation:
```
poetry install --sync
poetry run mkdocs serve
```

To deactivate environment: exit

To remove environment: poetry env remove --all

* Docker

Ensure Docker is updated; 20.10.0+ recommended:
```
docker --version
```
Only checks version. Upgrade differs per platform.
To install dependencies and serve docs in isolation:
```
docker compose up
```

To deactivate environment: docker compose stop

To remove environment: docker compose down

* Make

Ensure Make is available:
```
make --version
```
Only checks version. Upgrade differs per platform.
To install dependencies and serve docs in isolation:
```
make start
```

To deactivate environment: Ctrl+C

To remove environment: make stop

Some clients will offer automatic, remote build and deploy for testing.

To test changes end-to-end on client repository:

Install the theme at a specific version —

PIP

pip install mkdocs-tacc==0.5.0

Poetry

poetry add mkdocs-tacc@0.5.0

— or a specific branch –

PIP

pip install "mkdocs-tacc[all] @ git+https://github.com/TACC/mkdocs-tacc.git#work-in-progress"

Poetry

poetry add "mkdocs-tacc[all] @ git+https://github.com/TACC/mkdocs-tacc.git#work-in-progress"

— or other revision.

To test changes real-time on client repository: