A: 

Try giving your blocks names in the homepage CMS page. Similar errors I've received have been resolved this way. I see that you're trying to wrap the blocks in text lists, but from what I see you never actually identify the blocks from within the CMS page. Try something to this effect instead:

{{block type="test_tester/one" template="tester/one.phtml" name="testa"}}
{{block type="test_tester/two" template="tester/two.phtml" name="testb"}}

If you cannot get away from the parent blocks as containers, you may have to rethink part of your layout. If that doesn't do it either way, let me know and we'll try something else. Hope that helps.

Thanks, Joe

Joseph Mastey
Interestingly, this actually works - it has no effect on the CMS {{block}} style includes (as in your example) - these work with or without a name attribute. However, it does fix the 'cms.xml' <block> lines. If these lack a name, they don't work correctly.
KingJackaL
So your problem is or is not resolved then? :)
Joseph Mastey
Thinking about it, this makes sense. Using the inline syntax {{ }}, the block is immediately output and wouldn't really need a name. However, blocks specified using <block /> aren't automatically rendered, so you would need a handle to render them.
Joseph Mastey