Mirrors/Tone.js
2
0
Fork 0
mirror of https://github.com/Tonejs/Tone.js synced 2024-11-16 08:38:00 +00:00
Code Issues Projects Releases Packages Wiki Activity
Tone.js/test
History
Yotam Mann fdf39d4253 testing swing
2016-04-18 00:17:23 -04:00
..
audio using wave versions for testing 2016-03-04 23:52:17 -05:00
component removing conditional test for float waveform analysis 2016-03-20 19:03:18 -04:00
control removing exponent member 2015-11-17 22:51:32 -05:00
core testing swing 2016-04-18 00:17:23 -04:00
deps cross checking note conversions against teoria 2015-08-16 22:17:59 -04:00
effect using non-mp3s for testing 2016-03-05 00:07:17 -05:00
event fixed typo in test 2016-04-13 12:24:34 -04:00
helper Transport unnecessary dependency 2016-04-18 00:15:46 -04:00
instrument a few more sanity checks for the polysynth 2016-03-21 15:20:04 -04:00
signal polyfill for browsers that don't support interpolate value curves 2016-03-20 18:36:59 -04:00
source using wave versions for testing 2016-03-04 23:52:17 -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
karmaTest.js adding karma testing files and hooks 2016-03-04 16:25:44 -05:00
README.md updated testing README 2016-03-29 19:42:31 -04:00

README.md

I am currently using two test runners: mocha and karma + mocha.

From within the gulp folder, run gulp browser-test to collect all of the files, launch a local server and run the tests. If you run gulp karma-test, the tests can be configured to run across multiple browsers simultaneously.

Be sure that the browser window is in focus while tests are running.

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 then refresh the test/index.html page to rerun those 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

The tests target the latest specification and not any specific browser. I have been keeping a list of which features browsers/versions currently support in test/helper/Supports.js. Some tests are only conditionally run if that feature is supported on the platform.