TDD Video: "Help, I'm stuck, what do I do next"
What do you do when you are stuck in a TDD process? How do you decide where to start when testing? How can you pick what to text next? Watch: http://www.tablexi.com/blog/2013/04/help-im-stuck-what-do-i-test-next-xi-to-eye/developers/.
Comments
Well, when you’re stuck, you wait and think that’s the best solution to anything. Speaking about solutions, if you’re stuck on some task and need a solution, take a look at what we provide in our Custom Software Development Solutions: https://www.osplabs.com/custom-healthcare-software-development/
Or better yet, look at our 340B Inventory Software & Healthcare RCM Solutions
I also advise you to check out our healthcare software development company page
That’s a great question! Getting “stuck” in TDD often means you’re trying to write a test for too large or complex a piece of code. The main rule when you’re stuck is: reduce the scope! Start with the smallest, most atomic behavior your code needs to perform.
How do you decide where to start? Begin with a “Red” test that checks an edge case or the simplest input. This forces you to think about the external interface (API) before you write the implementation. If that seems too difficult, perhaps the problem lies in the architecture itself. Our development company often helps teams implement TDD by starting with the right architectural design, which makes testing a natural process, not a chore.
Post a comment