According to the commonly used TDD strategy, to implement something, you write a test that fail the code first, write the simplest code, refactor, and then repeat. I am trying to imagine this scenario with implementing a flexible length list (e.g. List<T> in .net.Let's say I first test by inserting one item. Probably the simplest way to achieve this is by backing the list with an array with length 1 (which will pass the test). Nothing to refactor here, so I'll go ahead and write another test that insert 2 items. I'll simply change the array length to 2, and the test pass again. Then I write test with 3 items, expand the array, and repeat again. I will end up forever doing this until I'm tired.Is this an exception to the fail-test-first strategy? Or am I missing something in the above strategy?PS: The actual implementation backs the list with an array which grows twice as large every time the number of elements exceed the array length.
Test driven development when implementing a flexible length list
unit testing;tdd;list