Hi ,
This will depend on how you structure your code and your azure resources. It's better if you can do it using a devops CI/CD tool, but if you just want a quick way,
Are you deploying with Visual Studio 2017 or 2019 (https://learn.microsoft.com/en-us/azure/azure-functions/functions-develop-vs?tabs=in-process)?
Are you passing the storage key though app settings (https://learn.microsoft.com/en-us/azure/azure-functions/functions-develop-vs?tabs=in-process#function-app-settings)?
The code may have a storage connection string under local.settings.json, once you deploy it will be under the app settings
But it could be hardcoded. You need to find and replace with the connection string for the storage used for "Test" (Considering your next environment is Test)
without devops/automated deployment you can manually create a new storage and new function for test, deploy the same code to the new "TEST" function using the "publish" feature of Visual Studio.
Do you have your current Azure Function and storage under the same resource group? good tip is to create a new resource group for the next stage. call it "test-[somename]-rg. and add your test function and test storage under it"
than:
Go to the new "TEST" storage, grab the key :
and replace on the new "Test" function
Of course there is a lot more to it if you want to improve this process, like organizing in Resource groups with environment prefix, like dev-mycompany-rg, test-mycompany-rg.
Automation : (to create function app and storage ) https://www.maxivanov.io/deploy-azure-functions-with-terraform/
(to deploy code) https://learn.microsoft.com/en-us/azure/azure-functions/functions-how-to-azure-devops?tabs=dotnet-core%2Cyaml%2Ccsharp
a nice thing to do is to store the storage secret on the azure vault and call the vault in the azure function: https://learn.microsoft.com/en-us/azure/app-service/app-service-key-vault-references
let me know if you need more details or to expand on it