44a6792873
Sometimes the context test results are pure emoji's Thanksgiving has too much variability, so swap for a more straight forward prompt. |
||
|---|---|---|
| .. | ||
| testdata | ||
| README.md | ||
| api_test.go | ||
| basic_test.go | ||
| concurrency_test.go | ||
| context_test.go | ||
| embed_test.go | ||
| library_models_test.go | ||
| llm_image_test.go | ||
| max_queue_test.go | ||
| model_arch_test.go | ||
| model_perf_test.go | ||
| quantization_test.go | ||
| utils_test.go | ||
README.md
Integration Tests
This directory contains integration tests to exercise Ollama end-to-end to verify behavior
By default, these tests are disabled so go test ./... will exercise only unit tests. To run integration tests you must pass the integration tag. go test -tags=integration ./... Some tests require additional tags to enable to allow scoped testing to keep the duration reasonable. For example, testing a broad set of models requires -tags=integration,models and a longer timeout (~60m or more depending on the speed of your GPU.). To view the current set of tag combinations use find integration -type f | xargs grep "go:build"
The integration tests have 2 modes of operating.
- By default, they will start the server on a random port, run the tests, and then shutdown the server.
- If
OLLAMA_TEST_EXISTINGis set to a non-empty string, the tests will run against an existing running server, which can be remote based on yourOLLAMA_HOSTenvironment variable
[!IMPORTANT] Before running the tests locally without the "test existing" setting, compile ollama from the top of the source tree
go build .in addition to GPU support with cmake if applicable on your platform. The integration tests expect to find an ollama binary at the top of the tree.