Domain is NOT malicious when Quad9 returns DNS answers. Google DNS must not be queried.

Silently handled non-dictionary returns must gracefully trigger an observable failure check.

End-to-End Live Test: Executes the full base class start() method, hits the real OpenCTI server, and verifies the DB state.

Check user playbooks are in the correct order and the robot jobs are excluded

Properties caching validation checking that static initialization calls occur once.

The file must NOT contain {page_context} — interpolation is the prompt template's job, not the static file's.

Iterate localized failure targets via subtests while verifying partial state logs.

Reproduce the exact production crash: a list containing a dict WITHOUT 'rrdata' key followed by an empty list from the pdns/reverse endpoint.

The file exists and loads into the module-level constant.

Every registered tool appears in the [Tools] section, and the hardcoded EXPECTED_TOOL_NAMES matches the live build_tools() registry. If someon

Non-printable characters (except newline) will silently confuse the LLM.

The loaded prompt content is embedded in the ChatPromptTemplate's system message, so the agent actually sees the file content at runtime.

Each planned section header appears so the structure is enforced.

System prompt must stay under 500 tokens to leave room for tool schemas and conversation history within Ollama's 8192 context window.

A required parameter without a value must raise TypeError.

Messages over the per-user limit emit RATE_LIMITED and are dropped.

6th message in the same window returns 429 with IntelOwl error envelope.

The regexes mirror React Router paths in frontend/src/components/Routes.jsx. When a frontend route changes (e.g. /jobs/:id → /analysis/:id),

Test that debug information is included in error message when debug mode is enabled.

retry_after is recalculated from the current time, so it shrinks as the window progresses.

In the final fraction of a window retry_after must still be >= 1: int() truncation would return 0 here (regression guard for the flaky failure

All parameters are configured → no error, returns queryset.