mirror of
https://github.com/josdejong/mathjs.git
synced 2026-01-18 14:59:29 +00:00
c5971b371a
* chore(package): update standard to version 12.0.0
* update to new lint version with --fix
I believe this mainly adds whitespace to `{}`'s.
* Replace assert.equal with assert.strictEqual
This breaks a lot of tests which I will endevour to fix in the next
commits.
* Fix most errors due to assert.strictEquals
Some instances of `strictEquals` are replaced by `deepEquals`.
`toString` has been used to make some string comparisions explicit.
Tests will still fail untill #1236 and #1237 are fixed.
* Fix assertion erros due to -0
With node 10, assert.strictEqual no longer considers `0 === -0`.
I missed these first time round as I was using node 8.
* Put toString correct side of bracket
I was converting the constructor to a string rather
than the result of the computation. Oops.
* Fixed #1236: quantileSeq has inconsistant return
* Update package-lock
* Fixed #1237: norm sometimes returning a complex number instead of number
* Fix cli tests
* More changes for standardjs, and fixes in unit tests
17 lines
540 B
JavaScript
17 lines
540 B
JavaScript
const assert = require('assert')
|
|
const math = require('../../../src/main')
|
|
|
|
describe('randomInt', function () {
|
|
// Note: randomInt is a convenience function generated by distribution
|
|
// it is tested in distribution.test.js
|
|
|
|
it('should have a function randomInt', function () {
|
|
assert.strictEqual(typeof math.randomInt, 'function')
|
|
})
|
|
|
|
it('should LaTeX randomInt', function () {
|
|
const expression = math.parse('randomInt(0,100)')
|
|
assert.strictEqual(expression.toTex(), '\\mathrm{randomInt}\\left(0,100\\right)')
|
|
})
|
|
})
|