| Age | Commit message (Collapse) | Author |
|---|
|
|
|
for json in tools/cri.json tools/sage.json tools/deliverables.json heroes.json tests/wizmann.json; do sed -i -e 's/\<source\>/__src/g' -e 's/\<target\>/__dst/g' $json; done
|
|
|
|
SimpleHTTPServer does a wrong 301 for query parameters, i.e.:
http://bla:foo/?hello=1
301 =>
http://bla:foo/?hello=1/
which kills our query parameter parsing. Instead of making the client
handle non compliant servers I rather fix the test server to not 301.
Real servers (need to check) don't do this I hope.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
need better graph accessors to give only the 'real' nodes & links - that will fix some of the tests, leaving the real wrong ones
|
|
|
|
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.
|
|
|
|
|
|
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?
|
|
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
|
|
|
|
|
