[hemmerling] Specification by Example, Modelling by Example

Related pages:

• System Design.
• Testing.
• Textual and Graphical Modeling by Domain Specific Languages.
• Unit Test / Module Test.

• Google+ "DDD Germany", with “Google Hangout” video conference events.
  • YouTube "DDD Channel".
• Skills Matter "CukeUp! 2013" in London, UK, 2013-04-13.
• Speech “BBD Hands-on with Python”.
  • Slides SlideShare "BBD Hands-on with Python. Practical Hands-on Workshop about 'Behaviour Driven Development', implementing the Game 'CodeBreaker' on Python 2.7 as Example" ( SlideShare "BBD Hands-on with Python. Practical Hands-on Workshop about 'Behaviour Driven Development', implementing the Game 'CodeBreaker' on Python 2.7 as Example" ).

• Stakeholder Whisperer / everzet “Modelling by Example”.
  • Hacker News "Introducing Modelling by Example (everzet.com)".
  • Stakeholder Whisperer "Introducing Modelling by Example ( formerly the artcile was at everzet's blog ).
• Skills Matter "Modelling by Example".

• Blog article Red Badger "What is Specification by Example?" → “What are the differences between Specification by example, Behaviour-Driven development (BDD) and Acceptance Testing-Driven Development (ATDD)?” #.
• YouTube "Christian Hassa: Specification By Example".

• EN.Wikipedia "User story".
• Book Mike Cohn "User Stories: für die agile Software-Entwicklung mit Scrum, XP u.a.".
• Mike Cohn's Connextra Format
  "As a 'role'
  I want 'features'
  So that 'business value'"
• A variant format, featured by The RSpec Book
  "In order to 'business value'
  As a 'role'
  I want 'features'"

• Github "cucumber / cucumber": "Gherkin" #
• Wikipedia:
  • EN.Wikipedia "Behavior Driven Development"
  • DE.Wikipedia "Behavior Driven Development" - “Given, When, Then” #.

• Dan North & Associates.
  • Dan North & Associates "Introducing BDD".
  • Dan North & Associates "What’s in a Story?".
• Wikipedia.
  • EN.Wikipedia "Behavior Driven Development"
  • DE.Wikipedia "Behavior Driven Development" #.
• Blog article Visiblox "Behaviour Driven Development for .NET developers".
• Blog article Steve Sanderson "Behavior Driven Development (BDD) with SpecFlow and ASP.NET MVC".
• Blog article Ryan Lanciaux "Gherkin style specification testing in .NET".

• Agile FAQs.
• Agile FAQs - Naresh Jain.
  • Blog Agile FAQs Blog "Managed Chaos. Naresh Jain's Random Thoughts on Software Development and Adventure Sports.
  • SlideShare "Naresh Jain".
  • soft tests "Naresh Jain: Acceptance Test Driven Development".

• Domain-Driven Design Community.
• “Value Objects”.
  • InfoQ "Power Use of Value Objects in DDD".
• EN.Wikipedia "Domain-driven design", DE.Wikipedia "Domain-Driven Design".

• Ports and Adapters.
  • Alistair Cockburn "Hexagonal architecture" - “The Pattern: Ports and Adapters ('Object Structural')”#.
    • Communication between different layers: “Think in slices, not in layers ( Lasagna )”!
  • Dependency inversion principle.
    • EN.Wikipedia "Dependency inversion principle", DE.Wikipedia "Dependency-Inversion-Prinzip".
    • EN.Wikipedia "Protocol (object-oriented programming)", EN.Wikipedia "Interface (Java)", DE.Wikipedia "Schnittstelle (Objektorientierung)".
    • If your favourite object oriented programming language does not have “Interfaces”, you may alternatively also use an “Abstract Class”.
• Repository Pattern.
  • By Martin Fowler - No DDD approach !
    • Microsoft MSDN Library "The Repository Pattern".
    • Norbert Eder "Das Repository Pattern anhand eines Beispiels inkl. Tests".
  • By Eric Evans - DDD approach: It provides the translation from data layer to domain language .

• Dennis Traub.
  • Blog Dennis Traub - Mein Blog zu Softwareentwicklung, Büchern und was mir sonst noch so in den Sinn kommt....
  • XING "Dennis Traub", LinkedIn "Dennis Traub".
  • Twitter "Dennis Traub. @DTraub. Software developer interested in craftsmanship. Entrepreneur, speaker, passionate reader. Learning addict, writer, husband and father. Paderborn, Germany. dennistraub.de".
  • Speech SQL Saturday #230 "DDD und relationale Daten - Ein Widerspruch?", 2013-07-13.
• Markus Völter - DSL Engineering.
  • Book Markus Voelter "Generic Tools, Specific Languages".
    • Free PDF book download on the accompaning website Markus Völter - DSL Engineering.
  • Book Markus Voelter "DSL Engineering: Designing, Implementing and Using Domain-Specific Languages".
    • Free PDF book download on the accompaning website Markus Völter - DSL Engineering.

