[{"_1":2,"_46":-5,"_47":-5},"loaderData",{"_3":4,"_14":15,"_44":-5,"_45":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_43":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNDk4Mg","title","Java For Testers","state","published","contactAuthorMethod","email","aboutText","

People ask me what books I recommend to learn Java. And I have a few books that I thoroughly recommend, but they are not aimed at beginners.

Those that are aimed at beginners, I re-read recently and came to the conclusion that they would confuse more than help, and they don't help people become productive fast.

I wanted to write a book that gets testers started fast, is easy to follow, and has examples related to their work.

I have a companion web site for the book at javafortesters.com

Who is it for?

This book is for people who want to learn Java. Particularly people on a team that want to learn Java, but who aren't going to be coding the main Java application i.e. Testers, Managers, Business Analysts, Front End Developers, Designers, etc.

If you already know Java then this book may not be for you.

It is aimed at beginners.

I cover 'just enough' to get people writing tests and abstraction layers, but I don't really go down into a lot of detail. For example, I cover the basics of Inheritance, but don't really cover Interfaces in detail. I explain the concept of Interfaces, because we need to know it to understand Collections, but not how to write them.

Why? Because I want to cover enough to get people started, and working. I don't want to overload them. Once they are on their way, and have gained some experience. Then, when they are ready, they should have the basic knowledge to let them understand the additional concepts.

Why 'for testers'?

Java Developers coding production applications in Java need to learn Java differently from other people on the team.

Throughout my career I have written thousands of lines of Java code, but I have rarely had to compile the code into an application. Yet, when we learn Java, one of the first things we learn is 'javac' and the 'main' method.

Most of the code I write is wrapped up in a JUnit @Test method.

Everytime I have taught Java to testers or other people on the team, I start with a JUnit @Test method and show them how to run tests from the IDE.

Testers, and other people on the team use java differently, and I think we need a different order and approach to learning Java.

Source Code

You can find the source code for all examples and exercises used in the book over on github:

github.com/eviltester/javaForTestersCode

All example code in the book is automatically pulled from the source code, so it will work.

","authors",[30],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci81MTc2","name","Alan Richardson",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://secure.gravatar.com/avatar/56dbf818e219090fadfd421789744b9d?r=pg&d=mm","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author