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
It's really embarrassing to admit that we currently lack test cases for the raop2 module. Should we have one? -- definitely yes.
However there are some challenges when dealing with remote audio server. For example, how we judge whether a remote speaker is playing a music correctly, in a correct tone and tempo, without noise or jitter? Human may easily tell whether the sound is "okay" or not. But what if we want to automate the tests? (And I believe, tests must be automated for sustainable/scalable development.)
I would imagine we should do this one by one anyway:
Define a set of manual test cases that are executed and confirmed by humans
Automate some easy part of testing first (e.g. make sure that the code does not crash or emit unexpected error message)
Enhance it further (automate more)
If somebody has an idea or knowledge, please share it with me. I'm curious how people are testing this kind of network audio.
The text was updated successfully, but these errors were encountered:
It's really embarrassing to admit that we currently lack test cases for the raop2 module. Should we have one? -- definitely yes.
However there are some challenges when dealing with remote audio server. For example, how we judge whether a remote speaker is playing a music correctly, in a correct tone and tempo, without noise or jitter? Human may easily tell whether the sound is "okay" or not. But what if we want to automate the tests? (And I believe, tests must be automated for sustainable/scalable development.)
I would imagine we should do this one by one anyway:
If somebody has an idea or knowledge, please share it with me. I'm curious how people are testing this kind of network audio.
The text was updated successfully, but these errors were encountered: