You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the functional tests for Semantic Kernel spawn a separate instance of the application with the environment variable ORCHESTRATION_STRATEGY set to semantic_kernel. However, following #873 , it is now possible to mock the config retrieved from Azure Storage instead of relying on the default config, therefore the semantic kernel tests can be moved to the default suite of tests, with the config file retrieved from Azure storage to have .orchestrator.strategy set to semantic_kernel.
Requirements
A list of requirements to consider this feature delivered
Move all tests functional tests from sk_orchestrator to default
For these tests, mock the call to retrieve the file from Azure Storage with .orchestrator.strategy set to semantic_kernel.
Tasks
To be filled in by the engineer picking up the issue
The text was updated successfully, but these errors were encountered:
Motivation
Currently, the functional tests for Semantic Kernel spawn a separate instance of the application with the environment variable
ORCHESTRATION_STRATEGY
set tosemantic_kernel
. However, following #873 , it is now possible to mock the config retrieved from Azure Storage instead of relying on the default config, therefore the semantic kernel tests can be moved to the default suite of tests, with the config file retrieved from Azure storage to have.orchestrator.strategy
set tosemantic_kernel
.Requirements
A list of requirements to consider this feature delivered
sk_orchestrator
todefault
.orchestrator.strategy
set tosemantic_kernel
.Tasks
To be filled in by the engineer picking up the issue
The text was updated successfully, but these errors were encountered: