Debugger-based Development
Having finally installed our SQL repository class last episode, albeit with the flat file as our source of truth, we start this episode checking our structured logs to make sure that things are working as we predicted.
Finding that they are, we need to add the ability to delete items from stock. We would like to prototype the user interface quickly, so we resort to the age-old technique of running the app in the debugger and hot reloading our code and the browser until we have something that looks and works well enough to commit to an acceptance test.
00:01:28 Checking the logs from our last deploy
00:02:57 Reviewing this story
00:03:47 Running our app in the debugger
00:04:59 Editing templates and reloading the web page
00:06:54 Adding a route for delete
00:07:55 We need to restart the server to add a route
00:08:08 Interactively inspecting the browser POST
00:09:29 Prototyping in the debugger
00:11:44 Hiding in-progress work with feature flags
00:16:27 A new approval test for the new UI
00:17:56 Refactoring our existing acceptance test to be more reusable
00:23:46 Extracting a test helper class
00:28:40 Creating a new acceptance test by duplicating an existing one
00:32:29 Finish the day on a failing test
This is part 78 of an exploration of where a Test Driven Development implementation of the Gilded Rose stock control system might take us in Kotlin. You can see the whole series as a playlist
• All Gilded Rose Episodes
and the code on GitHub
https://github.com/dmcg/gilded-rose-tdd
If you like this, you’ll probably like my book Java to Kotlin, A Refactoring Guidebook
(http://java-to-kotlin.dev). It's about far more than just the syntax differences between the languages - it shows how to upgrade your thinking to a more functional style.
I have some free time between producing videos and working for team Gilded Rose. If you like these videos I'd like to work with you - please get in touch - [email protected]