Reply to thread

Message: [QUOTE="Phlip, post: 4663965"] Call it assert_mysub(). In general, generic assertions have mundane names, such as assert_equal, and application-specific assertions have long names that reveal their application-specific intent. Such as assert_x_and_y. Next, all tests use the pattern Assemble, Activate, Assert, but your test case might be missing its Activate line. The line that actually does something important, in your production code! That pattern is, generally, why I always call the assembly methods "assemble_", and I always call assertions "assert_". And, as always, props for writing developer tests. You are now among the top 5% of all programmers. (More's the pity!;) [/QUOTE]