progress?
Let's get right to it. testStageManagerTakesUkelele
One more layer of indirection. Showing the Ukelele to the stage manager makes him take it. I'll start there.
Ok, now I need to back up a bit.
testAddResponseEffectToScriptLine
This is the lowest level, first I need to create a script Line object that includes a response that is an effect. I should rename Response to ResponseText (so that I can also create a ResponseEffect). Copy/Paste/Test for internal member, no problem. Copy/paste/Test for property - got an error (reference in another file). Tracked down, fixed.
Now adding ResponseEffect. Test, passes. Now to create the test that will use this feature (testAddResponseEffectToScriptLine). Ok, empty test, set to fail.
It occurs to me that I don't have an example effect to use in arrParameters. I'll add one first (I will be three failing tests "deep"). I could write failing tests all day (:
testCreateTakeUkeleleEffect
This one first. Creating setup function...Done. Added to main setup rountine. Updated testCreateTakeUkeleleEffect, done. Excellent. Next test...
testAddResponseEffectToScriptLine
With the effect already created, this should be easy. Well, it would have been if I had created a debugPrint method for verification. Doing so now... It's not too bad, just describe each of the memeber fields. I'm getting a really odd error, though, so Let's just cut out the debug print function for now. . .Nope, that wasn't it.
I finally tracked it down to an error in the test. I simply wasn't looking in the right place. That took longer than expected, but I'm finally back to only one failing test -
testStageManagerTakesUkelele
Which is the one I started with, and will start with next time.
One more layer of indirection. Showing the Ukelele to the stage manager makes him take it. I'll start there.
Ok, now I need to back up a bit.
testAddResponseEffectToScriptLine
This is the lowest level, first I need to create a script Line object that includes a response that is an effect. I should rename Response to ResponseText (so that I can also create a ResponseEffect). Copy/Paste/Test for internal member, no problem. Copy/paste/Test for property - got an error (reference in another file). Tracked down, fixed.
Now adding ResponseEffect. Test, passes. Now to create the test that will use this feature (testAddResponseEffectToScriptLine). Ok, empty test, set to fail.
It occurs to me that I don't have an example effect to use in arrParameters. I'll add one first (I will be three failing tests "deep"). I could write failing tests all day (:
testCreateTakeUkeleleEffect
This one first. Creating setup function...Done. Added to main setup rountine. Updated testCreateTakeUkeleleEffect, done. Excellent. Next test...
testAddResponseEffectToScriptLine
With the effect already created, this should be easy. Well, it would have been if I had created a debugPrint method for verification. Doing so now... It's not too bad, just describe each of the memeber fields. I'm getting a really odd error, though, so Let's just cut out the debug print function for now. . .Nope, that wasn't it.
I finally tracked it down to an error in the test. I simply wasn't looking in the right place. That took longer than expected, but I'm finally back to only one failing test -
testStageManagerTakesUkelele
Which is the one I started with, and will start with next time.
posted by FlyingSheep @ 8:26 PM
0 comments
