I put a lot of effort into making a top-tier mocha-inspired unit test framework for Roku, with examples, rich documentation and a couple of hours of video training.

I personally think it makes development way easier and more efficient (hence investing 150+ hours into it), so it might be that even new developers benefit from knowing about it.

https://github.com/georgejecook/rooibos

hello, in Lesson 3, item 3 you say
Modify home_scene.xml to route to the new screen components by replacing what is there with the following: function init()
? "[home_scene] init"
m.center_square = m.top.findNode("category_screen")
m.center_square.setFocus(true)
end function
However, that is what should go in the brs file. the contents of the xml file should also change, but you forgot to provide that. Not a big issue, I found it in the xml listing, which has the final revision of that file.

Hey @timbeynart-nbcuni I'm running through your crash course (as I just started working as a Roku Dev) and things are going well. Your documents are well-laid out and descriptive. One bit of feedback I had (and it's really small) was to create links between your different lessons. Having a link to Lesson 3 at the end of Lesson 2 would be super helpful once you complete each one.

Also, is there a way I can tip you or something? I know that was probably not your idea with this tutorial, but I like to give back.

I did create a little something to help automate sideloading using NodeJS. Maybe we can include that in the lesson to ease the burden of making small changes and having to upload each one.

One lesson I did learn in this was you can't just zip up a directory, you have to zip the contents of the directory and them upload it.

Either way, I'm just starting lesson 3 and I'm very grateful this is around.

1. There are some necessary changes from lesson 2 to lesson 3 in main.brs which appears to be missing in the lesson. Took a bit to figure out for a newbie:

		msg = wait(0, m.port)
		msgType = type(msg)
		if msgType = "roSGScreenEvent"
			if msg.isScreenClosed() then return
		end if

2. Emphasis on a minor change which is easy to over look in lesson 3:
   <ContentNode title = "DRAMA"/>
<category_node title = "HORROR" feed_url="..."/>
   I think an emphasis should be placed on the fact that ContentNode is modified to category_node as this is a minor difference that is not immediately obvious and if users are manually modifying as i did, as opposed to copy and paste, then it can be quite an annoying learning lesson.

In Lesson 3, at step 3, when running, I consistently get the error "Interface not a member of BrightScript Component" and breaks on the updated code in home_scene.brs. I'm not positive, but should the code be referencing the center_square or category_list? In your code example this is how it is set, so thinking maybe it should be changed?

	m.center_square = m.top.findNode("category_screen")
	m.center_square.setFocus(true)

I'm new to all this but when I added the following to home_scene.xml, it seemed to run

    <category_screen
      id="category_screen"
      visible="true"
      translation="[0,0]" />

Also, step 3 says to update the home_scene.xml file when it should be the home_scene.brs file :)