• EN.Wikipedia "Keyword-driven testing", EN.Wikipedia "Keyword-Driven Testing".
• Typical use case in the engineering industry: Testing of hardware, making use of Labview ( See National Instruments ( Labview, DIAdem ) ).

• EN.Wikipedia "Data-driven testing"

• Test-First Programming = You have the design of the application to be tested already in mind ( not just of the test code ).
• VersionOne - Agile Made Easier "Test-First Programming".

• Test Driven Development = You have a result in mind, but not a design of the application to be tested.
• Kent Beck.
• Don Wells "Extreme Programming: A Gentle Introduction".
• Bill Wake.
• XProgramming.com - “An Agile Development Resource”.

• Webcast O'Reilly Community, Harry Percival "TDD Web Development from Scratch. Test-Driven Development with Python", 60 minutes.
• “Is TDD dead?”-
  • YouTube "Is TDD dead?" with Martin Fowler, Kent Beck, David Heinemeier Hansson, 2014-05-09.
  • YouTube "Is TDD dead? [Part II]", 2014-05-16.

• EN.Wikipedia "Emergent Design".

• The OpenSource FitNesse, Github "unclebob/fitnesse", a Java 6 application. Support for C++, Python, Ruby, Delphi, C#,..
  • Brett Schuchert "FitNesse.Tutorials".
  • ButUncleBob.com.
    • ButUncleBob.com "FitNesse".
      • ButUncleBob.com "FitNesse": "FixtureCode".
  • EN.Wikipedia "FitNesse".
  • EN.Wikipedia "Framework for Integrated Test", DE.Wikipedia "Framework for Integrated Test" ( “FIT” ).
  • Tasks / functions.
    1. “Software development collaboration tool” → “Collaboratively define Acceptance Tests” ( additionally to xUnit tests ).
    2. “Software testing tool”.
    3. “Wiki”.
    4. “Web server”.
  • Fixture Gallery.
    • SourceForge "Fixture Gallery", SourceForge "Fixture Gallery" - “Simple, straight-forward examples of FIT/FitNesse fixtures for Java and .NET test environments. Documentation and examples are available in the form of a live FitNesse wiki and PDF”.
    • The free PDF book Gojko Adzic, Mike Stockdale, Jens Engel, Randy Coulman "Fixture Gallery: A cookbook for FIT/FitNesse tests".
    • Gojko Adzic - Building software that matters "Fixture Gallery" - “A cookbook for FIT/FitNesse tests”.
    • Gojko Adzic "FitNesse community web site": "Fixture Gallery".
  • Local installation on port 8888: “java -jar fitnesse-standalone.jar -p 8888”. The server can then be accessed by “http://localhost:8888/”.

• The OpenSource FIT for use with Fitnesse #.
  • Fit: Framework for Integrated Test.
  • SourceForge "FitLibrary", SourceForge "FitLibrary", Wiki SourceForge Wiki "FitLibrary".

• BerliOS Developer "PHPFIT" - FIT for PHP.

• Python.org "PyFIT 0.8a2 - Python version of the Framework for Interactive Testing", Github "pyfit".

• Mike Stockdale - OpenSource functional testing tools for .NET, using FitNesse and inspired by Fit.
  • Mike Stockdale "Fit Sharp" - “A set of open-source functional testing tools for .NET, inspired by the Framework for Integrated Test Fit”.
  • Github "Mike Stockdale".
    • Github "jediwhale/fitsharp" for Windows with .NET 3.5 - “Functional testing tools for .NET”.
• SourceForge "FitNesse.DotNet", SourceForge "FitNesse.DotNet", SourceForge ".NET FIT, FitLibrary for FitNesse, HTML" for Windows with .NET 2.0.

• FitNesse "Extend FitNesse".
  • Plugins:
    • “SLiM servers for different languages/environments”.
    • “SLiM fixtures”.

• butUncleBob.com "FitNesse UserGuide "SliM".
• FitNesse UserGuide "SliM" .
• FitNesse UserGuide "The Slim Protocol, version 0.4".

• The OpenSource robotframework, Google Code "robotframework. A generic test automation framework", GitHub "robotframework" in Python - “A generic test automation framework for acceptance testing and acceptance test-driven development (ATDD). It has easy-to-use tabular test data syntax and utilizes the keyword-driven testing approach. Its testing capabilities can be extended by test libraries implemented either with Python or Java, and users can create new keywords from existing ones using the same syntax that is used for creating test cases”.
• Google Code "robotframework-ride", GitHub "robotframework/RIDE" - “A light-weight and intuitive editor for Robot Framework test case files”.

• The deprecated Google Code "robotframework-seleniumlibrary. A web testing library for Robot Framework".
• GitHub "rtomac / robotframework-selenium2library - Selenium 2 (WebDriver) library for Robot Framework".

• Wiki Google Code Wiki "Robot Framework - A generic test automation framework".
  • Google Code Wiki "Robot Framework - A generic test automation framework" - UserGuide #.
• Wiki GitHub Wiki "robotframework/RIDE".
• Google Code "robotframework-seleniumlibrary. A web testing library for Robot Framework" - "Robot Framework Quick Start Guide".
• The tutorial Virtuous Programmer - Adventures of an autodidact "Robot Framework. Test Automation with Robot Framework" #.

