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 6af9f28c50 simplifying the API tests
2017-10-25 23:08:16 -04:00
..
audio using rest of effects tests on Convolver 2016-08-09 14:25:20 -04:00
component increasing acceptable range for test 2017-09-16 15:16:46 -04:00
control applying defaults API to control classes 2017-04-25 22:37:01 -04:00
core updating to new context dispose returning promise API 2017-10-25 18:00:04 -04:00
deps removing unused files from test deps 2017-04-30 15:04:28 -04:00
effect removing convolver effects tests that throw an error when running in TravisCI 2016-11-22 10:46:26 -08:00
event adjusting testing thresholds for rounded toTicks() 2017-09-17 12:43:06 -04:00
examples throw error if URL doesn't exist 2017-03-26 15:21:45 -04:00
helper simplifying the API tests 2017-10-25 23:08:16 -04:00
instrument alter tests for new envelope release curve 2017-09-13 18:30:02 -04:00
signal testing exponentialApproach and setValueCurve 2017-09-20 19:05:00 -04:00
source testing stopping multiple sources 2017-10-21 13:44:30 -04:00
type adjusting testing thresholds for rounded toTicks() 2017-09-17 12:43:06 -04: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 test all examples for execution errors 2017-03-26 14:51:25 -04: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.