Hello allocaters, It's me again aye, your allocateam hustler, in this blog post I want to elaborate what I have said in my last blog post about the minor set back I had when implementing some one else's test.
So here it goes, before we begin I want to give you an overview of what happened. In the second scrum meeting our lead developer Wisnu aka CAK decided to take the task of creating unit test of csv file validation. I my self decided to take the creating dummy data. All was well then next scrum meeting came. I was confused of what task to take next. Seeing that there is way more important things that the lead developer needs to take care of. I took the task of implementing the test that wisnu created.
All was well when implementing the csv validation. I had great help from ano because the csv validation needed the pandas module and ano just used the pandas module if you wanna see more check out his blog post here https://blog.allocateam.com/2018/03/csv-file-parsing-in-python-how.html
so any way all was well, but then disaster strikes.
So my code was running fine I did all the required test that the test needed. but there was one problem why wasn't my code passing all the required test.
I spent a lot of time trying to figure out what was wrong with the code I have created. It took me a while but then I figured out it wasn't the implementation that was wrong it was some of the test.
It turns out in the test driven development the test that you or someone else created might not be correct according to best practice of test driven development it's first add a test run the test if it fails make a little change run the test if it pass than development continues.
http://agiledata.org/essays/tdd.html
So the lesson learned here is, it's okay if your test is not passed the first time around what you need to do is make a little change run it again and if it pass add another test and so on and so on. What I learned here is that through all the testing I have done it made me more careful of the code that I am about to implement and it made me an overall better devoloper.
That brings us to conclusion of my blog post, that's all for now don't forget to always implement test driven development as always I am ahmad yazid harharah signing out :)
0 komentar:
Post a Comment