Testing improvements in Spring Boot 1.4

One of the nice things about working for Pivotal is that they have a great agile development division called Pivotal Labs. The teams within Labs are big proponents of Lean and XP software methodologies such as pair programming and test-driven development. Their love of testing has had a particular impact on Spring Boot 1.4 as we’ve started to get great feedback on things that could be improved. This blog post highlights some of the new testing features that have just landed in the latest M2 release.


SpringOne Platform

The Bigger Picture

Let’s talk about Pivotal. Our ambition is to make business more agile, to reduce the time around the innovation loop; speed is the single biggest advantage an organization can have. Pivotal’s main “product” is agility. This translates naturally into technology. Microservices are well-defined, small, easy-to-evolve, independently deployable batches of functionality. They lend themselves to rapid iteration because they’re small. Spring Boot and the Spring ecosystem make short work of standing up new microservices and applications, and Spring Cloud handles the complexity in distributed computing. Cloud Foundry automates the continuous deployment and management of applications. Distributed systems create valuable data which, when processed, can help drive direction. Pivotal Labs, our transformation arm, is a pioneer in agile development methodologies and continuous delivery, both essential when iterating in a dynamic market.