On Nov 21, 12:36 pm, "Edward K. Ream" <[email protected]> wrote:
> I am now training myself to create the @test node even when the fix is > "trivial", as with the recent fix to updateEditors. Imo, it's time to start greasing the unit-test gears in addition to removing grit. After writing this post, I saw that the new standard for testing should be to create unit tests for all *changed* code, regardless of the reason for the change. This will have the effect of extending the unit-test safety net to just about anything that might cause problems. For example, a recent mistaken change in leoQtLog.selectHelper caused leoQtLog.put to fail. Rather than creating @test nodes immediately for both methods, I made a further mistake by patching the innocent leoQtLog.put. I soon reverted the code, but the reversion was yet another change, so I could no longer avoid making @tests node, which are now in place. True, the @test nodes were created after the bug was fixed, but they do assert the essential properties that must be maintained. The new testing pattern has great promise; it should soon become second nature. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
