Tone.js/test
2015-12-06 13:14:36 -05:00
..
audio auto panner starts at the middle of the cycle 2015-08-27 22:56:35 -04:00
component wider tolerance for testing 2015-12-06 13:14:36 -05:00
control removing exponent member 2015-11-17 22:51:32 -05:00
core testing new Emitter style 2015-11-11 12:33:11 -05:00
deps cross checking note conversions against teoria 2015-08-16 22:17:59 -04:00
effect testing new classes and APIs 2015-10-21 10:55:56 -04:00
event fixing and testing start offset for non-looping parts 2015-11-26 08:42:33 -08:00
helper Timeline signal using new Tone.Param 2015-10-21 10:53:43 -04:00
instrument testing instruments 2015-08-31 11:37:10 -04:00
signal testing new classes and APIs 2015-10-21 10:55:56 -04:00
source testing playbackRates 2015-11-10 23:47:20 -05:00
.jshintrc adding "before" and "context" 2015-08-18 17:08:48 -04:00
index.html renamed test html file 2015-08-17 01:04:04 -04:00
README.md updating testing flags 2015-11-04 15:59:09 -05:00

gulp test from within the gulp folder to start a server and run all of the tests.

Individual files can be tested by running gulp collectTests -f [Tone class name] which will update the test/Main.js with the given class tests.

You can also test groups of classes by folder by adding another flag. For example to test all of the signals run gulp collectTests --signal. or the shorthand form: gulp collectTests -s.

  • -s = --signal
  • -i = --instrument
  • -o = --source
  • -v = --event
  • -e = --effect
  • -c = --core
  • -m = --component
  • -t = --control

Currently, Chrome is the target test platform. 100% of tests should pass. Fewer tests tends to pass in Safari and even fewer in Firefox. The goal is to have 100% pass on all browsers, but since the speicification and implementations are all relatively new, there are still a few kinks to work out.

Be sure that the browser window is in focus while tests are running. Timing in Tone.js is done using requestAnimationFrame which fires at a low priority or no priority if the tab is not in focus.