A lot of methodologies are used in software development but one of that I really use in my work and sometimes in the school is the Test Driven development, and one great thing that this semester happened to my is met to Kent Beck the creator of this test. So let me pass some of my knowledge to you with this blog.
This process consist of the repetition of a short development cycle where requirements are turned into specific test cases then the software is able to pass to the other iteration.
So first, like all my blogs let me recommends a video that will help you to understand more about this.
There are 5 steps on each iteration and are:
- Add a test – Each component of the system is a test. The test describes the function or improvements of a function. The test needs to be clear and understandable.
- Run the test – In this step you prove the code of the test to see if works correctly, if it doesn’t work as it should be edit the necessary code.
- Write more code – The next step is to write some code that causes the test to be accepted.
- Run again – If all the pest pass the new code accomplish the requirements proposed in the beginning .
- Refactor code – This part is to purify the existing code by removing the necessary code or adding new more code that is needed for the system.
Then the process is repeated until the system is done.
the benefits of this process are that the programmers are more efficient and more scenarios of failure are considered.
Some limitations are that this process is low for big systems because the necessity of create lots of test takes a lot of time, but it guarantee a system more robust.