• Gojko Adzic Building software that matters "Robot Framework review".
• codecentric "Thomas Jaspers: Robot Framework IDE (RIDE) – Overview".
• EN.Wikipedia "Robot Framework", DE.Wikipedia "Robot Framework".

• SourceForge "Software Automation Framework Support", SourceForge "Software Automation Framework Support" ( SAFS ) - “A software test automation framework supporting data-driven (aka keyword-driven) functional test automation and associated services”.
  • SourceForge "Software Automation Framework Support" - "Test Automation Frameworks".

• The OpenSource BDD development tool “JBehave” for Java.
  • JBehave, GitHub "jbehave" - no jars .
  • GrepCode "org.jbehave / jbehave-core" - “JBehave Core contains all the core functionality for running BDD stories”.
    • GrepCode "org.jbehave / jbehave-core / 3.9.5" - “jbehave-core-3.9.5.jar”, ” jbehave-core-3.9.5-sources.jar” .
  • MVNrepository "jbehave" - “jbehave-core-3.9.5.jar” .
  • Java2 "jbehave core < j < Jar File Download" - outdated jars .
  • Tutorial GitHub "jbehave/jbehave-tutorial".
    • “Behave Selenium Tutorials on the Etsy.com website”.
  • JBehave "Locating Stories" - “JBehave supports OpenDocument Text format via the ODF Toolkit”.

• GitHub "smartsquare/Jbehave_Examples".
• SlideShare "DanielRosowski".
  • SlideShare, DanielRosowski "Real Life TDD".
• SlideShare "Sascha Rodekamp".
  • SlideShare, Sascha Rodekamp "BDD with JBehave".
• EN.Wikipedia "Shopping cart", DE.Wikipedia "Einkaufswagen", EN.Wikipedia "Shopping cart software".

• Joe Colantonio "JBehave BDD – How to get Started using the Eclipse jBehave Plugin".
  • To install the Eclipse JBehave Plug-In, select “http://jbehave.org/reference/eclipse/updates/” as address by the Eclipse installation assistant.
• StackOverflow "Very simple step by step JBehave setup tutorial?" - Example of a story class and a steps class.
• University of Minnesota, UMWiki "To set up JBehave in a project in Eclipse".
• On Test Automation "Up and running with: JBehave".
• Codecentric Blog, Andreas Ebbert-Karroum "JBehave Configuration Tutorial".
• GitHub "ashrafuzzaman/Simple-jbehave-example".
• Warlock's Thoughts "JBehave - quick BDD example" with Spring Framework.
• Ryan Greenhall "Behaviour Driven Development: By Example".

• Jnario - “Executable Specifications for Java”.
• Jnario "Jnario Documentation".
• GitHub "sebastianbenz/Jnario".
• Sebastian Benz.
  • Sebastian Benz "Introducing Jnario - Executable Specifications for Java", 2012.
  • Sebastian Benz "Testing Web Apps with Selenium and Jnario", 2013.

• The OpenSource BDD development tool Specflow - Cucumber for .NET, GitHub "techtalk/SpecFlow" for .NET, Silverlight, Windows Phone, Mono - “Binding business requirements to .NET code”.
  • Wiki GitHub Wiki "SpecFlow".
  • LinkedIn "SpecFlow: Pragmatic BDD for .NET".
  • Twitter "SpecFlow, @specflow".
• The OpenSource BDD development tool NBehave, Google Code "nbBehave" for .NET.

• Bhat, GitHub "Behat" - “Open source Behavior Driven Development framework for PHP 5.3+”.
• Packagist - The PHP Package Repository "behat/behat. Scenario-oriented BDD framework for PHP 5.3".
• ThingShout "Getting Started with Behat".
• evenato tuts+ "BDD With Behat".

• The OpenSource PythonHosted "behave", Github "behave / behave", Github "jeamland / behave" - “A behaviour-driven development, Python style” #.
  • PythonHosted "behave - Comparison With Other Tools" - Comparison of “Behave”, “Cucumber”, “Lettuce”, “Freshen”.
  • PythonHosted "behave Tutorial".
  • PythonHosted "behave API reference".
  • Github "jenisys".
    • GitHub "jenisys" / "behave 1.2.4: Examples and Tutorials" #.
  • Manual installation:
    • The Python module “Behave” depends on the Python module “parse-type”, which depends on “parse”.
      • Python Package Index "parse".
      • Python Package Index "parse_type".
    • Manual installation: Unpack the downloads in different directories, and open a shell ( Powershell or Command.com on Windows ) in the directories, before executing the commands:
      1. “python setup.py parse”.
      2. “python setup.py parse_type”.
      3. “python setup.py behave”.
  • GitHub "behave/behave/tree/master/features" - Directory of .feature examples.
  • GitHub "behave/behave/blob/master/docs/parse_builtin_types.rst" - “Predefined Data Types in parse”.
  • The Python Standard Library / 7. String Services / "7.2. re — Regular expression operations".
  • GitHub Github "behave / behave" issues, ticket #216 by Rolf Hemmerling.

