.. Test First, Code Later ..
The first time I was about to use Test Driven Development (TDD), a lot of negative things about TDD, one-by-one, filling my mind.
Why.. why.. why we should test it first? Isn't it will just make the development flow being more complicated? Huh..
As time goes by, it turns out to be not that bad! Even, this approach sometimes somehow being so helpful, especially in the development of allocateam!
Let's take a look at the main positive side of this approach:
1. We are driven to think deeper and further
2. Help us to structurize what we are about to do
3. Make our testing phase easier for sure!
Additionally, there is an awesome thing named Continous Integration (CI) that served by GIT ..and maybe by another version control but I don't know hehe.. CI is really helpful for us when integrating our code for building an application. We can specify every stage that has to be passed by our code when it's already pushed into GIT, e.g. we divide stage for back-end test and front-end test or stage for testing, release, and deploy the code, etc. CI gives flexibility for developers to specify their own stages that they think they needed to support the application development.
The thing that I amazed is when Test Driven Development approach met Continous Integration! The collaboration between them is very helpful, at least for me. When my back-end test stage failed, the code won't be deployed to the server, so that will economize cost for deploying useless code to the server. And, CI also reminds me when I forgot to test my code in local because it will raise some error in GIT terminal.
My conclusion is Trust me that everything absolutely has its positive side. Be wiser to fill your mind with positive things! And.. TDD & CI isn't that bad, guys! It is powerful if you use it in the right way :)
0 komentar:
Post a Comment