TestMultipleExtensionsWithInput ensures multiple extension calls each using {{input}} get proper substitution.

TestNestedInputInExtension tests the original bug case: {{ext:name:op:{{input}}}} should pass the actual input, not the sentinel

--- Client Tests ---

Test generated using Keploy

Test generated using Keploy

An upstream redirect must show as an upstream error. The client must not go to the redirect target with the API key.

Malformed client JSON is a client error. The answer is a 400 with a stable generic message, not a 500.

With no configured key, the forwarded request must not contain the header.

An upstream that is not available is a 500. The body must not contain the raw transport error, because that error shows the internal upstream URL.

Rename must reject a file-path-like destination, the same as Save. The inherited StorageEntity.Rename accepts such a destination.

Save must reject a name that loadPattern uses as a filesystem path, and that includes a traversal name. For such a name, GetApplyVariables reads from

Save must not write through a symlinked pattern directory or a symlinked pattern file that points outside the storage tree.

A pattern backend failure must use the shared storageError mapping. That is a JSON envelope with the generic message, never the wrapped os.PathError.

A non-loopback bind without an API key must fail closed before the server starts. A loopback bind operates without a key.

--- ISC-C17: Negative Test Cases ---

--- Integration Test: Send with mock HTTP server ---

Test generated using Keploy

TestSentinelInVariableProcessing tests that the sentinel token is handled correctly in regular variable processing (not just extensions) Note: The sen

TestSentinelTokenReplacement tests the fix for the {{input}} sentinel token bug This test verifies that when {{input}} is used inside an extension cal