• Serenity BDD, GitHub "Serenity BDD. An automated acceptance tests reporting library (previously known as Thucydides)" - “Automated Acceptance Testing with Style. Serenity BDD helps you write better, more effective automated acceptance tests, and use these acceptance tests to produce world-class test reports and living documentation”.
  • Serenity BDD "Documentation".
• John Ferguson Smart.
  • John Ferguson Smart "Serenity BDD Tutorial #1 – introduction to web testing with Serenity BDD".

• Wakaleo Consulting, John Ferguson Smart "Thucydides", Archive.org "Wakaleo Consulting, John Ferguson Smart - Thucydides".
• GitHub "Thucydides BDD Reporting Library" - “Thucydides is a tool that lets you use WebDriver-based unit or BDD tests to write more flexible and more reusable WebDriver-based tests, and also to generate documentation about your acceptance tests, including a narrative description of test, along with the corresponding screen shots, and also high-level summaries and aggregations of the test r… ”.

• Book John Ferguson Smart: "BDD in Action. Behavior-Driven Development for the whole software lifecycle".

• GitHub.io "Spock Framework Reference Documentation", GitHub "Spock Framework".

• Book Konstantinos Kapelonis "Java Testing with Spock".
  • Accompanying Website Manning Publications "Java Testing with Spock".

• See Testing.

• Objective Partners Blog "Spock Mock Cheatsheet".
• GitHub.io GitHub.io "Spock Framework Reference Documentation" - "Class MockingApi".
• GitHub.io "Spock Framework Reference Documentation" - "Interaction Based Testing" - “How Are Mock Implementations Generated?”.
• Andre Steingress, Blog JVM Stuff "Spock - Mocking and Stubbing".
• Farenda "Spock Framework Mock".
• DZONE / Java Zone "Mocking Static Methods in Groovy".
• DZONE / Java Zone "Spocklight: Change Return Value of Mocked or Stubbed Service Based On Argument Value".
• StackOverflow "Grails / Spock: How to mock single method within class where method is called from within the class itself?".

• DZONE / Java Zone "Testing Java using the Spock Framework".
• DZONE / Java Zone "An introduction to Spock".
• Petri Kainulainen "Writing Unit Tests With Spock Framework: Creating a Gradle Project".
• ZeroTurnaround "Using Spock to test Groovy AND Java applications".
• EN.Wikipedia "Spock (testing framework)".

• PythonHosted "nose", Github "nose-devs", Python Package Index "nose", Read the Docs "nose" - “is nicer testing for python”.
  • Read the Docs "nose documentation / Testing with nose / -Testing tools".
• PythonHosted "compare", Github "rudylattae / compare", Python Package Index "compare" - “Alternative syntax for comparing/asserting expressions in Python. Supports pluggable matchers for custom comparisons”.
• PythonHosted "describe", Python Package Index "describe" - “An experimental behavioral framework inspired from rspec”.
• Hamcrest, Google Code "Hamcrest - library of matchers for building test expressions", GitHub "hamcrest", PythonHosted "PyHamcrest", Python Package Index "PyHamcrest".
  • Google Code "Hamcrest - library of matchers for building test expressions / Hamcrest Tutorial".
  • Google Code "Hamcrest - library of matchers for building test expressions / PyHamcrest Tutorial".
  • Read the Docs "PyHamcrest documentation", Read the Docs "PyHamcrest".
  • “PyHamcrest” can´t be updated by well-known automatic installation processes, on Python 2.7 even after a proper installation of the Python package “behave”. An installation attempt by “easy_install pyhamcrest” is aborted due to syntax errors in downloaded Python files and other faults . Is “PyHamcrest” just for Python 3.x or also still for Python 2.x ?!
• Should-DSL, PythonHosted "should_dsl", Github "hugobr/should-dsl", Python Package Index "should_dsl" - “Should assertions in Python as clear and readable as possible”.

• The OpenSource Concordion - “A tool for writing automated acceptance tests in Java”.
  • Concordion - Non-Java Versions.
    • Google Code "pyconcordion. Concordion Python Port (write concordion like html files, python fixtures and run it !)".
    • Google Code "concordion-net. A .NET port of the acceptance testing framework".

• The OpenSource Cucumber - behaviour driven development with elegance and joy, for Ruby.
  • Github "Cucumber".
  • EN.Wikipedia "Cucumber (software)".

• Chai - “A BDD / TDD assertion library for node and the browser that can be delightfully paired with any javascript testing framework”.

• Github " cucumber/cucumber-js - Pure Javascript Cucumber".

• Jasmine - “A behavior-driven development framework for testing JavaScript code”.
  • EN.Wikipedia "Jasmine (JavaScript framework)".
• Github "mhevery/jasmine-node".
• Github "grunt-contrib-jasmine".
• Paper magazine article Sag’s durch die Blume – Behavior-Driven Development mit Jasmine in iX, issue 8/2013.
  • Blog article Blogisticon - Das Holisticon-Blog, "Sag’s durch die Blume – Behavior-Driven Development mit Jasmine".
  • Github " simonox/Jasmine-Bar-Example" - The code related to the article in the paper magazine.
