mrtns

Abstract

Behaviour Driven Development, like any other dogma in software development, is a complicated beast. It's proselytized by the zealots, and abdicated by the trolls. The practical reality is somewhere in between. And the best we can do is arm ourselves with understanding.

This workshop will attempt to cut through to the core of BDD. We will learn the history and theory behind it, show the outputs of its evolving practice, and explore how to incorporate it into our current work.

BDD finds itself at the intersection of a lot of different disciplines. This is ultimately what makes it so effective, fruitful and exciting. After all, building the right software is just as important as (if not more than) building the software right.

mrtns

Abstract

Behaviour Driven Development, like any other dogma in software development, is a complicated beast. It's proselytized by the zealots, and abdicated by the trolls. The practical reality is somewhere in between. And the best we can do is arm ourselves with understanding.

BDD finds itself at the intersection of a lot of different disciplines. The majority of those are non-technical. This workshop will focus on the technical aspects. Having a solid understanding of these will allow practicioners to focus instead on the really important parts, instead of getting caught up in implementation details.

Syllabus

mrtns

# MySQL is in UTC timezone

SELECT @@global.time_zone, @@session.time_zone, @@system_time_zone, TIMEDIFF(NOW(), UTC_TIMESTAMP);

/*
+----------------------------------------------------------------------------------------+
|@@global.time_zone|@@session.time_zone|@@system_time_zone|TIMEDIFF(NOW(), UTC_TIMESTAMP)|
+----------------------------------------------------------------------------------------+
|SYSTEM            |SYSTEM             |UTC               |00:00:00                      |
+----------------------------------------------------------------------------------------+

mrtns

WYSIWYG Chart Editors

• Quartz Chartbuilder

GUIs for Exploration

• Quartz Atlas

Resources

mrtns

• Configuring IPython Notebook Support for PySpark
• Project Jupyter grant proposal
  Project Jupyter: Computational Narratives as the Engine of Collaborative Data Science

mrtns

This variation of a bivariate area chart uses clipping to alternate colors. When New York is warmer than San Francisco, the difference between the two is filled in green. When San Francisco is warmer, the difference is filled in red. A similar technique was used by William Playfair all the way back in 1786.

mrtns

http://www.unit-testing.net/CurrentArticle/How-To-Use-Model-View-Presenter-With-AspNet-WebForms.html

http://www.hanselman.com/blog/OneASPNETSneakPeekElegantWebFormsAndSnowballsInHell.aspx

http://www.ctothoughts.com/2011/11/testing-aspnet-webforms.html

http://www.aaron-powell.com/posts/2010-05-18-testing-messaging-within-a-presenter.html

mrtns

Approaches

• Write a single spec. Script multiple runs. Use tags to define which scenarios to execute on each run
• Write a single spec. Script multiple runs. Use spec tables to define different assertions to perform on each run
• Write a spec. Duplicate a spec for each variation. Set up run in Using block of spec

Notes

Variations

• envrionment

mrtns

https://developer.apple.com/library/mac/documentation/AppleApplications/Reference/SafariWebContent/UsingtheViewport/UsingtheViewport.html

http://webdesignerwall.com/tutorials/viewport-meta-tag-for-non-responsive-design/comment-page-1#comments

http://blog.javierusobiaga.com/stop-using-the-viewport-tag-until-you-know-ho

http://stackoverflow.com/questions/8735457/scale-fit-mobile-web-content-using-viewport-meta-tag
http://stackoverflow.com/questions/18466871/conditional-viewport-scale-to-fit-when-screen-width-is-too-small-or-too-big

http://dev.opera.com/articles/view/an-introduction-to-meta-viewport-and-viewport/

mrtns

BDD

“BDD is a second-generation, outside-in, pull-based, multiple-stakeholder, multiple-scale, high-automation, agile methodology. It describes a cycle of interactions with well-defined outputs, resulting in the delivery of working, tested software that matters.”

Goals

2. Quality

1. Go Faster

Theory, Practice