Start using Behaviour-Driven Development (BDD) when designing an application and focus on the domain instead of the database, Julie Lerman, a Microsoft MVP since 2003, suggests. BDD lets developers focus on user stories and behaviour in the business domain when building up logic and tests. New to BDD, Julie has implemented a working example using Visual Studio, C# and SpecFlow.
The project for Cucumber, a Behaviour Driven Development, BDD, tool, has recently increased the team and intensive work last months has brought open bugs down substantially, Aslak Hellesøy revealed when talking about the Cucumber ecosystem during a Cucumber conference day last week.
The community research we published on .NET tools and practices had more than 650 votes leading to some interesting results. We attempt to draw insights.
InfoQ's research initiative continues with an 8th question: "What are the most widely used .NET practices and tools?". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.
Wikispeed founder Joe Justice gave a talk in Wellington, New Zealand, this week in which he spoke about the Wikispeed mission of "Rapidly Solving Problems for Social Good", starting by using agile techniques to build a 100MPG vehicle with the intent of creating a new approach to motor-vehicle manufacturing, using open-source and crowd-source approaches building on agile values and principles.
Recently Cap Gemini's Steve Jones has written an article on how he believes that thinking about solutions to problems is less important these days than jumping on the latest hype bandwagon. Although he uses REST and Big Data as examples, he believes it goes beyond any single technology and that eventually IT will no longer belong to IT people.
Mighty-Moose, a continuous build and test-runner for .NET, now comes free of charge.
Dan North has recently discussed the impact of opportunity costs in his article "The Art of Misdirection." Opportunity Cost is about choosing an obvious solution for a particular problem context, although sometimes an alternative option may be the better choice. Software engineers, in particular, are subject to such opportunity costs as they are constantly facing decisions in their daily work.
Forrester have recently released the results of their November 2011 Global Agile Software Application Development Online Survey in a report entitled "Survey Results: How Agile Is Your Organization?" It contains a number of interesting findings around how organisations that have adopted Agile are dealing with their implementation.
What is the most important thing that the Agile community needs to embrace in 2012 and beyond? InfoQ had the opportunity to attend the recent YOW! Australia Software Developer Conference and took the opportunity of having such a large number of Agile speakers in one place to sit in on the sessions and ask them their thoughts on this question.
The Global Day of Code Retreat is an world-wide event to raise the awareness for code retreats, which is a full-day format of learning and improving development skills by solving a simple task repeatedly with TDD and Pair Programming while focussing on important aspects of software development.
There has been a lot of discussion recently about the tension inherent in the Agile Manifesto value "individuals and interactions over processes and tools". This item examines some of the points that have been made.
Behavior Driven Development (BDD) is being increasingly seen as an alternative way to approach Test Driven Development. SpecFlow and NSpec are popular frameworks for BDD in .NET. They help create test specifications that are easy to read even for non-programmers and allow the design of the software to be driven by it’s purpose.
James Whittaker, a former Microsoft architect, author of several books in the “How to Break Software” series, and currently Director of Test Engineering at Google, has written a series of posts on how Google does testing. Google blends development with testing, having relatively few testers, and each product goes through successive channels before is ready for prime time.
A new form of an old question has been asked in the Behavior Driven Development community: is BDD merely Acceptance Test Driven Development done well? While the community calls out the differences, Dan North makes a request to avoid focusing on them, calling TDD "amazing".