• Github "ibolmo/jasmine-jstd-adapter" for Google Code "js-test-driver - Remote javascript console".

• See.
  • Scripting Languages for Windows 2/2 - Windows Powershell.
  • Scripting Programming Languages for Windows 3/3 - Testing with Windows PowerShell.

• Github "cucumber/cucumber", "cucumber / examples / python".
• Github Wiki "cucumber/cucumber" - "Python".
• RubyForge "rubypython", RubyForge "rubypython".

• The OpenSource Github "rlisagor/freshen" - “Clone of the Cucumber BDD framework for Python”. A plugin for nose - is nicer testing for python.

• The OpenSource *Gabriel Falcão G. de Moura "Lettuce", Github "gabrielfalcao / lettuce" - “A BDD tool for python, 100% inspired on cucumber”.
• Important item to deal with and to communicate with are “world”, “context”, “step”.

• The OpenSource Github "heynemann / pyccuracy" - “A Behaviour-Driven-Development-style tool written in Python that aims to make it easier to write automated acceptance tests. It improves the readability of those tests by using a structured natural language – and a simple mechanism to extend this language – so that both developers and customers can collaborate and understand what the tests do”.

• Python Package Index "pytest-bdd" - “BDD library for the py.test runner”, “ytest-bdd implements a subset of Gherkin language for the automation of the project requirements testing and easier behavioral driven development. Unlike many other BDD tools it doesn't require a separate runner and benefits from the power and flexibility of the pytest. It allows to unify your unit and functional tests, easier continuous integration server configuration and maximal reuse of the tests setup”.
• GitHub " olegpidsadnyi / pytest-bdd".

• By the use of regular expressions, You may parameterize BBD script snippets, to help the reuse and recall of the same code, by several sentences.
• BDDWiki: BehaviourDrivenDevelopment.
• Functional process testing with JBehave and Camunda BPM:
  • Event “Test-driven business process modeling with camunda BPM” by users of camunda BPM platform, by Holisticon AG and camunda services GmbH in Hamburg, Germany ( 2013-11-26 ).
  • Holisticon AG Blog "Testgetriebene Geschäftsprozessmodellierung mit camunda BPM".
  • Github "camunda / camunda-bpm-testing".
  • Github "camunda / camunda-bpm-testing / camunda-bpm-jbehave".
• Speech “BDD in Python” by Gabriel Jacobsohn, Twitter "Gabriel Jacobsohn", GitHub "GJacobsohn", Stack Overflow "Gabriel Jacobsohn" on the regional meeting of Python User Group Hamburg ( 2014-02-04 ).
  • GitHub "GJacobsohn/bdd_vortrag".

• Serverspec - RSpec tests for your servers configured by Puppet, Chef or anything else - “With Serverspec, you can write RSpec tests for checking your servers are configured correctly. Serverspec tests your servers' actual state by executing command locally, via SSH, via WinRM, via Docker API and so on. So you don't need to install any agent softwares on your servers and can use any configuration management tools, Puppet, Chef, CFEngine and so on. But the true aim of Serverspec is to help refactoring infrastructure code”.
• GitHub "serverspec" - “RSpec tests for your servers configured by Puppet, Chef or anything else even by hand”.

• PyUseCase / TextTest / StoryText, in Python.
  • The successor SourceForge "StoryText", SourceForge "StoryText" ( formerly: “PyUseCase” ).
  • The successor TextTest, TextTest, SourceForge "TextTest", SourceForge "TextTest" ( formerly: “PyUseCase” ).
  • Facebook "Geoff Bache".
  • Emily Bache - coding is like cooking "PyUseCase 3.0", 2009-12-16.
• The OpenSource SpecFlow - Pragmatic BDD for .NET, Github "techtalk / SpecFlow" for Windows with .NET.
  • “SpecFlow aims at bridging the communication gap between domain experts and developers by binding business readable behavior specifications and examples to the underlying implementation”.
  • “Our mission is to provide a pragmatic and frictionless approach to Specification-By-Example for .NET projects”.
  • “SpecFlow also supports the concepts of Acceptance Test Driven Development (ATDD) and Behavior Driven Development (BDD), which are often used synonymously with Specification-By-Example”.

• The commercial Green Pepper for Java and .NET 2.0. Works together with Visual Studio, MS Build and Atlassian tools.
  • Blog Green Popper Blog.
• The commercial Thoughtworks Studios "Twist" for Java and for Groovy.
  • Blog Thoughtworks Studios Blog.
• The commercial imbus TestBench for Windows → Keyword-driven testing / table-driven testing / action word based testing.

• The commercial online service Relish - “Living documentation. Combine your product's documentation with cucumber tests. Publish, browse, search & share on Relishapp…”.

• Gojko Adzic - Building software that matters.
  • Book Gojko Adzic "Specification by Example: How Successful Teams Deliver the Right Software".
    • The companion website Specification by Example. How successful teams deliver the right software.
  • Book Gojko Adzic "Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing".

