1"use strict";(globalThis.webpackChunkwebsite=globalThis.webpackChunkwebsite||[]).push([[1701],{63555(e,t,n){n.r(t),n.d(t,{assets:()=>l,contentTitle:()=>a,default:()=>u,frontMatter:()=>r,metadata:()=>i,toc:()=>c});var i=n(9469),o=n(74848),s=n(28453);const r={slug:"bdd/distilling-the-essence",title:"Webinar: Distilling the Essence",authors:[{name:"Theo England"}],tags:["Webinar"]},a=void 0,l={authorsImageUrls:[void 0]},c=[];function d(e){const t={p:"p",...(0,s.R)(),...e.components},{YouTubeVideo:n}=t;return n||function(e,t){throw new Error("Expected "+(t?"component":"object")+" `"+e+"` to be defined: you likely forgot to import, pass, or provide it.")}("YouTubeVideo",!0),(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(t.p,{children:"When creating our scenarios, we want to fully describe the desired functionality, but not over-describe it. We want our scenarios to do more than check for correct operation. We want to paint a picture of what\u2019s intended that aids understanding by others (or even ourselves) in the future. Which details should we leave visible, and which should we hide? In this webinar presentation, we will look at ways to distil our scenarios down to their essence and remove distracting incidental details."}),"\n",(0,o.jsx)(t.p,{children:"In this webinar recording, George Dinwiddie, an experienced BDD writer, practitioner, and enthusiast, gives you some tips for writing scenarios which sing."}),"\n",(0,o.jsx)(n,{video:"-vgM1YiCea8"})]})}function u(e={}){const{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,o.jsx)(t,{...e,children:(0,o.jsx)(d,{...e})}):d(e)}},28453(e,t,n){n.d(t,{R:()=>r,x:()=>a});var i=n(96540);const o={},s=i.createContext(o);function r(e){const t=i.useContext(s);return i.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:r(e.components),i.createElement(s.Provider,{value:t},e.children)}},9469(e){e.exports=JSON.parse('{"permalink":"/blog/bdd/distilling-the-essence","source":"@site/blog/2019-03-27-distilling-the-essence.mdx","title":"Webinar: Distilling the Essence","description":"When creating our scenarios, we want to fully describe the desired functionality, but not over-describe it. We want our scenarios to do more than check for c
1orrect operation. We want to paint a picture of what\u2019s intended that aids understanding by others (or even ourselves) in the future. Which details should we leave visible, and which should we hide? In this webinar presentation, we will look at ways to distil our scenarios down to their essence and remove distracting incidental details.","date":"2019-03-27T00:00:00.000Z","tags":[{"inline":true,"label":"Webinar","permalink":"/blog/tags/webinar"}],"hasTruncateMarker":true,"authors":[{"name":"Theo England","socials":{},"key":null,"page":null}],"frontMatter":{"slug":"bdd/distilling-the-essence","title":"Webinar: Distilling the Essence","authors":[{"name":"Theo England"}],"tags":["Webinar"]},"unlisted":false,"prevItem":{"title":"Podcast: Testing with Alex Schladebeck","permalink":"/blog/podcast/alex-schladebeck-on-testing"},"nextItem":{"title":"CukenFest: Q&A with Bruno Boucard and Thomas Pierrain","permalink":"/blog/events/cukenfest-asks-bruno-boucard-and-thomas-pierran"}}')}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.