-
Notifications
You must be signed in to change notification settings - Fork 172
Test checklist
Sebastian Moors edited this page Oct 6, 2016
·
4 revisions
This list contains a bunch of things which should be tested with every release and after any substantial change:
- Midi input: Connect a (virtual) instrument to hydrogen and play some notes. The samples which are triggered (for example a bassdrum for Midi Note 36) should be clearly audible and not distorted.
- (Computer) Keyboard input: Press some keys on your computer keyboard. You should be able to trigger instruments. See the keymapping in the manual for more informations about which keys to press..
- Export a track to a wav file
- Check if the clock is working when a song is played
It makes sense to test these things with different sound drivers.