@AndreMiras not yet ready 😁
just starting the discussion ...
I have thought about how to add unit testing:
so far i tested the code visually with my GUI Magic Session Mixer
that was working for me, but of course its nowhere an automatic solution. (Also it doesnt test MagicApp)
What about uploading a free to use sound file to the test folder and use the vlc media player to play it. Then change volume and "assert" expected feedback? We could also use taskkill /F /IM vlc.exe to just kill all open vlc windows. VLC has the characteristic, that every new app window will create a new WAS (session). That way we could easily stress test pycaw (Opening a lot of windows and closing them all instantly).
Im proposing to use vlc since i cant find any other nice crossplattform solution (win 7 - 10)
What wont work:
Internet Explorer:
start iexplore music.mp3 or any other file format will download the file
<audio autoplay="autoplay"><source src="music.mp3" /></audio> a simple website wont work either: Problem
Windows Media Player:
behaves just weird in terms of sessions - probably because its so old.
What could work:
VLC media player (-needs to be installed)
Powershell to play .wav link (-is ugly and I could not kill the session besides using taskkill /F /IM powershell.exe what could also interfere with the unit testing)
@AndreMiras not yet ready 😁 just starting the discussion ...
I have thought about how to add unit testing:
taskkill /F /IM vlc.exe
to just kill all open vlc windows. VLC has the characteristic, that every new app window will create a new WAS (session). That way we could easily stress test pycaw (Opening a lot of windows and closing them all instantly).Im proposing to use vlc since i cant find any other nice crossplattform solution (win 7 - 10)
What wont work:
Internet Explorer:
start iexplore music.mp3
or any other file format will download the file<audio autoplay="autoplay"><source src="music.mp3" /></audio>
a simple website wont work either: ProblemWindows Media Player:
What could work:
taskkill /F /IM powershell.exe
what could also interfere with the unit testing)