joergen7 / cre Goto Github PK

Planned release date: Dec 2015

Content:

• No external processes survive a failure
• Importing of script files
• Altering function body should invalidate the cache

It is a bit annoying to start cfide and then search for the cf file using the interface which starts not from the local directory but from some root.

I suggest that 1..n files can be provided as arguments.
e.g.: cfide consensus.cf test.cf

Somehow unit testing should be provided (e.g.: whether the deftasks work).

If scripts can be imported (see other issue), scripts can be written such that they contain only one deftask and some known input data.

This means what is missing is

1. the ability to compare expected and produced output
2. a way to bulge start multiple of such tests (e.g.: all cuneiform test files .cft?? in a directory).
3. a way to visualize the ones that failed.