What You really need to start using TDD

By -

Today I tell you something about tools and things which is being necessary to start writing with TDD. Why? Because If you don't use it, you will lose your motivation. You won't see results and improvement. Finally, you won't use TDD.

IDE!

Good IDE allows you to increase write tests, switch between code and test, run test, debug and check results. This is important for me, because programmers lost a lot of time by these operations. If you use TDD you will do these operations a lot of time, so you need something to reduce spending time. After wise choose, we can go to another step.

Know shortcut

To better reduce spend time doing another operation than writes code we need know the shortcut. I know about the begin You can have a problem with remembering it, but I am sure if you use it for two weeks you will use it automatically. I know it from autopsy. If you choose your IDE I think of the internet, you can find a table with shortcut for your IDE. I have on my desk, one for IntellJ, so you don't need change, configure or create it. You only need to start using it.

Change your mind

If you want to write tests first, you should change your mind. The first thing which you should change is thinking about test case, but don't about implement. Why? You should create test without any production code. In my opinion, this top of the improve on TDD. Created test is clear and understandable, because it was created in real test/use case. About this I will write a post later.

Second thing what you should change is create code step by step. This is a problem for us, because we like creating a lot of functionality on one step. I know it, but If you want use TDD then you should write for one functionality one test before it's implemented. If you cheat on only one time you will cheat on many times.

Better chair

You will be creating code faster and faster if you develop code with TDD. You need a good chair to it, because if you have a back pain you will create less quality test and you will have a problem with inventing good tests and parameters. It may seem ridiculous, but when I am in a bad mood or I am tired I always have a problem with concentrated on the test.

Summary

I give you advice how to start using TDD and what You need to prepare and use. The next post will be about base things on TDD. I will be happy if you put comments below this post. I try to create the best pattern to create good quality and fast test, so if you have an advice for me I would like to read it.

Comments

Post a Comment

Popular posts from this blog

Why TDD is bad practice?

By -
Image
Did you listen that TDD is bad? What do you think about it? I have my opinion about it! TDD is bad because... We don't have time to write tests first - I think this is a good point. I sometimes don't have time for that. Why? Because I need to do quickly fix on our code and deploy it. In this case I don't have time to create test after wrote production code too. The even worse case is when we have tested this part of our code and test after change doesn't work. I don't like this, because I must read tests and thinking about repair tests for new logic. I really don't like this. I would like to create new test and remove old every time when I have that situation. What's wrong with the test first on this case? Nothing, because if you have time to write tests after create code, you have time to create test before it. Don't you think so? We know how will implement it, but we don't know how testing it - I think a lot of developers have this problem,
Read more >>

How correctly imitate dependencies?

By -
Image
This is continuous of my previous post about why we should imitate our dependencies. I did it not long ago. I though about how do it properly and when I can say that it is correct. Start from test and real dependencies I am starting from the tests. I wrote the simple tests which, I though, are correct. That was my learned about dependencies. I had the good situation that I had some prepared tests before. During the writing test I got a knowledge. A lot of time, I verified what the system return. After it, I got the full automated tests for my dependency. Now, I am sure that dependency works like I think. Like my test use it. I think this is a very good advantage. Extract the interface for communicating The implementation to communicate is implemented and tested. Our test, if you implement it like functionality test, not code test, should show us, how we want to use our dependency. We know what parameters we use, what methods. We know what we want. That is a place where we must extr
Read more >>

Software development using Angular 5 with Spring Boot

By -
Image
Hi everyone. My last the bigger post is about configuration Spring Boot and Angular 5 . After that instruction we have integrated both technology on one app. If you created it you know that development is very hard in this case. We must waiting for build a client and it isn't effective. We can use webpack-dev-server to speed up this process, so this post is just about it. Angular and webpack-dev-server I think I have to explain webpack and webpack-dev-server. The first tools let pack our angular app to one or more files. This files is bundles. It is for improve speed of our app. Why? Because one page application need all files on start by assumption. The better way is load it using only one connection and one file, because establishing connection taking time. This is a few information about webpack, but what is webpack-dev-server? This is the tool. It serve our that files which webpack compiled, but it working on memory, so we have quick result on our browser. This is a amazing
Read more >>