Roku Developer Program

[MarkRoddy]

I've finished the initial release of the testing framework I've been working on (and pestering people on this board about :). I've placed all the source and some docs on Google Code so anyone whose interested can take a look and hopefully find some use:
http://code.google.com/p/brstest/

If you'd like to give it a try I'd recommend reading the quick start guide as it walks you through writing an initial set of test cases and getting them to run on your box.
http://code.google.com/p/brstest/wiki/QuickStart

And finally, you can download the initial release here:
http://code.google.com/p/brstest/downloads/list

From the stand point of writing tests it may seem a little feature bear as I spent most of my time working on the test discover and execution to the detriment of the actual test case (though if you explore the code and see the tests written for brstest, it's still quite usable). Expect to see this change very soon as I have a ton of additional features I'm going to be adding in the next few weeks.

Any comments/suggestions/bug reports would be greatly appreciated.

-Mark

P.S. - Developing for the Roku is much easier if you're using brstest as you no longer need to be in front of the TV to do so. I placed the function call to run all my tests within my Main() method, so as soon as I push the app to my box using 'make install' the debug console shows the tests running immediately without having to navigate the menu on the tv. I even did a little coding from work on my lunch break by connecting to my machine at home.

[MarkRoddy]

I've just uploaded a new release, v0.1.1:
http://code.google.com/p/brstest/downloads/list

This release adds the ability to use assertEqual() and assertNotEqual() on roList, roArray, and roAssociativeArray objects. Also in adding this change it will be trivial in the future to add support for comparing other objects I may not have included as long as a function can be written to compare two instances. I hope to do another release sometime in the next few weeks that makes it easier to control the way tests are run (output, dropping into the debugger on failure, etc). After that I have a few long term goals such as a GUI for running the tests, setup/teardown implementation, xml based output so tests can be run as part of a continuous integration build, and much more. However, none of these are really holding anyone (or me at least) from using library so they are likely very long term goals while work the channels and libraries (json parser at some point of no one beats me to it) which I started but didn't finish due to the lack of a testing infrastructure. Given this, if you have any specific requests now is really the time to speak up or forever hold your peace 🙂

As always, feedback of any kind is greatly appreciated.

-Mark