Closed TimSusa closed 5 years ago
The problem with testing this lib is that we need to have MIDI devices plugged in to get relevant results. Without a device plugged in, there's only so much we can test.
Having said that, what you suggest is still valid.
FYI, you can emulate MIDI devices using https://github.com/jazz-soft/midi-test
Yeah, that's a good tip. Maybe it could be used during testing.
Sounds and looks quite good. @jazz-soft: Thanks for that input. I will give it a shot
If we could use that to conduct tests with virtual MIDI devices (I/O), that would be a real step forward.
Hey, I have succeeded to convert all your tests. Furthermore a virtual midi driver test was created. Stuff runs on my mac without the need of a browser. All 94 Tests are passing. I would appreciate your feedback.
Tests are passing on my side too (macOS also). I think that's a good base to start with. Thanks a lot!
@jazz-soft big big thanks for your input. I wonder, if you would pose this library for production purposes. I mean I would have the need to create virtual midi ports out of my private application
In order to fulfil the test-pyramid, an e2e test could be established via cypress or puppeteer that simply runs existing index.html from test folder. Furthermore, all the selectors (testing midi stuff) could be checked for being ok and console output could be tracked. Circle CI could be used for free for test-automation and connecting the results to all github pull-requests.
This issue is connected to https://github.com/djipco/webmidi/issues/63