<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rhizi/tests/test_nan_problem.js, branch master</title>
<subtitle>Connective intelligence</subtitle>
<id>https://git.yuv.al/rhizi/atom/tests/test_nan_problem.js?h=master</id>
<link rel='self' href='https://git.yuv.al/rhizi/atom/tests/test_nan_problem.js?h=master'/>
<link rel='alternate' type='text/html' href='https://git.yuv.al/rhizi/'/>
<updated>2014-10-20T18:36:37Z</updated>
<entry>
<title>introduce require.js and rewrite tests</title>
<updated>2014-10-20T18:36:37Z</updated>
<author>
<name>Alon Levy</name>
<email>alon@pobox.com</email>
</author>
<published>2014-10-20T10:25:32Z</published>
<link rel='alternate' type='text/html' href='https://git.yuv.al/rhizi/commit/?id=c919c4bfef4ad9e2dc25d040c0727dd29ad541ae'/>
<id>urn:sha1:c919c4bfef4ad9e2dc25d040c0727dd29ad541ae</id>
<content type='text'>
Yes, I'm being lazy. The purpose of require.js is to allow writing
modules, i.e. individual smaller then the whole files with clear
dependencies. This is achieved by using a new api provided by
require.js:

define, require, requirejs

Read more at [requirejs] (http://requirejs.org)

Tests have been rewritten to work correctly with require.js; they still
use jsdom.

Test output is now stored in the repository, all tests are run via
run_tests.js; This is a hack - once a good harness (with assertions,
suites - unittest like) presents itself it will be used.

Hidden here is also using FileSaver for history saving, so history is
saved to history.json instead to a random name. Plus dropping some dead
code.
</content>
</entry>
<entry>
<title>tests: add test_nan_problem</title>
<updated>2014-10-07T05:51:34Z</updated>
<author>
<name>Alon Levy</name>
<email>alon@pobox.com</email>
</author>
<published>2014-10-06T07:08:13Z</published>
<link rel='alternate' type='text/html' href='https://git.yuv.al/rhizi/commit/?id=df93bb43321bcccbc7ee539b520203e97f18d9da'/>
<id>urn:sha1:df93bb43321bcccbc7ee539b520203e97f18d9da</id>
<content type='text'>
replaces test_history.js.
fixes links to new external/scripts/*

The new test some point it actually showed the d3 problem, but now it doesn't.

To run it:
node tests/test_nan_problem.js | grep nan
</content>
</entry>
</feed>