• MindMup "Gojko Adzic 'Specification by Example: How Successful Teams Deliver the Right Software'" by Rolf Hemmerling.

• The video Gojko Adzic - Blog article "Challenging requirements".
• Michael Bolton, DevelopSense "Blog: Testing vs. Checking".

• Book Caper Jones "Estimating Software Costs: Bringing Realism to Estimating".

• Book Donald C. Gause, Gerald M. Weinberg "Exploring Requirements".
• Book David J. Anderson, Donald G Reinertsen "Kanban: Successful Evolutionary Change for Your Technology Business".
• Book Jim Shore, Shane Warden "The Art of Agile Development".
• Book Craig Larman, Bas Vodde "Scaling Lean and Agile Development: Thinking and Organizational Tools for Large-Scale Scrum".
• Gojko Adzic - Blog article "Improving testing practices at Google".
• Book Mary Poppendieck, Tom Poppendieck "Implementing Lean Software Development: From Concept to Cash".
• Opinion by Gojko Adzic: “Many people I met at conferences misunderstand and think that incrementally building up a documentation system means oging back to the Waterfall ideas of big up-front analysis. During the presentation 'How to Sell BDD to the business' in November 2009, Dan North said that BDD is effectively V-Model compressedinto two weeks” .

• Book Richard Monson-Haefel "97 Things Every Software Architect Should Know".
• Book Frederick P. Brooks "The Mythical Man-Month. Essays on Software Engineering".
• Suggestion by Gojko Adzic: “Instead of trying to collaborate with business users on specifying how to put things into the system, we should start with examples of output”.
• Book Mark Denne, Jane Cleland-Huang "Software by Numbers: Low-Risk, High-Return Development".
• Feature Teams - Article “Craig Larman and Bas Vodde 'Feature Team Primer'” (PDF)).
• Chris Matts.
  • The once-free PDF book Archive.org "Chris Matts: Real Options at Agile 2009".
    • lulu_word_comic_vFinal.pdf ).
    • I am still looking for a free PDF copy of the book. Please contact me, if you have a freely downloaded item and if you are willing to share it with me, for free.
  • The free PDF book with Comics Chris Matts "Agile2010 Nashville. Gaylord Opryland Resort" ( The PDF book “Real Options at Agile 2009” is not available for (free) download at this site ) → “Feature Injection and Test Driven Requirements”.
  • Google + "Chris Matts - Album "Feature Injection".
  • Yahoo Groups "real_options_discussion · Real Options".
  • Blog Chris Matts - Blog "The IT Risk Manager ...based on practice rather than theory".
  • Blog Real options bloggers ( Olav Maassen, Chris Matts ).
    • Blog articleReal options bloggers ( Olav Maassen, Chris Matts ) "Lean and real options".
  • Twitter "Chris Matts".
  • InfoQ "'Real Options' Underlie Agile Practices".
  • C2 "Chris Matts".
• Book Ingrid Ottersten, Mijo Balic, Peter Corrigan "Effect Managing IT".
• Gojko Adzic - Blog article "Impact Mapping".
• Jeff Patton, AgileProductDesign.

• Book Craig Larman, Bas Vodde "Practices for Scaling Lean and Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum".
• Book Lisa Crispin, Janet Gregory "Agile Testing: A Practical Guide for Testers and Agile Teams".
• Suggestion by Gojko Adzic: “Implementing Specification workshops into Product Backlog Refinement ( PBR ) workshops”.
  • CollabNet, Michael James "The Backlog Refinement Meeting (or Backlog Grooming)".

• Book Donald C. Gause, Gerald M. Weinberg "Exploring Requirements".
• Gojko Adzic: "Examples make it easy to spot inconsistencies".
• Suggestion by Gojko Adzic: “Feedback Exercises”.
• Book Eric J. Evans: "Domain-Driven Design: Tackling Complexity in the Heart of Software".
• Balsamiq.
  • Blogs Balsamiq Blogs.
  • The commercial Balsamiq Mockups for Windows, Linux, MacOSX.
  • The commercial online service Balsamiq myBalsamiq - “The best way to do remote, collaborative UX Design”.
• The QUPER model by Björn Regnell.
  • The Video Björn Regnell "2009 Session: Supporting Roadmapping of Quality Requirements" - Product benefits curve:
    1. Utility.
    2. Diffentiation.
    3. Saturation.
  • Gojko Adzic - Blog article "QUPER model for better requirements".
• Gojko Adzic - Blog article "Agile in a Start-up Games Development Studio".
• Opinion by Gojko Adzic:
  • “Specifications with examples are acceptance tests”.
  • “Scripts are not specifications” .
    • “A script explains how something can be tested. It describes business functionality through lower-level interactions with the system. A script requires the reader to work back from the actions and understand what's really important. Scripts also bake the test into workflow and session constrains, which migh changein the future even when the underlaying”. business rules don´t change.
    • “A specification explains what the system does. It focusses on the business functionality in the most direct way possible. Specifications are shorter because because they describe buiness concepts directly. That makes them easier to read and understand than scripts”.

