Java for Testers

TLDR; We can use JUnit to execute code to support any type of testing.

I have deliberately created a failing test. Obviously deliberately since I would never ever create such simple issues in code.

TLDR; I try to write tests at an appropriate semantic level so I never need to create dependencies between @Test methods, I re-use abstraction calls instead of dependencies between @Test methods.

We don’t have to build full applications to create test tools. Sometimes we write throwaway tests.

An explanation of the Java Main method, and why we don’t really need it when automating.

In the book Java For Testers, I teach Java slightly differently to make it easier to learn. Let me explain how.

I just installed JDK 1.8 and had a problem configuring and switching versions.

Since I do receive this question via email quite a lot, I will answer it as an FAQ.

When you run your tests in IntelliJ you may have seen an output where only the failing tests are shown in the run pane tree.

If you see the “Maven projects need to be imported” popup in IntelliJ, then do click “Enable Auto-Import”.