mathjs/test/expression/function/parse.test.js
greenkeeper[bot] c5971b371a Update standard to the latest version 🚀 (#1226)
* 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
2018-09-08 16:33:58 +02:00

29 lines
907 B
JavaScript

// test parse
const assert = require('assert')
const math = require('../../../src/main')
const Node = math.expression.node.Node
describe('parse', function () {
it('should parse an expression', function () {
const node = math.parse('(5+3)/4')
assert.ok(node instanceof Node)
assert.strictEqual(node.compile().eval(), 2)
})
it('should parse multiple expressions', function () {
const nodes = math.parse(['2+3', '4+5'])
assert.ok(Array.isArray(nodes))
assert.strictEqual(nodes.length, 2)
assert.ok(nodes[0] instanceof Node)
assert.ok(nodes[1] instanceof Node)
assert.strictEqual(nodes[0].compile().eval(), 5)
assert.strictEqual(nodes[1].compile().eval(), 9)
})
it('should LaTeX parse', function () {
const expression = math.parse('parse(expr,options)')
assert.strictEqual(expression.toTex(), '\\mathrm{parse}\\left( expr, options\\right)')
})
})