Why do I write tests?

I was asked recently why we write tests for code. This is a topic I have spent a lot of time discussing and teaching others about so I decided to write a post documenting my answers. Story Line Let’s say a QA engineer finds a bug in a web application before a critical release. There…

SOLID Programming (1) – Single

SOLID is an acronym for several of the most useful OOP design principles: Single Responsibility Open/Closed Liskov Substitution Interface Segregation Dependency Inversion In this post, I will cover the first principle, Single Responsibility. I hope these posts will give you an understanding of how these principles can improve the way you write code and maybe…

3 Most Intriguing Features of JUnit 5

I wanted to put together a post of the three most interesting features of JUnit 5 I found. Some of them are syntactical sugar, but some are things I have felt have been missing from previous versions of JUnit. 1. Expected Exceptions The first example is something I have always felt out of place in…

Exciting Features in JUnit5

This past July, Junit made some significant changes to their API. I’m just getting around  now to testing them and I wanted to let you know about some new the big changes! They have restructured some of their packages from org.junit to org.junit.jupiter.api @Before is now @BeforeEach @BeforeClass is now @BeforeAll @After is now @AfterEach @AfterClass is…