I often have to test a prompt with a different client then what is declared in the

function

Today I have a LLMClient and a Bedrock client .. the LLMClient must be used by the product because we use a client registry to override it, but my test cases I want to use the Bedrock client. - I manually change the client to Bedrock and test - this works, but are there anyways to support this in our

test.baml

instead?

we don't have an easy way to change this just yet -- we are looking at supporting that in our new test harness, which allows more flexible test parameterization.

Sweet for now its not the end of the world - just wrote a personal linter to check that all the functions use the proper client Ideally the interface could be like this

test test_1 {
  functions [FunctionName]
  client BedrockClient
  args {
    my_first_arg 18
  }
}

yep agreed that's along the lines of what we are thinking for expanding that test block