I released five new sample lessons from my Test With Spring course: Introduction to Spock Framework

What Prevents You From Writing Automated Tests?

If you read my blog on a regular basis, you have probably noticed that I have written many tutorials about automated testing.

The problem is that some of these tutorials are quite old and outdated, and that is why I am going to update them.

Here’s where you come in.

Before I can help you to solve your problems, I need to know what prevents you from writing automated tests. That is why I created a this survey. It has only two questions and answering to it takes only a few minutes of your time. You can help me to help yourself by clicking the link found from below:

Answer to my test automation survey.

Also, I will publish the results of my test automation survey on my blog. That blog post will also provide links to articles that help people to find solutions to their problems.

Thank you in advance!

About the Author

Petri Kainulainen is passionate about software development and continuous improvement. He is specialized in software development with the Spring Framework and is the author of Spring Data book.

About Petri Kainulainen →

3 comments… add one
  • I like writing tests after reading your blog posts. Thank you.
    Now a big variety of combination of tests prevents me from writing really professional codes.
    But what I understand that good tests depends on the situation.
    For example, the book “Pro Spring 3” gives advice to write integration tests for service layer, but you recommend for persistence layer. I am confused. Which of approach is better?
    And what about Selenium? Does developers really need this tool for automated testing or QA?

    Reply
    • Thank you for your kind words. I really appreciate them!

      But what I understand that good tests depends on the situation.

      I agree.

      For example, the book “Pro Spring 3” gives advice to write integration tests for service layer, but you recommend for persistence layer. I am confused. Which of approach is better?

      Actually I write integration tests for:

      • Every custom method found from my repositories
      • Every controller method

      The reason for this is that this way I get a good integration test coverage, and I can use unit tests for testing the individual components. However, this is only my opinion.

      Writing integration tests for service classes is also a valid approach, but you need to test your controller classes as well. You can use end-to-end tests for this purpose, but they are a lot harder to write than integration tests.

      And what about Selenium? Does developers really need this tool for automated testing or QA?

      I think that developers should know how to write end-to-end tests. However, since writing end-to-end tests takes a lot of work, you have to select your test cases wisely. If you don’t know how to do this, you should definitely ask help from the testers assigned to your project.

      Also, if your employer has a QA department, your employer might have a company policy which states that the QA department is responsible of writing end-to-end tests.

      As always, the answer to this question is: it depends.

      Reply

Leave a Comment