Tips for the voice agent tester

Tips for test cases, jobs, batch jobs, recording mode, and Kubernetes.

• If the recording mode is turned on, many calls might be generated. Your disk space and performance might be affected.
• The jobs include the worker definition for running the test. So, any changes to the worker don't affect jobs that are running. If you want a job to follow that updated worker, you must restart the job.
• If the worker contains no test cases, then no jobs can be started by the worker until test cases are added to it.
• If you delete a running job, the tester webhook manages the failure that results from not finding the job and hangs up the call.
• If you delete a worker, all the jobs that the worker ran and all the data for the jobs are deleted.
• If a test case that is being used by a worker gets deleted, when the jobs of that worker reach that test, the jobs fail. These jobs are marked as not valid until you change the worker definition and remove that test case from the array of test cases.
• The microservice uses Speech to Text and Text to Speech. However, you can use only Speech to Text if you have valid WAV files by using a send type of commands. For more information, see Action tags and state variables in the Voice Gateway API.
• If the gateway that you're testing is on Kubernetes, you might need to apply a different rule to the network configuration.