Command line tool for testing DekiScript extensions

[arnec]

I've just posted a page on the wiki with an attached utility for testing DekiScript extensions from the command line (or if you want programmatically).

http://wiki.developer.mindtouch.com/DekiScript/FAQ/How_do_I..._Test_my_DekiScript_Extensions%3f

Let me know if this is useful.

cheers,
arne

[neilw]

That looks awesome.

Does it show the full head/body/tail returns from the extension? That would be perfect.

[anbrcyp]

Looks like an awesome QA tool. Reminds me of a homegrown test suite I used way back in the day to test nightly builds of a database server. You could run tens of thousands tests to verify nothing had broken in your last build, and email the results out to your developers.

Thanks much for the tool. :)

[arnec]

That looks awesome.

Does it show the full head/body/tail returns from the extension? That would be perfect.

It returns the exact output of the extension, i.e. if you return a number, you'll get a number, but if you return html, you'll see the full html on the command line

[arnec]

Looks like an awesome QA tool. Reminds me of a homegrown test suite I used way back in the day to test nightly builds of a database server. You could run tens of thousands tests to verify nothing had broken in your last build, and email the results out to your developers.

Thanks much for the tool. :)

That's precisely the use case I also have in mind, being able to build a suite of regression tests so that you can make sure changes didn't break anything before it rolls into production. Let me know if it works this way for you.

[anbrcyp]

That's precisely the use case I also have in mind, being able to build a suite of regression tests so that you can make sure changes didn't break anything before it rolls into production. Let me know if it works this way for you.

Unfortunately, that kind of software development is something about 8 years in my past so this tool won't get that level of attention from me. :(

Now I'm just a grease monkey with some programming experience and a penchant for weekend warrior coding. I figure it's better for me and the world in general than filling my weekend hours with sudoku or crossword puzzles. :D

Conceptually, I think someone with time and experience could build this relatively easily. The test suite I used really only did one thing. It had a database which contained SQL scripts and the expected output. It would run the script on the latest engine and do an exact diff. I believe it also included the option to run basic OS level commands for testing how other programs interacted with the engine. If the result had any variation from the expected, it was returned as a failure with details, etc. etc.

I think the biggest hurdle for Deki is going to be the wide variety of software setups that can be tested. A full blown Deki-test suite would be awesome for developers, though.