JUnit 5: The Rise of Jupiter (Yaroslav Yermilov, @EPAM) (slides, src, video)
The planet Jupiter (5th! in the Solar System) needs 11 years to make one complete orbit around the Sun. So do JUnit needs 11 years to get a new major release, which means it’s going to be really huge.
Milestone 3 is already available and GA is scheduled on Q3 2017, so now it’s the best time learn and discuss how automating testing is going to look like very soon.
In this talk we will go through JUnit 5 changes and see how they will influence test code we write. Also we will discuss JUnit 5 architectural approach, how it can be extended and how it turns JUnit from test framework into test platform.
During the meetup, we are going to overview Project Reactor in depth and trying to understand how to use correctly given functionality and rebuild imperative web application to reactive one.
1. Project Reactor overview.
2. Imperative Application analyzing (2 pages web application with the Gitter integration and plain DB for event logging)
3. Test Refactoring
4. Application refactoring
In this article we will try to examine current state of the automated testing concept in the Java world. As a reference, we will go through basic and advanced spock-framework features and compare them with what JUnit4/JUnit5/TestNG/Hamcrest/AssertJ/Mockito/whatever can offer instead. We will try to understand Spock philosophy and find out both pragmatic and emotional answer to the questions: should I use spock-framework in the year of 2016? how to convince my manager that “yes, we should”? how to convince my teammates that “no, we shouldn’t”?
What’s About Modern Unit Testing?
To my mind, automated testing is one of the most powerful software development concept suggested so far.Read more …
Many organizations are working hard to be agile. They have mostly mastered the non-technical aspects of agile development, however, the major impediments come from not embracing some key technical practices. Evolving an application requires, amount other things, evolving the design and architecture, but that has risks.
In this workshop, we will focus and learn some key technical practices that will help us evolve applications based on the feedback cycles that agile development heavily relies upon. We will learn design principles and practices that help reduce risk involved often in evolving software. Read more…