�ݺ�ߣshows by User: etldan

�ݺ�ߣshows by User: etldan / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: etldan / Wed, 11 Feb 2015 05:53:27 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: etldan Living with acceptance tests: Beyond Write-Once (XP NYC) /slideshow/living-with-acceptance-tests-beyond-writeonce-xp-nyc/44542518 livingwithacceptancetests-150211055327-conversion-gate02
This presentation is from the XP NYC meetup. It was presented on February 10, 2015. Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations.]]>
This presentation is from the XP NYC meetup. It was presented on February 10, 2015. Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations.]]> Wed, 11 Feb 2015 05:53:27 GMT /slideshow/living-with-acceptance-tests-beyond-writeonce-xp-nyc/44542518 etldan@slideshare.net(etldan) Living with acceptance tests: Beyond Write-Once (XP NYC) etldan This presentation is from the XP NYC meetup. It was presented on February 10, 2015. Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/livingwithacceptancetests-150211055327-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds" /> This presentation is from the XP NYC meetup. It was presented on February 10, 2015. Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations.

Living with acceptance tests: Beyond Write-Once (XP NYC) from Daniel Wellman

]]> 447 3 https://cdn.slidesharecdn.com/ss_thumbnails/livingwithacceptancetests-150211055327-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Living with Acceptance Tests: Beyond Write-Once /slideshow/living-with-acceptance-tests-beyond-writeonce/39776844 livingwithacceptancetests-141001194900-phpapp02
Presented at CukeUp! NYC 2014 in Brooklyn, NY. Session description: Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations.]]>
Presented at CukeUp! NYC 2014 in Brooklyn, NY. Session description: Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations.]]> Wed, 01 Oct 2014 19:49:00 GMT /slideshow/living-with-acceptance-tests-beyond-writeonce/39776844 etldan@slideshare.net(etldan) Living with Acceptance Tests: Beyond Write-Once etldan Presented at CukeUp! NYC 2014 in Brooklyn, NY. Session description: Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/livingwithacceptancetests-141001194900-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Presented at CukeUp! NYC 2014 in Brooklyn, NY. Session description: Acceptance tests have become a common part of building software for an agile process. However, I've observed a trend of growing build times - with teams saying "Our build is 15 minutes... well, actually it's 45 minutes because our Cucumbers took so long, so we parallelized the cukes." One reason for this may be that teams treat their acceptance tests as "Write-Once": create for a new story, get them to pass, and leave them be. In this talk we'll explore the technical and social forces that cause an acceptance test suite to grow, and discuss some ways to refactor and improve these tests. We'll touch on hexagonal architecture, declarative vs. imperative style, and alternate Cucumber step implementations.

Living with Acceptance Tests: Beyond Write-Once from Daniel Wellman

]]> 692 3 https://cdn.slidesharecdn.com/ss_thumbnails/livingwithacceptancetests-141001194900-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Anatomy of a Gem: Bane /slideshow/anatomy-of-a-gem-bane/32519307 baneanatomyofagem-140319230246-phpapp02
Inside the design decisions of Bane, a test harness for sockets. This talk discusses the key design decisions of Bane, presents some code, and looks at some of Bane's automated tests.]]>
Inside the design decisions of Bane, a test harness for sockets. This talk discusses the key design decisions of Bane, presents some code, and looks at some of Bane's automated tests.]]> Wed, 19 Mar 2014 23:02:46 GMT /slideshow/anatomy-of-a-gem-bane/32519307 etldan@slideshare.net(etldan) Anatomy of a Gem: Bane etldan Inside the design decisions of Bane, a test harness for sockets. This talk discusses the key design decisions of Bane, presents some code, and looks at some of Bane's automated tests. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/baneanatomyofagem-140319230246-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Inside the design decisions of Bane, a test harness for sockets. This talk discusses the key design decisions of Bane, presents some code, and looks at some of Bane's automated tests.

Anatomy of a Gem: Bane from Daniel Wellman

]]> 539 4 https://cdn.slidesharecdn.com/ss_thumbnails/baneanatomyofagem-140319230246-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 How to Start Test-Driven Development in Legacy Code /slideshow/how-to-start-testdriven-development-in-legacy-code-12982341/12982341 testinglegacycode-120518074437-phpapp01
From The New York XP & Agile Meetup Group presentation on May 17, 2012. http://www.meetup.com/xp-26/events/16214945/]]>
From The New York XP & Agile Meetup Group presentation on May 17, 2012. http://www.meetup.com/xp-26/events/16214945/]]> Fri, 18 May 2012 07:44:36 GMT /slideshow/how-to-start-testdriven-development-in-legacy-code-12982341/12982341 etldan@slideshare.net(etldan) How to Start Test-Driven Development in Legacy Code etldan From The New York XP & Agile Meetup Group presentation on May 17, 2012. http://www.meetup.com/xp-26/events/16214945/ <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testinglegacycode-120518074437-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> From The New York XP & Agile Meetup Group presentation on May 17, 2012. http://www.meetup.com/xp-26/events/16214945/

How to Start Test-Driven Development in Legacy Code from Daniel Wellman

]]> 1231 5 https://cdn.slidesharecdn.com/ss_thumbnails/testinglegacycode-120518074437-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Agile Ajax: The Google Web Toolkit Experience /slideshow/agile-ajax-the-google-web-toolkit-experience/5560970 gwtexperience-101025200408-phpapp02
These slides are from the Agile 2009 Presentation "Agile Ajax: The Google Web Toolkit Experience." This talk discussed where GWT was a good fit in an Agile development process, and where it was not. ]]>
These slides are from the Agile 2009 Presentation "Agile Ajax: The Google Web Toolkit Experience." This talk discussed where GWT was a good fit in an Agile development process, and where it was not. ]]> Mon, 25 Oct 2010 20:04:06 GMT /slideshow/agile-ajax-the-google-web-toolkit-experience/5560970 etldan@slideshare.net(etldan) Agile Ajax: The Google Web Toolkit Experience etldan These slides are from the Agile 2009 Presentation "Agile Ajax: The Google Web Toolkit Experience." This talk discussed where GWT was a good fit in an Agile development process, and where it was not. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/gwtexperience-101025200408-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> These slides are from the Agile 2009 Presentation "Agile Ajax: The Google Web Toolkit Experience." This talk discussed where GWT was a good fit in an Agile development process, and where it was not.

Agile Ajax: The Google Web Toolkit Experience from Daniel Wellman

]]> 811 2 https://cdn.slidesharecdn.com/ss_thumbnails/gwtexperience-101025200408-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-etldan-48x48.jpg?cb=1606755209 I am a software developer who is passionate about building and helping others build great software. I’m a practitioner of Extreme Programming and Agile development methodologies, and am especially interested in Test Driven Development and design. www.danielwellman.com/ https://cdn.slidesharecdn.com/ss_thumbnails/livingwithacceptancetests-150211055327-conversion-gate02-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/living-with-acceptance-tests-beyond-writeonce-xp-nyc/44542518 Living with acceptance... https://cdn.slidesharecdn.com/ss_thumbnails/livingwithacceptancetests-141001194900-phpapp02-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/living-with-acceptance-tests-beyond-writeonce/39776844 Living with Acceptance... https://cdn.slidesharecdn.com/ss_thumbnails/baneanatomyofagem-140319230246-phpapp02-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/anatomy-of-a-gem-bane/32519307 Anatomy of a Gem: Bane