My common shortcuts on IntellJ for TDD

By -

Hi everyone! On previous post I wrote about What we need to write fast using TDD. This post is about one section of it. Shortcuts on my IDE. Currently I use IntellJ and I show you the shortcuts which I use for improving my work.

List of shortcuts

  • Ctrl + Shift + T - Go to Test/Go to Test Subject - I use it for quick switch between test and production code. Using it, I don't need use mouse to click a package and I don't lose my time for finding a class.
  • In test class Alt + Insert and next Enter - Create test method - a faster way to write a method of test.
  • Ctrl + E - List of recent files. I use it for quick switch between used files. I try not to use a mouse when I write the code.
  • Double shift - next shortcut to switch between all classes.
  • In test class Ctrl + Shift + F10 - running test
  • In tested class Shift + F10 - run previous action - my previous action is almost always test for current written code.
  • F2 - go to next warning or error - this is the best way to generate methods and field, when we have don't compile code. F2 and Ctrl + Enter and we very fast create construction for real code.
  • F6 - move class/method - I use it for refactoring.
  • Shift + F6 - rename - as above.
  • Ctrl + Shift + V or M or C or P - withdraw V -> variable M -> method C -> constant P -> parameter - as above.
  • Ctrl + P - show parameter - it is good for existing code for quick check what kind of parameter we need to pass.
  • Ctrl + Alt + Left/Right - go to previous/next your point of track - this is for quick go back when you debug or switch.
  • Ctrl + Shift + A - find and execute action - when I forget a shortcut then I use it for running action and read what shortcut is.

Summary

These aren't all of shortcut, but I think it is common for TDD. Maybe You know shortcut which We can use for improve our work with TDD? Put it in comment below. If I learn new nice shortcut I will update this post.

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 >>