From 0cda088b41e6e2a12df267ea4341d31ed18712e5 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Fri, 13 Sep 2019 14:50:19 +0100 Subject: [PATCH] Live blogging from SymfonyLive London 2019 --- source/_posts/2019-09-13-live-blogging-symfonylive-london.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_posts/2019-09-13-live-blogging-symfonylive-london.md b/source/_posts/2019-09-13-live-blogging-symfonylive-london.md index 95652cc1..0cadae91 100644 --- a/source/_posts/2019-09-13-live-blogging-symfonylive-london.md +++ b/source/_posts/2019-09-13-live-blogging-symfonylive-london.md @@ -447,6 +447,10 @@ SPAs are sometimes teh right solution. Why do they want to use it, can the same - Then I should be on '/flight/LTN-WAW' - Add I should see "Your flight has been booked." in "#result" * In the BDD way - what is the business logic? What is the value for this scenario? What is the reason 'why', and who benefits from this? + * We just need to know that there are 5 seats left on a flight + * Talk and communicate about how the feature is going to work - not just developers + * BDD aids communication + * Can we get a different outcome when the context changes? ## Migrating to Symfony one route at a time (Steve Winter)