• Book Rick Mugridge, Ward Cunningham: "Fit for Developing Software: Framework for Integrated Tests".
• Suggestion by Gojko Adzic: “Specification should be in the domain language” → BDD.

• Suggestion by Gojko Adzic: “Avoid automating existing manual test scripts”.
• Suggestion by Gojko Adzic: “Don't check business logic though the user interface.”Traditional test automation tools mostly work by manipulating user interface objects. Most automation tools for exeutable specifications can go below the user interface and talk to application programming interfaces directly ( API ) .
• Suggestion by Gojko Adzic: “Automate below the skin of the application. Workflow and session rules can often be checked only against the user interface layer. But that doesn´t mean that the only option to automate those checks is to launch a browser. Instead of automating the specifications through a browser, several teams developing web applications saved a lot of time and effort going right below the skin of the application - to the HTTP layer”.
• Web Automation by direct HTTP automation:
  • twill: a simple scripting language for Web browsing - “twill supports automated Web testing and has a simple Python interface”.
  • WebRat - “Webrat - Ruby Acceptance Testing for Web applications”.
  • Selenium Browser automation framework, HtmlUnitDriver.
• Gojko Adzic suggests: “Specify user interface functionality at a higher level of abstraction”.
  • Gojko Adzic discovered: “Automating user interfaces. Almost all the teams I interviewed made the same mistake early on. They specified tests intended to be automated though user interface as series of technical tips, often directly writing user interface automation commands in their specification” .
  • Pierre Veragen realized “User interface tests were task oriented ( click, point ) and therefore rightly coupled to the implementation of the GUI, rather thant activity oriented.... FitNesse tests wre organized according to the way UI was set up”.
    • “When the UI was updated, all these tests had to be updated...”.
    • “A small change to the GUI, adding a ribbon control, broke everything. There was no way we could update the tests”.
  • Lance Walton explains:
    • “The next stage was to understand that the workflow still had to do with the solution we designed, so actully let's forget about workflow and focus on what the user is trying to achieve”.
    • “So we had pages that contained the details, then we had the task level above that, and then we finally had the goal that the user is trying to achieve”.
  • Gojko Adzic suggests: “Avoid recorded UI tests”, “Many traditional test automation tools offer record-and-replay user interface automation”, “This is one of the areas where automation of executable specifications is quite different than traditional automatied regression testing”.
  • Gojko Adzic defines “Three level of user interface automation”.
    1. Technical activity level - What are the technical steps required to exercise individual workflow steps ?
       • For example: Open the shop home page, log in with “test user” and “testpassword”, got to the ”/book” page, click the first image with the “book” CSS-class, wait for the page to load, click the Buy Now link, and so on.
    2. User workflow level - How can a user exercise the functionality through the UI, on a higher activity level ?
       • For example: Put two books in a shoppoing cart, enter address details and verify that delivery options include free delivery.
       • The automation layer should handle the workflow level by combining blocks composed at the technicial activity level.
    3. Business rule level - What is the test demonstrating or exercising ?
       • For example: Free delivery is offered to customers who order two or more books”. Specifications should be described at the business rule level.
• Gojko Adzic - Blog article "How to implement UI testing without shooting yourself in the foot".

• EN.Wikipedia "Continuous integration", DE.Wikipedia "Kontinuierliche Integration".
• Book Steve Freeman, Nat Pryce: "Growing Object-Oriented Software, Guided by Tests".

• Hemal Kuntawala "How we build quality software".
• Gojko Adzic - Blog article "Are tools necessary for acceptance testing, or are they just evil?".
• Gojko Adzic - Blog article "Shock therapy agile adoption at 7Digital".
• Michael Bolton, DevelopSense.
  • Michael Bolton, DevelopSense "Blog: Acceptance Tests: Let’s Change the Title, Too".
• Alistair Cockburn.
  • Alistair Cockburn "Sacrifice one person strategy".
• Craig Larman, Bas Vodde "Acceptance Test-Driven Development with Robot Framework".
• Dan North "Whose domain is it anyway?".
• James Shore, The Art of Agile.
  • James Shore, The Art of Agile "Alternatives to Acceptance Testing".
  • James Shore, The Art of Agile "The Problems With Acceptance Testing".
• Lance Walton, Casual Miracles "Writing Maintainable Acceptance Tests".

• Markus Gärtner - Software Testing, Craftsmanship, Leadership and beyond.
  • Book Markus Gärtner "ATDD by Example: A Practical Guide to Acceptance Test-driven Development".
  • Book Markus Gärtner "ATDD in der Praxis: Eine praktische Einführung in die Akzeptanztest-getriebene Softwareentwicklung mit Cucumber, Selenium und FitNesse".
  • dpunkt.verlag GmbH "Markus Gärtner: ATDD in der Praxis".
  • There are 2 throughout examples covered in the book:
    1. Airport parking lot ( “Parking calculator” ) → in Ruby, using Cucumber.
    2. Traffic light software system → in Java, using FitNesse, SLiM, JUnit.

