Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Establish test cases #47

Open
hfujita opened this issue Nov 7, 2015 · 0 comments
Open

Establish test cases #47

hfujita opened this issue Nov 7, 2015 · 0 comments

Comments

@hfujita
Copy link
Owner

hfujita commented Nov 7, 2015

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:

  1. Define a set of manual test cases that are executed and confirmed by humans
  2. Automate some easy part of testing first (e.g. make sure that the code does not crash or emit unexpected error message)
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant