ollama/integration
nicole pardal 5d347f6d6f
server: Consolidate embedding truncation in runner (#12730)
Currently, checking the length of prompts for embeddings to ensure
they fit in the context window (and possible truncation) occurs in
two places - the Ollama server and runner. This can lead to
inconsistencies in both the checks and reported number of tokens
processed. Since we have to do this processing in the runner, this
consolidates all of the logic there.
2025-10-27 11:59:12 -07:00
..
testdata test: add a few missing embedding models (#12661) 2025-10-16 09:36:25 -07:00
api_test.go tests: add single threaded history test (#12295) 2025-09-22 11:23:14 -07:00
basic_test.go Integration test tuning (#12492) 2025-10-08 09:51:25 -07:00
concurrency_test.go test: harden scheduler tests (#12662) 2025-10-17 08:56:44 -07:00
context_test.go test: harden scheduler tests (#12662) 2025-10-17 08:56:44 -07:00
embed_test.go server: Consolidate embedding truncation in runner (#12730) 2025-10-27 11:59:12 -07:00
library_models_test.go Integration test tuning (#12492) 2025-10-08 09:51:25 -07:00
llm_image_test.go Integration test tuning (#12492) 2025-10-08 09:51:25 -07:00
max_queue_test.go perf: build graph for next batch async to keep GPU busy (#11863) 2025-08-29 14:20:28 -07:00
model_arch_test.go test: harden scheduler tests (#12662) 2025-10-17 08:56:44 -07:00
model_perf_test.go Integration test tuning (#12492) 2025-10-08 09:51:25 -07:00
quantization_test.go Integration test tuning (#12492) 2025-10-08 09:51:25 -07:00
README.md tests: add single threaded history test (#12295) 2025-09-22 11:23:14 -07:00
utils_test.go test: harden scheduler tests (#12662) 2025-10-17 08:56:44 -07:00

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.

  1. By default, they will start the server on a random port, run the tests, and then shutdown the server.
  2. If OLLAMA_TEST_EXISTING is set to a non-empty string, the tests will run against an existing running server, which can be remote based on your OLLAMA_HOST environment 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.

Many tests use a default small model suitable to run on many systems. You can override this default model by setting OLLAMA_TEST_DEFAULT_MODEL