There are many software development blogs out there, but many of them don’t publish testing articles on a regular basis.
Also, I have noticed that some software developers don’t read blogs written by software testers.
That is a shame because I think that we can learn a lot from them.
That is why I decided to create a newsletter that shares the best testing articles which I found during the last week.
Let’s get started.
- How to mock a Spring bean (version 2) is a very interesting blog post that describes how you can create mock beans by using Mockito. This is useful if you are writing integration (or end-to-end) tests and you want to mock a few beans that are using external APIs.
- Improve Your JUnit Experience with this Annotation identifies a useful tip that helps you to run your test methods in alphabetical order. This is useful if you are using an IDE that cannot do this on the user interface (IntelliJ Idea can do this!).
- Verifying DateTime and Date with Hamcrest helps you to to write assertions for Java 8 date and time API by using Hamcrest. Although I recommend that you use AssertJ for this purpose, sometimes you must use Hamcrest. If you have to use Hamcrest, this blog post makes your testing experience less painful.
The Really Valuable Stuff
- Automation – The Saviour helps you to write better automated tests and describes when you should just give up on test automation. The fact is that you cannot automate everything because it would take too much time. That is why you have to learn to make the correct trade-offs and use manual testing for things that are hard to automate.
- Three reasons to start improving your API test automation skills describes three reasons why you should pay more attention to your API test automation skills. Writing automated tests on the API level makes sense because they are a lot easier to write than end-to-end tests and cover a lot more code than unit tests. If you haven’t written them yet, read this blog post and write your first API test.
- Top 10 audit topics for test cases describes a 10 step process that helps you to improve your existing test suite. This process aims to delete unnecessary tests and identify areas that require more work. I think that it is extremely important that you evaluate your test suite on a regular basis. If you haven’t done this yet, you can get started by reading this blog post.
- Top 5 traps of test automation identifies five mistakes that developers make when they are writing automated tests. I like this post because it made me think (about excessive mocking), and I think that it is the sign of a useful blog post. Also, even though this blog post doesn’t reveal anything truly revolutionary, it is always useful to study other people’s opinions.
It’s Time for Feedback
Because I want to make this newsletter worth your time, I am asking you to help me make it better.
- If you have any feedback about this newsletter, share your thoughts on the comment section.
- If you have written a blog post about automated testing or software testing, ping me on Twitter.
- You can share this blog post on Twitter.
P.S. If you want to make sure that you don’t ever miss Java Testing Weekly, you should subscribe my newsletter.