-
Notifications
You must be signed in to change notification settings - Fork 607
Cycle test within a test function(TEST_F) #32
Comments
Here are some of my code: `m_detector = kwd::KittAiKeyWordDetector::create(
`void AlexaClient::StartService(void)
}` |
Hi Boyce, There shouldn't be any problem with running multiple cycles, and your lifecycle flow sounds correct. Are you having specific problems implementing the cycle test? Ken |
Hi @kencecka From what we have tried based on the flow above, we need to disconnect/connect AVS again to keep the inquiry process normal, but it costs 3s~4s to reconnect with AVS, we expect to inquire AVS more than once without disconnecting and connecting with AVS again and again. The flow what we expected is: initial -> connect -> startRecognizing -> stopCapture -> play response audio --> startRecognizing -> stopCapture -> play response audio --> startRecognizing -> ......... But if we skip the disconnect/connect step, we can inquire AVS for 2 times normally, then we got the following errors when trying a 3rd time:
For a better user experience, we want to have a seamless inquiry between cycles. |
Hi Boyce, You are correct in your expectation that you should not need to disconnect and reconnect. Looking at your log above, it appears that you are encountering a similar issue to the one described here. We are investigating, and will update you when we have more details. In the mean time, if you are able to provide some sample code that reproduces the issue, that may help with debugging, as we are not currently seeing this issue with our own testing. Thanks, |
Hi @kencecka ,
sample code like this |
Hi Boyce, I think I see where you are running in to trouble. Your sample code is a modified version of AudioInputProcessorIntegartionTest.cpp. That test tries to thoroughly verify that all aspects of the SDK interacting with AVS are working as expected. One piece of this is to verify that the correct events are being sent out to AVS. To do this, the integration test inserts a shim ( Reviewing your code, I see:
If I uncomment the Note that there is no need for a shim like this in a normal use case. You can connect your Hope that helps, |
Hi @kencecka , -- I removed the shim(TestMessageSender), and add a object of acl::AVSConnectionManager, It works for me. |
Hi, I'm trying to do a cycle test within(TEST_F), in other words, I would like it to run SetUp() one time, and I can send my audio data cycle by cycle to AVS, do you have some advises?
I have a question about this: What is the life-cycle of it If I want to do cycle test?
this is my understand: initial -> connect -> startRecognizing -> stopCapture -> play response audio --> disconnect --> connect -> startRecognizing -> stopCapture -> play response audio --> disconnect --> connect -> .........
Is it correct?
code snippet like below:
The text was updated successfully, but these errors were encountered: