Mirrors/Tone.js
2
0
Fork 0
mirror of https://github.com/Tonejs/Tone.js synced 2024-11-16 00:27:58 +00:00
Code Issues Projects Releases Packages Wiki Activity
Tone.js/test
History
Yotam Mann 58eac95314 define left and right variables
2018-02-04 11:43:34 -05:00
..
audio testing loading un-decodable audio 2018-01-18 12:50:45 -05:00
component checking for discontinuities with different curve types 2018-01-03 15:23:20 -05:00
control linting 2017-12-30 11:26:29 -05:00
core increasing testing threshold 2018-02-01 09:56:32 -05:00
deps linting 2017-12-30 11:26:29 -05:00
effect adjusting test threshs to be less susceptible to randomness 2018-01-17 13:40:18 -05:00
event linting 2017-12-30 11:26:29 -05:00
examples linting 2017-12-30 11:26:29 -05:00
helper define left and right variables 2018-02-04 11:43:34 -05:00
instrument linting 2017-12-30 11:26:29 -05:00
signal testing cancelAndHold during exponential ramp 2018-01-03 15:38:04 -05:00
source updating threshold 2018-01-17 13:30:24 -05:00
type increasing Midi conversion tests 2017-12-29 13:14:02 -05:00
.jshintrc adding "before" and "context" 2015-08-18 17:08:48 -04:00
index.html silence version logging in tests 2017-11-29 15:23:20 -05:00
karmaTest.js adding polyfill 2017-12-30 00:30:52 -05:00
README.md only using karma test runner with headless chrome 2017-06-29 17:31:10 -04:00

README.md

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

From within the gulp folder, run gulp karma-test to collect all of the files, launch a local server and run the tests.

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.