summaryrefslogtreecommitdiff
path: root/tests/test_analyzer.js
AgeCommit message (Collapse)Author
2014-12-16moving files around after repository mergerAlon Levy
2014-11-10rename rhizicore -> rz_core, move towards common rz_ prefixLV-426
2014-10-27update test output, mark issue 86 test as suchAlon Levy
2014-10-21test_analyzer: better testAlon Levy
need better graph accessors to give only the 'real' nodes & links - that will fix some of the tests, leaving the real wrong ones
2014-10-21fix test_analyzer after require.jsAlon Levy
2014-10-20introduce require.js and rewrite testsAlon Levy
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.
2014-10-19[wip] tests/test_analyzer #82Alon Levy
2014-10-09test_analyzer: correct command line argumentsAlon Levy
2014-10-08add tests_analyzerAlon Levy
node test_analyzer.js '#a and #b and #c are cool' | dot -Tpng > /tmp/temp.png; xdg-open /tmp/temp.png Todo: use stdin, then it will be a total pipe Todo: make this a rhizi debug feature that displays the image in the browser?