Using abstract base classes to reduce risk of Spring context overall issues with Spring (Boot) integration tests.
Integration Testing Your Spring
WebClients with Wiremock (4 mins read).
How to write integration tests using Wiremock, for use with
@Scheduled annotations with Spring (Boot) (2 mins read).
How to test your Spring (Boot) scheduling without waiting for hours.
Filters When using
WebMvcTest (1 mins read).
How to exclude specific
Filters from running when performing
How to write integration tests using
MockWebServer with Spring Boot, for use with
How to write integration tests using
RestClientTest with Spring Boot, for use with
How to Create and Unit Test Java Bean Validation Annotations (12 mins read).
A guided example through what the different type of annotation
ElementTypes are, with respect to Bean Validation, and how to write unit tests for them.
Anyone thinking of / already using #Spectral for their API linting? I've written up how I've created a test harness to #TDD new API rules into our standards at https://www.jvt.me/posts/2021/12/22/spectral-jest/
Test Driven Development for Your Spectral Rules, using Jest (7 mins read).
How to write unit tests for Spectral API linting, in a test-driven development fashion.
Shift Your Testing Left with Spring Boot Controllers (5 mins read).
How to break down your tests for Spring Boot controllers, which could be used when performing Test Driven Development.
The thing that I found most valuable - and most generally underrated - from learning TDD 5 years into my career is the art of developing by making lots of small, targeted commits that each deliver an increment but leave the codebase deployable. Multiple commits per day.
Jez Humble (@jezhumble)Sun, 07 Nov 2021 17:28 GMT
I describe TDD, and practically every other software development technique as "neither necessary nor sufficient, but sometimes useful". Zealotry of TDD or any other practice is often a consequence of Dunning-Kruger; a lack of awareness of how effective other techniques can be.
IMO, a snazzy rebrand at this stage would only be helpful if we could also stop people framing TDD as a silver bullet, and acknowledge that it is just one of many useful strategies that have different Value vs. Cost trade offs in different circumstances. Seems unlikely though..🙂
Dave Smith (@davidjamessmith)Mon, 27 Sep 2021 12:03 +0000
Daniel Terhorst-North (@tastapod)Mon, 27 Sep 2021 12:43 +0000
I hear some "OGs" telling devs you don't need TDD anymore after you've done it "long enough" The design feedback and safety and 20 other things TDD gives us, even the oldest practitioners we know we can't do without. I personally will never be ditching it. Don't buy it. #TDD
Dave Schinkel (@DaveSchinkel)Tue, 12 Jan 2021 21:13 GMT
Recommended read: How to level up your TDD skills? https://deniseyu.io/2018/07/05/leveling-up-tdd.html
Recommended read: TDD https://ronjeffries.com/articles/019-01ff/tdd-one-word/
This is an interesting read - I'm a big fan of TDD but a few things here hold true
Recommended read: Against TDD http://neopragma.com/index.php/2019/09/29/against-tdd/
A few reasons explaining why you should be writing unit tests for your functional tests.
Revert 'Some knowledge-sharing news' (5 mins read).
The unfortunate decision to cancel my Packt training courses.
Using the example of deploying and running a Java JAR file as a way to show the lifecycle of a fully test-driven Chef cookbook.
Some exciting job and knowledge-sharing news (4 mins read).
Moving into Quality Engineering, publishing Chef training courses, conference speaking about Chef at OggCamp and the complex mess that is this very static website at DevOpsDays London.
include_recipes with Chef and ChefSpec (2 mins read).
How to best test
include_recipes within your Chef recipes, as well as how to ensure that you aren't running any dependent recipes in your tests.
You're currently viewing page 1 of 1, of 24 posts.