• Book John Ferguson Smart: "BDD in Action. Behavior-Driven Development for the whole software lifecycle".
• Matt Wynne.
  • Book Matt Wynne, Aslak Hellesoy: "The Cucumber Book: Behaviour-Driven Development for Testers and Developers".
    • Aslak Hellesoy.
    • Blog Matt Wynne "Tea-Driven Development. Matt Wynne taking it one tea at a time".
    • The Pragmatic Bookshelf "Matt Wynne, Aslak Hellesoy: The Cucumber Book: Behaviour-Driven Development for Testers and Developers".
  • Book Ian Dees, Matt Wynne, Aslak Hellesoy: "Cucumber Recipes: Automate Anything with BDD Tools and Techniques".
    • The Pragmatic Bookshelf "Ian Dees, Matt Wynne, Aslak Hellesoy: Cucumber Recipes: Automate Anything with BDD Tools and Techniques".
• Book David Chelimsky, Dave Astels, Bryan Helmkamp, Dan North, Zach Dennis, Aslak Hellesoy: "The RSpec Book: Behaviour Driven Development with RSpec, Cucumber, and Friends".
  • The Pragmatic Bookshelf "David Chelimsky, Dave Astels, Bryan Helmkamp, Dan North, Zach Dennis, Aslak Hellesoy: The RSpec Book: Behaviour Driven Development with RSpec, Cucumber, and Friends".

• Book Abel Avram, Floyd Marinescu: "Domain-Driven Design Quickly".
  • Free PDF download of the book InfoQ "Domain Driven Design Quickly".
• Book Eric J. Evans: "Domain-Driven Design: Tackling Complexity in the Heart of Software" #.
  • Video YouTube "Eric Evans: What I've learned about DDD since the book".
• Book Dan Haywood: "Domain-Driven Design Using Naked Objects".
• Book Jimmy Nilsson: "Applying Domain-Driven Design and Patterns: With Examples in C# and .NET".
• Book Vaughn Vernon: "Implementing Domain-Driven Design".
  • Vaughn Vernon: Architecture and Domain-Driven Design.

• Gojko Adzic - Building software that matters.
  • Book Gojko Adzic: "Test Driven .Net Development with Fitnesse".
    • The companion website Gojko Adzic - Building software that matters "Test Driven .NET Development with FitNesse: Second Edition" with a free HTML online and free PDF edition of the book.
    • The free online HTML edition Gojko Adzic - Building software that matters "Test Driven .NET Development with FitNesse: Second Edition".
    • The Wiki Gojko Adzic "FitNesse community web site".
• Book Rick Mugridge, Ward Cunningham: "Fit for Developing Software: Framework for Integrated Tests" #.
• Book Frank Westphal: "Testgetriebene Entwicklung mit JUnit & FIT: Wie Software änderbar bleibt" about JUnit 3 only, and FIT #.

• internet.com "Agile Software Development eBook", sponsored by IBM - “This eBook begins with an overview of the Agile Scaling Model (ASM), a framework used to provide context to the plethora of agile methodologies available today”.

• LogiGear "Key Success Factors for Keyword Driven Testing".
• Agile Toolkit Podcast. Conversations about Agile Development and Delivery "Agile 2009 - Aslak Hellesoy - Cucmber test framework".
• Will Beattie's Technical Blog "Getting started with SpecFlow, WatiN, ATDD and BDD" #.
• Blog "Agile Testing. Did anybody say webscale?", Article "Writing FitNesse tests in Python" #.
• cuke4ninja.
  • Gojko Adzic, David de Florinier "The Secret Ninja Cucumber Scrolls" - “This document is a step-by-step guide for Cucumber, a tool that is quickly becoming the weapon of choice for many agile teams when it comes to functional test automation, creating executable specifications and building a living documentation”.
  • Github "davedf/cuke4ninja".
  • Twitter "cuke4ninja".
• Dale H. Emery. consultant to software teams and leaders - Articles.
  • Article “Writing Maintainable Automated Acceptance Tests” (PDF) #.
• Google Groups "Lettuce Users".
• Grig Gheorghiu "Acceptance testing with FitNesse and PyFIT".
• Blog Blogisticon - Das Holisticon-Blog, Hamburg #.
• Linux Journal, Issue 189, January 2010 - Reuven M. Lerner "At the Forge - Cucumber".
• Andrej Pietschker, XING "Andrej Pietschker", LinkedIn "Andrej Pietschker":
  • German Testing Night 2014-03-27 "Giesecke&Devrient, Andrej Pietschker: Tests als Requirements - Brücke zwischen Entwicklung und Systemtest bauen" - How to use BDD and Gherkin for testing and requiements.
• Ruby Inside, Mike Gunderloy "Cucumber: The Latest in Ruby Testing".
• Net tuts, David Sale "Behavior-Driven Development in Python" → Describing Github "rlisagor/freshen".
• StickyMinds, Danny R. Faught "Keyword-Driven Testing".
  • EN.Wikipedia "Functional testing", EN.Wikipedia "Black-box testing".
• Blog Joseph Wilk "Programming bits and bobs".

• Google Groups "SpecFlow", Google Groups "SpecFlow Announcements".